public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/5784] Fix static linking with -lpthread.
Date: Mon, 08 Apr 2024 20:04:15 +0000 [thread overview]
Message-ID: <bug-5784-131-jj0TnRaY43@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-5784-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=5784
--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Florian Weimer from comment #10)
>
> This is a GCC bug. It should not use weak symbols in static builds. Or
> dynamic builds, but there it doesn't matter anymore since glibc 2.34. I
> think we cleaned all this up for libstdc++, looks like we missed libgfortran.
I opened:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114646
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-08 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-5784-131@http.sourceware.org/bugzilla/>
2012-12-19 10:43 ` [Bug nptl/5784] [RFC] Support " schwab@linux-m68k.org
2014-07-02 7:18 ` fweimer at redhat dot com
2022-04-19 16:42 ` [Bug nptl/5784] Fix " dushistov at mail dot ru
2024-04-08 18:35 ` hjl.tools at gmail dot com
2024-04-08 19:28 ` fweimer at redhat dot com
2024-04-08 19:36 ` hjl.tools at gmail dot com
2024-04-08 19:39 ` hjl.tools at gmail dot com
2024-04-08 19:57 ` fweimer at redhat dot com
2024-04-08 20:04 ` hjl.tools at gmail dot com [this message]
2024-04-08 20:08 ` pinskia at gcc dot gnu.org
2024-04-08 20:08 ` pinskia at gcc dot gnu.org
2024-04-08 21:36 ` bruno at clisp dot org
2024-04-09 12:29 ` hjl.tools at gmail 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-5784-131-jj0TnRaY43@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).