This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: [50 character or so descriptive subject here (for reference)]
- To: ragnar@lightside.ddns.org
- Subject: Re: [50 character or so descriptive subject here (for reference)]
- From: Andreas Jaeger <aj@arthur.rhein-neckar.de>
- Date: 25 Oct 1998 12:51:18 +0100
- Cc: libc-alpha@cygnus.com
- Mail-Copies-To: never
- References: <199810241931.UAA26817@lightside.ddns.org>
>>>>> ragnar writes:
>> Synopsis: can't get rid of libc.so.5?
>> Severity: serious
>> Priority: high
>> Category: libc
>> Class: sw-bug
>> Release: libc-2.0.99
>> Environment:
> Host type: i686-pc-linux-gnulibc1
> System: Linux lightside.ddns.org 2.1.126 #33 Sat Oct 24 08:59:49 MET 1998 i686 unknown
> Architecture: i686
> Addons: crypt linuxthreads
> Build CC: ecc
> Compiler version: egcs-2.91.57 19980901 (egcs-1.1 release)
> Kernel headers: 2.1.126
>> Description:
> Somehow I'm ending up with a libc.so.5 in ld.so, and it obviously shouldn't
> be there. I spent _all_ sunday trying to figure out why or how to solve it,
> but.. i must admit I have no idea since everything looks like it's in its
> place, so the only thing that I can think of is some silly configure problem
> because glibc 2.0.7presomething worked fine.
> Anyway, since:
> lightside:~/comp/glibc-2.0.99/build/elf# ldd ld-linux.so.2
> ./ld-linux.so.2 => ./ld-linux.so.2 (0x4000c000)
> libc.so.5 => /lib/libc.so.5 (0x40020000)
Which ldd are you using? Since you're just building glibc you should
set up your environment correctly. Try for example:
$ LD_TRACE_LOADED_OBJECTS=1 LD_LIBRARY_PATH=.:elf:math:resolv:nss:nis:db2 \
elf/ld-linux.so.2 elf/ld-linux.so.2
statically linked
$ LD_TRACE_LOADED_OBJECTS=1 LD_LIBRARY_PATH=.:elf:math:resolv:nss:nis:db2 \
elf/ld-linux.so.2 sunrpc/rpcgen
libc.so.6 => ./libc.so.6 (0x40000000)
/usr/glibc/glibc-2.1/lib/ld-linux.so.2 => elf/ld-linux.so.2 (0x2aaaa000)
Btw. I've seen some reports which indicated failure of glibc together
with Linux 2.1.126. I'd really appreciate if somebody could tell me
if Linux 2.1.126 is broken or glibc2.
Andreas
--
Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de