public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103133] Binary built with -static using std::thread crashes Date: Mon, 08 Nov 2021 12:31:46 +0000 [thread overview] Message-ID: <bug-103133-4-78rGWBl8tf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103133-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133 Florian Weimer <fw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at gcc dot gnu.org --- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> --- libstdc++.a still uses weak symbols. I assumed we had already removed all that weak symbol stuff from libstdc++ for __GLIBC_PREREQ (2, 34).
next prev parent reply other threads:[~2021-11-08 12:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-08 12:02 [Bug c++/103133] New: " loximann at gmail dot com 2021-11-08 12:17 ` [Bug libstdc++/103133] " redi at gcc dot gnu.org 2021-11-08 12:31 ` fw at gcc dot gnu.org [this message] 2021-11-08 12:47 ` rguenth at gcc dot gnu.org 2021-11-08 12:50 ` redi at gcc dot gnu.org 2021-11-08 12:51 ` redi at gcc dot gnu.org 2021-11-08 13:02 ` redi at gcc dot gnu.org 2021-11-10 12:04 ` cvs-commit at gcc dot gnu.org 2021-11-10 12:09 ` redi at gcc dot gnu.org 2021-11-12 10:28 ` redi at gcc dot gnu.org 2021-11-24 11:52 ` cvs-commit at gcc dot gnu.org 2021-11-24 11:55 ` redi at gcc dot gnu.org 2022-08-03 12:30 ` cvs-commit at gcc dot gnu.org 2022-08-03 13:33 ` redi at gcc dot gnu.org
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-103133-4-78rGWBl8tf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).