This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 03 Feb 2012 08:46:20 +0000
- Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- Auto-submitted: auto-generated
- References: <bug-51906-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906
--- Comment #40 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-03 08:46:20 UTC ---
Created attachment 26558
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26558
disable __GTHREAD_RECURSIVE_MUTEX_INIT for Lion
Thanks, Iain.
I'm thinking of something like this, which allows os_defines.h to set a macro
which forces gthreads to use the init function if the macro is known to be
problematic. This should work for PR 51296 too