This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/11682] New: undefined reference to `__condvar_cleanup' from 2.3.5 to 2.12
- From: "others1 at pervalidus dot net" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 9 Jun 2010 02:23:35 -0000
- Subject: [Bug nptl/11682] New: undefined reference to `__condvar_cleanup' from 2.3.5 to 2.12
- Reply-to: sourceware-bugzilla at sourceware dot org
I get the following error upgrading from 2.3.5 to 2.12 git, using --prefix=/usr
--enable-stackguard-randomization --enable-add-ons=libidn,nptl --enable-bind-now
--enable-kernel=2.6.33 --without-cvs
--with-headers=/home/fredlwm/src/linux-2.6.34/objdir/usr/include --with-tls
/home/fredlwm/src/glibc-2.12-20100601/objdir/nptl/libpthread_pic.a(pthread_cond_timedwait.os):
In function `pthread_cond_timedwait@@GLIBC_2.3.2':
pthread_cond_timedwait.c:(.text+0xaa): undefined reference to `__condvar_cleanup'
/usr/lib/gcc/i686-pc-linux-gnu/4.4.4/../../../../i686-pc-linux-gnu/bin/ld:
/home/fredlwm/src/glibc-2.12-20100601/objdir/nptl/libpthread_pic.a(pthread_cond_timedwait.os):
relocation R_386_GOTOFF against undefined hidden symbol `__condvar_cleanup' can
not be used when making a shared object
/usr/lib/gcc/i686-pc-linux-gnu/4.4.4/../../../../i686-pc-linux-gnu/bin/ld: final
link failed: Bad value
collect2: ld returned 1 exit status
make[2]: *** [/home/fredlwm/src/glibc-2.12-20100601/objdir/nptl/libpthread.so]
Error 1
binutils is 2.20.51.0.9, GCC 4.4.4, kernel headers from 2.6.34.
--
Summary: undefined reference to `__condvar_cleanup' from 2.3.5
to 2.12
Product: glibc
Version: 2.12
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: others1 at pervalidus dot net
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=11682
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.