public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15648] multiple definition of `__lll_lock_wait_private'
Date: Thu, 03 Oct 2013 01:00:00 -0000 [thread overview]
Message-ID: <bug-15648-131-QIbasYPRRm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15648-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15648
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #21 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Ondrej Bilka from comment #20)
> Carlos, is your patch ready to libc-alpha?
No. This issue needs to be driven to consensus over the solution to use for
libpthread, either we link with `ld -r' and force all of libpthread into the
application during a static link or we do it piece-meal dependency by
dependency trying to keep the link minimal.
Previous comments from Roland and myself was that we should try to fix these
kinds of issues one at a time, but it's looking liked `ld -r' is going to be
the only real solution given the number of applications and core tools that use
a weakref and a check to test for conditional library inclusion.
This has to go to libca-alpha for discussion, but I don't have time to champion
this right now. If you are interested I encourage you to get consensus and
implement a solution, I'd be happy to review.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-03 1:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 10:15 [Bug libc/15648] New: " knrstaj at gmail dot com
2013-06-19 15:01 ` [Bug libc/15648] " carlos at redhat dot com
2013-06-20 2:47 ` knrstaj at gmail dot com
2013-06-20 2:54 ` knrstaj at gmail dot com
2013-06-20 3:32 ` [Bug libc/15648] Support building glibc with -flto carlos at redhat dot com
2013-06-20 3:34 ` carlos at redhat dot com
2013-06-20 6:10 ` knrstaj at gmail dot com
2013-06-20 8:15 ` [Bug libc/15648] multiple definition of `__lll_lock_wait_private' schwab@linux-m68k.org
2013-06-20 9:24 ` knrstaj at gmail dot com
2013-06-20 12:55 ` carlos at redhat dot com
2013-06-20 12:57 ` carlos at redhat dot com
2013-06-20 12:58 ` jakub at redhat dot com
2013-06-20 13:52 ` carlos at redhat dot com
2013-06-21 1:22 ` knrstaj at gmail dot com
2013-06-21 1:33 ` knrstaj at gmail dot com
2013-06-21 7:42 ` schwab@linux-m68k.org
2013-06-21 7:52 ` jakub at redhat dot com
2013-06-21 13:13 ` carlos at redhat dot com
2013-06-21 13:21 ` carlos at redhat dot com
2013-06-21 14:42 ` knrstaj at gmail dot com
2013-10-02 17:05 ` neleai at seznam dot cz
2013-10-03 1:00 ` carlos at redhat dot com [this message]
2014-02-07 3:04 ` [Bug nptl/15648] " jsm28 at gcc dot gnu.org
2014-06-13 15:03 ` fweimer at redhat dot com
2021-02-23 8:32 ` fweimer at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15648-131-QIbasYPRRm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).