glibc-2.2.5 undefined _dl_cpuclock_offset very very strange !

Ingo Krabbe i.krabbe@dokom.net
Sun May 12 11:50:00 GMT 2002


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'

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 ...

INGO

-------------- next part --------------
A non-text attachment was scrubbed...
Name: out.err
Type: text/x-c
Size: 1713 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20020512/7ad62779/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: out.good
Type: text/x-c
Size: 1603 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20020512/7ad62779/attachment-0001.bin>


More information about the Libc-alpha mailing list