[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Linked against libc5 AND libc6?

On Thu, 2 Jul 1998, Shaleh wrote:

: Nathan E Norman wrote:
: >kepler:/usr/annex $ ldd erpcd
: >         libdb.so.2 => /lib/libdb.so.2 (0x4000a000)
: >         libc.so.5 => /lib/libc.so.5 (0x40018000)
: >         libc.so.6 => /lib/libc.so.6 (0x400d6000)
: >         ld-linux.so.2 => /lib/ld-linux.so.2 (0x40179000)
: Do an ldd on libdb.so.2.  I find the most common cause of this double
: linkage is that one of the other libs is linked against libc6 when the
: actual app was linked on libc5 (this was the problem w/ quake mentioned
: on the mailing list ad infinitum).  Otherwise get the source and compile
: it on either libc5 or a libc6 system.

Hmm ... ok, that makes sense.  When I do an ldd on erpcd on a libc5
system it only says it's linked against libc5 ... and libdb is linked
against libc6 on hamm systems.

tesla:/usr/annex # ldd erpcd 
        libdb.so.2 => /lib/libdb.so.2
        libc.so.5 => /lib/libc.so.5
tesla:/usr/annex # cat /etc/debian_version 

Any way out of this mess?  I don't have a libc5 version of libdb 2 ... I
had to make a rather ugly hack to get this to run on the bo system :)

Thanks for the explanation of the crosslinking.  That makes a lot more
sense now that I think about it.

Nathan Norman
MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD  57104
mailto://finn@midco.net   http://www.midco.net
finger finn@kepler.midco.net for PGP Key: (0xA33B86E9)

Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null

Reply to: