Complete.Org: Mailing Lists: Archives: freeciv-dev: July 2000:
[Freeciv-Dev] Re: Help with Readline
Home

[Freeciv-Dev] Re: Help with Readline

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Help with Readline
From: Thue <thue@xxxxxxx>
Date: Sun, 23 Jul 2000 15:18:51 +0200

> > I don't know much about shared libraries, but I can do:
> > 
> > $ ldd /usr/lib/libreadline.so
> >         libncurses.so.5 => /lib/libncurses.so.5 (0x40028000)
> >         libc.so.6 => /lib/libc.so.6 (0x40066000)
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> > 
> > which is presumably how it knows to also link libncurses.
> > 
> > I think it shouldn't depend on the readline version, just how it
> > was packaged/compiled/installed?
> 
> Sounds rigth - So it is bugs in the respective distros!?
> 
> > > Now, how do we
> > > 1) make configure link with another lib while checking for readline. (that
> > > is the current problem)
> > > 2) Determine which lib we should link against?
> > 
> > Yuck.  :-7
> 
> I am rigth now looking at the bash ./configure which should have the same
> problems and seems to have found a solution to them.
> 
> -Thue

Umm, it seems to be pretty complicated in bash.
Does anyone know how to fix the lib setup on the systems? Is it really a
bug in the lib setup, or is it considered allowed? If so I think we should
just mention it in the INSTALL file so they can correct it themselves.

-Thue



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