On Fri, Jul 20, 2001 at 04:05:44PM -0700, Matt wrote:
> Well, I downloaded ncurses 5.2 and its patches built it into $HOME and still
> get the same error. How can I tell for sure which ncurses lynx is trying to
> use? ~/lib is the first thing in LD_LIBRARY_PATH and I did a 'make clean'
> and killed config.cache and config.status and reconfigured and ran 'make'
> again.
FreeBSD's linker is a little brain-damaged: unless you link statically,
it will try to use the shared library in /usr/lib. (I retain that one,
for testing, and build more recent stuff against static libraries on
that platform, do some test-builds with shared libraries, of course).
That is
setenv LIBS="-L$HOME/lib -lncurses"
setenv CPPFLAGS="-I$HOME/include -I$HOME/include/ncurses"
configure
> P.S. I hate installing software under $HOME ;)
I install ncurses (static) under /usr/local on that platform. To avoid
confusion, I use the ncurses --disable-overwrite option, so the configure
script won't find two matches for <curses.h>.
--
Thomas E. Dickey <[EMAIL PROTECTED]>
http://dickey.his.com
ftp://dickey.his.com
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
