public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53270] Error when bootstrapping gcc on hppa2.0-unknown-linux-gcc
Date: Wed, 09 May 2012 17:18:00 -0000 [thread overview]
Message-ID: <bug-53270-4-EBZyKd4vEh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53270-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53270
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-09 17:12:14 UTC ---
(In reply to comment #12)
> You might try configuring with "--disable-libstdcxx-threads". It
> disables C++11 threads support.
guard.cc is always built, it's part of libsupc++ so it's nothing to do with the
C++11 thread library.
I'm pretty sure we've already dealt with this failure elsewhere, IIRC the
linuxthreads pthread_mutex_t type has a volatile member causing the default
assignment operator to be deleted.
For PR 51296 I added a way to force use of __GTHREAD_MUTEX_INIT_FUNCTION, by
defining _GTHREAD_USE_MUTEX_INIT_FUNC in
libstdc++-v3/config/os/.../os_defines.h
We might want to put something in config/os/gnu-linux/os_defines.h so that the
macro is defined when using linuxthreads
next prev parent reply other threads:[~2012-05-09 17:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 20:31 [Bug libstdc++/53270] New: " jimis at gmx dot net
2012-05-07 20:38 ` [Bug libstdc++/53270] " jimis at gmx dot net
2012-05-07 23:21 ` danglin at gcc dot gnu.org
2012-05-08 0:00 ` jimis at gmx dot net
2012-05-08 1:37 ` danglin at gcc dot gnu.org
2012-05-08 6:38 ` jimis at gmx dot net
2012-05-08 6:39 ` jimis at gmx dot net
2012-05-08 6:43 ` jimis at gmx dot net
2012-05-08 15:21 ` danglin at gcc dot gnu.org
2012-05-08 19:01 ` steven at gcc dot gnu.org
2012-05-08 19:24 ` steven at gcc dot gnu.org
2012-05-08 19:32 ` dave.anglin at bell dot net
2012-05-08 21:37 ` danglin at gcc dot gnu.org
2012-05-09 4:47 ` jimis at gmx dot net
2012-05-09 17:18 ` redi at gcc dot gnu.org [this message]
2012-05-09 19:04 ` dave.anglin at bell dot net
2012-05-10 0:42 ` jimis at gmx dot net
2012-05-10 0:56 ` jimis at gmx dot net
2012-05-10 3:50 ` dave.anglin at bell dot net
2012-05-18 14:23 ` jimis at gmx dot net
2012-05-18 14:23 ` jimis at gmx dot net
2012-05-18 14:28 ` jimis at gmx dot net
2012-05-18 17:32 ` redi at gcc dot gnu.org
2012-05-18 17:39 ` jimis at gmx dot net
2012-05-18 17:40 ` redi at gcc dot gnu.org
2012-05-18 17:42 ` jimis at gmx dot net
2012-05-18 17:44 ` jimis at gmx dot net
2012-05-19 6:19 ` redi at gcc dot gnu.org
2012-05-20 11:34 ` jimis at gmx dot net
2012-05-20 15:36 ` dave.anglin at bell dot net
2012-06-05 18:33 ` redi at gcc dot gnu.org
2012-06-09 12:26 ` redi at gcc dot gnu.org
2012-06-14 22:21 ` redi at gcc dot gnu.org
2012-06-14 22:26 ` redi at gcc dot gnu.org
2012-06-19 7:42 ` redi at gcc dot gnu.org
2012-06-19 11:15 ` [Bug libstdc++/53270] [4.6/4.7 Regression] " redi at gcc dot gnu.org
2012-07-16 21:57 ` redi at gcc dot gnu.org
2012-07-16 22:34 ` redi at gcc dot gnu.org
2012-07-16 22:35 ` [Bug libstdc++/53270] [4.6 " redi at gcc dot gnu.org
2012-07-22 16:46 ` redi at gcc dot gnu.org
2012-07-22 16:48 ` 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-53270-4-EBZyKd4vEh@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).