This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/15648] multiple definition of `__lll_lock_wait_private'

Jakub Jelinek <jakub at redhat dot com> changed:

           What    |Removed                     |Added
                 CC|                            |jakub at redhat dot com

--- Comment #16 from Jakub Jelinek <jakub at redhat dot com> ---
Static linking of -lpthread never worked well, there are tons of issues with
that, which is why in Fedora/RHEL we are just linking all the content of
libpthread.a using ld -r into libpthread.o and libpthread.a contains just that
single object.  Then this bug doesn't exist.  There are many assumptions
(unwritten dependencies) in between libpthread object files, with dynamic
linking you simply have all of them together or nothing, but with libpthread,
unless you do that ld -r hack, you don't.  Not to mention that many programs
(e.g. gcc gthr.h) check using weakref for availability of some pthread_*
symbol(s) and if non-NULL, assume all of libpthread is available, rather than
random parts from it.

Why exactly are you linking statically?

You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]