public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3 Date: Thu, 09 Mar 2023 11:28:00 +0000 [thread overview] Message-ID: <bug-109074-4-Gpfz7wwZ79@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109074-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109074 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|MOVED |INVALID --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually there is no bug here. With older versions of glibc, you need to link against libpthread to get threads in general. This is true with any version of gcc.
next prev parent reply other threads:[~2023-03-09 11:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-09 6:56 [Bug c++/109074] New: " murugesandins at gmail dot com 2023-03-09 10:20 ` [Bug c++/109074] " rguenth at gcc dot gnu.org 2023-03-09 11:28 ` pinskia at gcc dot gnu.org [this message] 2023-03-09 11:30 ` pinskia at gcc dot gnu.org 2023-03-10 4:34 ` [Bug libstdc++/109074] " murugesandins at gmail dot com 2023-03-10 4:53 ` murugesandins at gmail dot com 2023-03-10 5:01 ` pinskia at gcc dot gnu.org 2023-03-10 5:26 ` murugesandins at gmail dot com 2023-03-10 10:32 ` redi at gcc dot gnu.org 2023-03-10 21:30 ` murugesandins at gmail dot com 2023-03-10 23:20 ` murugesandins at gmail dot com 2023-03-10 23:30 ` pinskia at gcc dot gnu.org 2023-03-12 20:52 ` redi at gcc dot gnu.org 2023-03-13 3:30 ` murugesandins 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-109074-4-Gpfz7wwZ79@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).