This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/15648] multiple definition of `__lll_lock_wait_private'
- From: "knrstaj at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 20 Jun 2013 09:24:28 +0000
- Subject: [Bug libc/15648] multiple definition of `__lll_lock_wait_private'
- Auto-submitted: auto-generated
- References: <bug-15648-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15648
--- Comment #8 from Neil <knrstaj at gmail dot com> ---
Yes, I see the libc.a and libpthread.a
nm /usr/lib/i386-linux-gnu/libpthread.a
lowlevellock.o:
U __have_futex_clock_realtime
00000030 T __lll_lock_wait
00000000 T __lll_lock_wait_private
00000060 T __lll_timedlock_wait
000001c0 T __lll_timedwait_tid
00000190 T __lll_unlock_wake
00000160 T __lll_unlock_wake_private
U _dl_sysinfo
nm /usr/lib/i386-linux-gnu/libc.a
libc-lowlevellock.o:
00000000 T __lll_lock_wait_private
00000030 T __lll_unlock_wake_private
U _dl_sysinfo
Why not to make __lll_lock_wait_private and __lll_unlock_wake_private in a
individual file?
If ld include libc-lowlevellock.o first, it always cause error when includeing
lowlevellock.o. Right?
--
You are receiving this mail because:
You are on the CC list for the bug.