[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Kenichi Handa
Subject: ospeed
Date: Mon, 13 Nov 2000 22:01:18 +0900 (JST)

Dave Love <address@hidden> writes:
KH>  The second one is the problem of `ospeed'.  It seems that HPUX
KH>  10.20 doesn't have the variable `ospeed'.  So, "extern XXX
KH>  opseed" hack doesn't work.  We have discussed on `ospeed' problem
KH>  long ago and my conclusion was to use Emacs's internal variable
KH>  only (see the attached mail at the tail).

> I think I actually removed it from some of the files where it wasn't
> used.

Currently sysdep.c and termcap.c uses the variable
`ospeed'.   But, as termcap.c declares `ospeed' by itself as
short ospeed;
HPUX has no problem.   Only sysdep.c extern it.

My basic question is:
        Are there any meanings in setting system's `ospeed' variable?

If not, as sysdep.c never refers a value of `ospeed' (it
just set it), I want to change this name to, say
emacs_ospeed, as I wrote before.

> I happened to look at the Texinfo configure recently in
> connexion with termcap.  It contains this:
> dnl Checks for variables.
> # HP-UX 9 (at least) needs -lncurses which defines termcap variables PC etc.
> AC_MSG_CHECKING(for library with termcap variables)
> AC_CACHE_VAL(ac_cv_var_ospeed,
> oldLIBS=$LIBS 
> for trylib in $termlib ncurses curses termlib termcap terminfo; do
>    if test "x$trylib" != "x$termlib"; then
>      LIBS="$oldLIBS -l$termlib -l$trylib"
>    else
>      LIBS="$oldLIBS -l$termlib"
>    fi
>    AC_TRY_LINK(, 
> #include <ncurses/termcap.h>
> #else
> #include <termcap.h>
> #else
> #undef PC
> char *BC;
> char* *UP;
> char PC;      
> short ospeed; 
> #endif
> #endif
> return ospeed != 0;
> , ac_cv_var_ospeed=$trylib; break)
> done
> )
> AC_MSG_RESULT($ac_cv_var_ospeed)
> if test -n "$ac_cv_var_ospeed" \
>    && test "x$termlib" != "x$ac_cv_var_ospeed"; then
>   TERMLIBS="${TERMLIBS} -l${ac_cv_var_ospeed}"
> fi

Could you explain what does this mean?  I have no knowldge
about termcap/terminfo/ncurses matter.

By the way, I couldn't find any header files under
/usr/include of HPUX 10.20 that define "termcap variables PC etc."

Ken'ichi HANDA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]