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: Wed, 19 Jun 2013 15:01:00 -0000 [thread overview]
Message-ID: <bug-15648-131-601hbHiPVH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15648-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15648
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
We need a complete reproducer for this issue please.
Include exactly the steps you took and the expected versus observed results.
This includes the exact gcc command you used to compile your application, and
exactly what version of glibc you were using.
If you are using a distro glibc then you need to file this issue upstream with
the distro so they can determine if any of their patches caused the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-19 15:01 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 ` carlos at redhat dot com [this message]
2013-06-20 2:47 ` [Bug libc/15648] " 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
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-601hbHiPVH@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).