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: David Pfitzner <dwp@xxxxxxxxxxxxxx>
Date: Sun, 23 Jul 2000 14:34:55 +1000 (EST)

Thue <thue@xxxxxxx> wrote:

> btw, I think I can see from the output that the problem indeed is that
> linking with your readline 4.1 requires linking with -ltermcap as well at
> the same time.
> 
> Now, assuming the above is correct, how do we get around it? The problem
> is not in readline 2.x as far as we know, and in some 4,1's. It is in the
> 4.1's with mandrake 7.1 (me) and suse, but dwp had no problem with his
> debian 4.1 readline. I have one compiled from source, and it has the
> problem too.

Well my debian system has it setup so using -lreadline also links in 
libncurses.  (Actually this is related to the problem I had earlier: an 
older package didn't correctly depend on the right libncurses package; 
fixed in a newer debian package version.)

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?

> 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

-- David



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