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: "iains 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 17:27:30 +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 #46 from Iain Sandoe <iains at gcc dot gnu.org> 2012-02-03 17:27:30 UTC ---
(In reply to comment #45)
> Then I think we have to disable __GTHREAD_RECURSIVE_MUTEX_INIT unconditionally
> on darwin.
I hope not.
putting -mmacosx-version-min=10.6 - will cause the macro value to be 1060 - so
defeating it. One would not expect it to run on 10.7.
If one puts -mmacosx-version-min=10.6 and sysroots to the 10.6 SDK - *and*
then transfers the executable to a 10.6 system - then that should work. If
not, then I agree.
> If the bug is later fixed in (say) 10.8 then we could use the init macro if
> MIN_REQUIRED >= 1080 since we know that it won't be run on a system where the
> bug is present.
Indeed.. let's hope its 107x rather than 1080 ...