Re: next question - with-keyboard not working

"Pascal J. Bourguignon" <[email protected]>
Newsgroups gmane.lisp.clisp.general
Organization Informatimago
Message-ID <[email protected]>
[email protected] (Don Cohen) writes:

> Pascal J. Bourguignon writes:
>  > [email protected] (Don Cohen) writes:
>  > 
>  > I would guess that KEYBOARD comes along with SCREEN.
> see below
>
>  > But you're on unix apparently.  If you compiled clisp yourself, check
> yes and yes
>
>  > the configuration and compilation logs.  Perhaps it failed to detect
>  > something and that made it opt out of screen and keyboard?
>
> I used:
>  ./configure CC='gcc -m64' --with-libsigsegv-prefix=/usr/local \
>  --disable-maintainer-mode --with-debug --with-module=rawsock build-dir
> and the output never mentions either screen or keyboard...
> I do see in stream.c 
>  #ifdef KEYBOARD
>
>  /* Keyboard-Stream
>  ...
>
> In lispbibl.c I see
>  /* Whether to create a stream *KEYBOARD-INPUT*
>   and whether it will be used for the stream *TERMINAL-IO*: */
>  #if (defined(UNIX) && !defined(NO_TERMCAP_NCURSES)) ||
>  defined(WIN32_NATIVE)
>    #define KEYBOARD
>    #if 0
>      #define TERMINAL_USES_KEYBOARD
>    #endif
>  #endif
> BTW I see something similar for SCREEN
>
> I see in clisp --version
> gcc -m64 -g -O2 -W ...  -DNO_TERMCAP_NCURSES ...
> so that seems to be the problem.
>
> This seems to come from makemake:
>  if [ "${with_termcap_ncurses}" = no -o "${LIBTERMCAP}" = "broken" ] ;
>  then
>    XCFLAGS=$XCFLAGS' -DNO_TERMCAP_NCURSES'
>    LIBTERMCAP=""
>  fi
>
> Above that in makemake I see
>  # Set the defaults for the --with options.
>  with_termcap_ncurses=yes # no effect if missing termcap/ncurses
> but also
>  # These variables are set by configure:
>   ...
>  LIBTERMCAP='broken'           # '-L/usr/??/lib' or 'broken' or ''
>
> and yet I see nothing about libtermcap in the configure script.
> I do see in config.log:
>  configure:38073: gcc -m64 -o conftest -g -O2   conftest.c
>  -ltermcap  -ldl -lavcall -lcallback >&5
> and
>  /bin/ld: cannot find -ltermcap
> and
>  LIBTERMCAP='broken'
> but so far I can't figure out where those come from.
> I also don't yet see how to get libtermcap.

How to get libtermcap and libncurses would depend on your exact unix
system.

On a debian linux, you'd do:

     sudo apt-get  install libncurses5 libncurses5-dev

termcap is the old terminal database. On modern linux, it's replaced by
terminfo.  A library to access that database is libtinfo5, it's a
dependency of ncurses, so it should be installed automatically, along
with the terminal database by the above command.

If you're on a different linux or a different unix, you will have to see
how to find and install the corresponding libraries with your package
manager, or in the worst case, download and compile them manually.

The upstreams are 
http://www.gnu.org/software/ncurses/
http://www.catb.org/esr/terminfo/



>  > > And why do you seem to have newer updates than I do when I've been
>  > > doing hg pull seemingly successfully until recently?
>  > 
>  > Good question.
>  > [pjb@kuiper :0.0 clisp-hg]$ hg paths
>  > default = http://hg.code.sf.net/p/clisp/clisp
>   $ hg paths
>   not trusting file /home/don/hg/clisp/.hg/hgrc from untrusted user don,
>   group don
>   not trusting file /home/don/hg/clisp/.hg/hgrc from untrusted user don,
>   group don
> no other output
> I'm guessing hg pull still works for you?
> So I'm using a non-current location.

You should probably address first the error indicated by the message.

    ls -l /home/don/hg/clisp/.hg/hgrc

and check the owner, group and access rights.
I have pjb:pjb and 644, and my .hg/ directory is pjb:pjb and 755.

    $ cat .hg/hgrc
    [paths]
    default = http://hg.code.sf.net/p/clisp/clisp

-- 
__Pascal Bourguignon__


------------------------------------------------------------------------------
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.