http://llvm.org/bugs/show_bug.cgi?id=18322
Bug ID: 18322
Summary: test/Headers/cxx11.cpp is failing on OS X 10.9
Mavericks
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++11
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Classification: Unclassified
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20131202/094538.html
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20131202/094539.html
"""
On Mon, Dec 2, 2013 at 5:58 PM, Rafael Espíndola <[email protected]>
wrote:
> looks like this found a real issue with OS X 10.9's headers.
I agree that this looks like a bug in the headers; it looks like
sys/_types/_wchar_t.h should probably not be specified as a separate submodule,
since including it in an 'extern "C" {' suggests that it's just a fragment of
text rather than an actual submodule.
> Should we just xfail the test?
That fixes the test, but does nothing for people who are using Clang SVN on Mac
OS with older (incompatible) modules. We need to figure out how to handle that
case. Maybe we should include a version number in module.map files, and ignore
module.maps that don't specify the right version?
> Including a system header (<stdint.h>) in a
> clang test seems like a bad idea, no?
Well... the point of this test is to ensure that we do the right thing when our
own <stdint.h> #include_next's the system one. We should probably change the
test to get that effect a different way (for instance, by providing a fake
sysroot with a fake <stdint.h>).
"""
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
