John Ellson wrote:
Rex Dieter wrote:
Per
http://bugzilla.redhat.com/bugzilla/166344
it appears that there is no shared libpthread or libdl on x86_64.
The lack of these shared libraries is causing applications linking
against libgc to fail with undefined symbols.
Can anyone confirm this (I don't have access to any x86_64 box)? Is
this on purpose or a (glibc) bug?
-- Rex
Seems OK on my x86_64 box, so long as you have glibc-devel installed:
$ ls -l /usr/lib64/libdl* /usr/lib64/libpthread*
-rw-r--r-- 1 root root 11882 Sep 12 12:58 /usr/lib64/libdl.a
lrwxrwxrwx 1 root root 22 Sep 13 10:48 /usr/lib64/libdl.so ->
../../lib64/libdl.so.2
-rw-r--r-- 1 root root 289334 Sep 12 12:58 /usr/lib64/libpthread.a
-rw-r--r-- 1 root root 222 Sep 12 12:40 /usr/lib64/libpthread.so
-rw-r--r-- 1 root root 1596 Sep 12 12:58
/usr/lib64/libpthread_nonshared.a
$ rpm -qf /lib64/libdl.so.2
glibc-2.3.90-12
$ rpm -qf /usr/lib64/libdl.so
glibc-devel-2.3.90-12
$ rpm -qf /usr/lib64/libpthread.so
glibc-devel-2.3.90-12
Jonh
gc needs a BuildRequires on glibc-devel.
If I install gc-6.6-2 from extras I get:
$ ldd libgc.so
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002aaaaac0f000)
libc.so.6 => /lib64/libc.so.6 (0x00002aaaaad1c000)
/lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
but if I "rpmbuild --rebuild" it from the src.rpm I get:
$ ldd libgc.so
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aaaaac0f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002aaaaad24000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002aaaaae28000)
libc.so.6 => /lib64/libc.so.6 (0x00002aaaaaf36000)
/lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
John
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-devel-list