public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at cornsyrup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52590] std::thread Segmentation fault static linking
Date: Wed, 14 Mar 2012 22:20:00 -0000 [thread overview]
Message-ID: <bug-52590-4-9cX7Sbub51@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52590-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52590
--- Comment #2 from Jason Toffaletti <jason at cornsyrup dot org> 2012-03-14 21:29:18 UTC ---
(In reply to comment #1)
> > -static
>
> You need to make sure all of libpthread.a is included, right it does not get
> linked that way.
>
> This is not a GCC or glibc bug.
Your comment seems to suggest there is a way, but I can't find it.
g++ -Wl,--whole-archive -static -pthread -std=c++0x -o thread thread.cc
Gives pages of linker errors.
http://sourceware.org/bugzilla/show_bug.cgi?id=10652 suggests glibc and
pthreads just don't work with static linking.
next prev parent reply other threads:[~2012-03-14 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 20:42 [Bug libstdc++/52590] New: " jason at cornsyrup dot org
2012-03-14 20:43 ` [Bug libstdc++/52590] " pinskia at gcc dot gnu.org
2012-03-14 22:20 ` jason at cornsyrup dot org [this message]
2012-03-15 4:47 ` jason at cornsyrup dot org
2012-03-15 7:52 ` jakub at gcc dot gnu.org
2022-03-09 17:40 ` redi at gcc dot gnu.org
2023-03-03 19:10 ` cvs-commit 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-52590-4-9cX7Sbub51@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).