Re: Linked against libc5 AND libc6?
Frankly the only solution is to find a libc5 version of everything you need, or a libc6 version of everything you need. Sorry. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
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 1.3 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 :) Well, you could take the libdb.so.2 you built on the bo system and stick it in /usr/lib/libc5-compat on the hamm system (don't forget to run ldconfig after). The loader is intelligent in the way that if there are two copies of the library, it will link in the one which uses the same version of libc as the binary. Then perhaps you should petition someone to do a libc5 version of DB 2 for the oldlibs section. Regards, /Anders -- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | Mud at Kingdoms| [EMAIL PROTECTED] NetGuide Scandinavia | telnet kingdoms.se 1812| Fax: +46 31 50 79 39 http://www.netg.se | | Tel: +46 31 50 79 40 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Linked against libc5 AND libc6?
Hi there, I've got an odd problem ... I'll ask the questions first: What can I do about a binary that is linked against libc5 and libc6? It (of course) segfaults every time I try to run it. Now, the explanation: We recently purchased a Bay Networks 8000 Remote Access Concentrator. This box needs a UNIX (or NT) machine behind it for authentication purposes. Bay distributes a CD with the software on it - amazingly, Linux binaries were pre-built (good thing since the source wouldn't compile, but that's a question for a different list). The pre-built binaries are linked against libc5 and libc6. I'm not too sure why they did this, but I had to set up a bo box to get this to work. (Perhaps they were thinking that a libc6 box wouldn't have libc5.so installed?) 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) At any rate, I'm wondering if there's anything I can do to prevent this thing from trying to load either of the shared libs. I don't understand shared libraries and all that underlying stuff to well yet, so go easy on me :) If it's a flat No Way In Hell, that's ok - I'll just have to get this source to compile under libc5 OR libc6, right? Sorry for being ignorant on this stuff - I'm trying to learn it. Thanks in advance ... -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
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. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
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. Noah PGP public key available at http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html or by 'finger -l [EMAIL PROTECTED]' -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBNZvhHIdCcpBjGWoFAQG0RAP/TxPPX3PKei8BcO+0nZ0ckq3asr4jw1Sq jXgF/5BplrBrwMNypDS2mSvDKnujjLJN1NM9goj7n12S5pn2jqwgL4emr5Xlt2Bu A7Yf+PKTWnpzFXUgJMWPChWxI9Uk0ni6e7QuLCz0/uWfndZcvE2ttKXUD10ZJs3x /iQkeiQ8K/A= =au/T -END PGP SIGNATURE- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
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 1.3 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://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
