public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lightningdzeyenr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104852] std::[j]thread::detach() still gives segmentation faults with glibc 2.34
Date: Wed, 09 Mar 2022 17:42:23 +0000 [thread overview]
Message-ID: <bug-104852-4-X9TMyeo9vv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104852-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104852
--- Comment #4 from Jackson Huff <lightningdzeyenr at gmail dot com> ---
(In reply to Jonathan Wakely from comment #2)
> For distros other than Red Hat (and Fedora, CentOS etc.) you need to use:
>
> -Wl,--whole-archive -lpthread -Wl,--no-whole-archive
>
> Otherwise the pthread symbols do not get pulled in by the linker.
This would seem like a fix, but applying those flags to both the ADD_FLAGS
variable and both manually specifying then in CMakeLists.txt made no difference
(I tried variations for hours but no dice).
next prev parent reply other threads:[~2022-03-09 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 4:13 [Bug libstdc++/104852] New: " lightningdzeyenr at gmail dot com
2022-03-09 4:16 ` [Bug libstdc++/104852] " lightningdzeyenr at gmail dot com
2022-03-09 17:36 ` redi at gcc dot gnu.org
2022-03-09 17:40 ` redi at gcc dot gnu.org
2022-03-09 17:42 ` lightningdzeyenr at gmail dot com [this message]
2022-03-09 17:46 ` lightningdzeyenr at gmail dot com
2022-03-09 18:55 ` redi at gcc dot gnu.org
2022-03-09 19:18 ` redi at gcc dot gnu.org
2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org
2023-03-03 19:39 ` aoliva 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-104852-4-X9TMyeo9vv@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: 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).