Re: [clisp-list] Getting 2.31 to compile on older systems

[Douglas P. <dg...@ma...>]

On Tuesday, Sep 16, 2003, at 10:52 US/Eastern, Fred Cohen wrote:

> In my eternal attempts to get clisp to compile for my special needs, I
> built a system or the sole purpose of building a clisp.  It is, to a 
> not
> so close approximation, a Redhat 6.2 or so system.  I got the clisp2.31
> source tar file, untarred it, and did a ./configure followed by
> 	cd src
> 	./makemake --with-dynamic-ffi > Makefile
> 	make config.lisp
>
> So far no problem.  Then I did:
> 	make
>
> which ultimately ended in:
> ...
> libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl    -o 
> lisp.run
> stream.o: In function `rd_ch_terminal3':
> stream.o(.text+0xd409): undefined reference to `rl_already_prompted'
> stream.o: In function `make_terminal_stream_':
> stream.o(.text+0xdab5): undefined reference to `rl_gnu_readline_p'
> stream.o: In function `rl_memory_abort':
> stream.o(.text+0x13693): undefined reference to `rl_gnu_readline_p'
> collect2: ld returned 1 exit status
> make: *** [lisp.run] Error 1
>
> Does this mean I need a newe readline library or some such thing? Or am
> I missing something much bigger.  And of course - is there a way to not
> have to update my libraries and still get clisp to run reasonably well?
> I don't want to lose line editing - that's real handy...

JFG&G (Just For Grins & Giggles), you could try configuring it without 
readline and see how far you get. At least that would(maybe) eliminate 
one extra variable.

I too would not want to use it without readline, so I'm only suggesting 
this as an interim to see if there are other issues that might pop-up.

<D\'gou