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: "mikestump at comcast dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 03 Feb 2012 20:44:16 +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 #52 from Mike Stump <mikestump at comcast dot net> 2012-02-03 20:44:16 UTC ---
> OK. I'd missed that - in which case no objection to the unconditional disable
> from me.
We can even fixincludes it away! I'm fine with #undef or some such... I think
that is a good way forward. If they would fix it in a .x minor OS release, I'm
fine with simply requiring the user update their system as well, though, I
wouldn't holds ones breath for the update.