This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: glibc-2.2.5 undefined _dl_cpuclock_offset very very strange !
- From: Andreas Jaeger <aj at suse dot de>
- To: Ingo Krabbe <i dot krabbe at dokom dot net>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Sun, 12 May 2002 21:44:13 +0200
- Subject: Re: glibc-2.2.5 undefined _dl_cpuclock_offset very very strange !
- References: <E176yQi-0005RX-00@mail.dokom.net>
Ingo Krabbe <i.krabbe@dokom.net> writes:
> Hi,
>
> I've read the Ulrich Dreppers answers about mixing architectures but I still
> cannot believe whats happening here:
>
> I have two systems on my hard disk. I build a glibc into /glibc225 a new gcc
> into /gcc and some binutils to /binutils. When booting with one system I get
> the
>
> /glibc225/lib/libpthread.so: undefined reference to `_dl_cpuclock_offset'
Which dynamic linker is used? Is the one from /glibc225/lib used?
Use readelf to check for the path,
Andreas
> error. I cannot reproduce that on the other system no matter how hard I try !
>
> I will attach two outputs of
> gcc -v main.c -lpthread &> out.err -- for the problem
> gcc -v main.c -lpthread &> out.good -- for the good result
>
> which look quite the same with the difference that one throws the error. If
> anybody can tell what's different please tell me. May it be the kernel ???
>
> The working kernel says
> Linux dimwit 2.4.18 #5 Mon Mai 13 14:37:25 CEST 2002 i686 unknown
> the other one should be something like
> Linux dimwit 2.5.15 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX athlon unknown
>
> To have the same configuration I linked in /glibc225 /gcc and /binutils into
> both systems (different root disks). And even copied the startfiles
> /usr/lib/crt* from the bad one to the good one.
>
> Awaiting your words of wisdom ...
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj