On Wed, Jul 12, 2017 at 10:23:04PM +0200, Eujean Snyman wrote:
> Bruce Dubbs wrote:
> 
> >
> > I just rebuilt clisp on a system with readline 7 without any problems. Can
> > you post the actual output of the build showing the error?
> >
> > I do confirm that readline.h now has:
> >
> >   extern unsigned long rl_readline_state;
> >
> > so I suppose there could be a runtime issue, but I can't find a build
> > problem.
> >
> 
> My readline.h has the same
>   extern unsigned long rl_readline_state;
> 
> but i believe the problem is in modules/readline/readline.lisp where it
> expects an int.
> 
> After extracting my procedure is as follows:
> 
> sed -i -e '/socket/d' -e '/"streams"/d' tests/tests.lisp
> 
> mkdir build &&
> cd    build &&
> 
> ../configure --srcdir=../                       \
>              --prefix=/usr                      \
>              --with-libsigsegv-prefix=/usr      \
>              --with-libffcall-prefix=/usr       &&
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Finally this produces the following error:
> ...
> ;; Loaded file /sources/blfs/clisp-2.49/build/syscalls/posix.fas
> ;; Loading file /sources/blfs/clisp-2.49/build/regexp/regexp.fas ...
> ;; Loaded file /sources/blfs/clisp-2.49/build/regexp/regexp.fas
> ;; Loading file /sources/blfs/clisp-2.49/build/readline/readline.fas ...
> *** - FFI::FIND-FOREIGN-VARIABLE: foreign variable
>       #<FOREIGN-VARIABLE "rl_readline_state" #x00007F8FCDDC5010> does
> not have the required size or
>       alignment
> 
> ./clisp-link: failed in /sources/blfs/clisp-2.49/build
> make: *** [Makefile:2597: base] Error 1
> 
> Which is what led me to the same fix that Ken mentioned earlier. With
> the patch applied, it compiles
> 
> fine and the following is obtained from clisp --version
> 
> GNU CLISP 2.49 (2010-07-07) (built 3708841252) (memory 3708841376)
> Software: GNU C 7.1.0
> gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit
> -Wreturn-type -Wmissing-declarations -O -DENABLE_UNICODE -DDYNAMIC_FFI
> -DDYNAMIC_MODULES -I.  /usr/lib/libreadline.so -lncurses -ldl
> /usr/lib/libavcall.so /usr/lib/libcallback.so  -L/usr/lib -lsigsegv
> -L/usr/lib -lc libgnu_cl.a
> SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED
> TRIVIALMAP_MEMORY
> libsigsegv 2.11
> libreadline 7.0
> libffcall 1.13
> Features:
> (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL
> COMMON-LISP LISP=CL INTERPRETER
>  SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE
> BASE-CHAR=CHARACTER WORD-SIZE=64
>  PC386 UNIX)
> C Modules: (clisp i18n syscalls regexp readline)
> Installation directory: /usr/lib/clisp-2.49/
> User language: ENGLISH
> Machine: X86_64 (X86_64)
> 
> Which is interesting when compared to the output Ken got, he didn't
> have READLINE as a feature?


True, now you mention it.  I only ran that because the person who
had said "me too" said that he couldn't run it, so it was just a
test to confirm it had compiled.

My only use for it, and the reason it's in the book, is to build
xindy - obviously it manages that fine without readline :)

A few months back I was looking at the development version of clisp,
in the expectation it might get released in time for texlive-2017.
That didn't happen, but it needed libffcall (a development release).
I dislike that because it only installs static libs (and has no
stable interface) so I'm not in a hurry to add it to the book until
it becomes required.

But it looks as if the presence of libffcall is probably what leads
to the build failure.

I find clisp impenetrable, but I will note that the development
version I installed, with libffcall, had to be built as a regular
user.  When I tried running make check, one of the stream tests gave
me an -EPERM, but running make check as root was fine.

The clisp development version also required --enable-portability (if
anybody who likes lisp wants to try this at home).  I think there
has been a new development version of clisp since I did the testing.

ĸen
-- 
I live in a city. I know sparrows from starlings.  After that
everything is a duck as far as I'm concerned.  -- Monstrous Regiment
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to