public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/41810] Cannot build gcc: gthr-default.h:466: error: '__mutex' was not declared in this scope Date: Tue, 17 Nov 2009 19:43:00 -0000 [thread overview] Message-ID: <20091117194312.18086.qmail@sourceware.org> (raw) In-Reply-To: <bug-41810-15602@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from ro at techfak dot uni-bielefeld dot de 2009-11-17 19:43 ------- Subject: Re: Cannot build gcc: gthr-default.h:466: error: '__mutex' was not declared in this scope > ------- Comment #3 from alanpae at ilkda dot com 2009-11-17 19:18 ------- [...] > Will try building it again with threads=none or the equivalent. Why are you building with --enable-threads=solaris in the first place? Just omit --enable-threads (defaulting to posix); the implementation of both on Solaris 2 is the same, anyway. It is beyond me why anyone would want to program to the old UI Threads interface. That said, I'm testing the obvious fix: Index: gcc/gthr-solaris.h =================================================================== --- gcc/gthr-solaris.h (revision 154216) +++ gcc/gthr-solaris.h (working copy) @@ -37,7 +37,7 @@ #include <errno.h> #ifdef __cplusplus -#define UNUSED(x) +#define UNUSED(x) x #else #define UNUSED(x) x __attribute__((unused)) #endif I've now idea what other problems with --enable-threads=solaris might exist, though. This isn't regularly tested. Rainer -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41810
next prev parent reply other threads:[~2009-11-17 19:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-23 16:58 [Bug libstdc++/41810] New: " YLitvinenko at astana dot oilfield dot slb dot com 2009-10-23 17:03 ` [Bug libstdc++/41810] " YLitvinenko at astana dot oilfield dot slb dot com 2009-10-23 18:14 ` [Bug target/41810] " paolo dot carlini at oracle dot com 2009-11-17 19:18 ` alanpae at ilkda dot com 2009-11-17 19:43 ` ro at techfak dot uni-bielefeld dot de [this message] 2009-11-18 7:03 ` YLitvinenko at astana dot oilfield dot slb dot com 2009-11-18 11:18 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2009-11-18 19:39 ` alanpae at ilkda dot com 2009-11-19 11:26 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2009-11-19 11:55 ` jakub at gcc dot gnu dot org 2009-11-20 17:10 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2009-11-20 17:17 ` ro at gcc dot gnu dot org 2009-11-27 15:17 ` ro at gcc dot gnu dot org [not found] <bug-41810-4@http.gcc.gnu.org/bugzilla/> 2011-07-18 16:25 ` ro 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=20091117194312.18086.qmail@sourceware.org \ --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).