Re: Linked against libc5 AND libc6?
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 2 Jul 1998, 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)
The executable might not have been built against both libcs, but your
environment might be confusing it. Do you have your $LD_LIBRARY_PATH
environment variable set in your shell? If so, try unsetting it, and
running ldd on the executable.
I've run into this problem several times with libc5 apps. Most recently
effected was Netscape 4.04, dynamically linked against Motif. For some
reason, ld.so wasn't finding libXm.so, so I set the LD_LIBRARY_PATH to
point to the directory containing it. This was the same directory that
contained libc.so.6. This caused Netscape to try linking against both
libc5 and libc6, which caused ugly things to happen. I wouldn't be
surprised if your environment is causing similar things to happen.
PGP public key available at
or by 'finger -l firstname.lastname@example.org'
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Unsubscribe? mail -s unsubscribe email@example.com < /dev/null