[cfe-dev] [LLVMdev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>

[Nikola Smiljanic]

>
>
> I'll probably open a bug on this, but I just tried using clang.exe 3.5.0
> built with either MSVC or MinGW-w64-win32threads. When built with
> MinGW-w64,
> clang.exe is too promiscuous in terms of where it picks up system headers.
> It found a set of mingw.org headers installed elsewhere on my system
> (definitely not on my path) which it proceeded to error on:
>
>
I think we already have a bug http://llvm.org/bugs/show_bug.cgi?id=18546.
Clang driver never had proper support for MinGW.



> So, would love if clang could be a more self-sufficient toolchain and stop
> picking up headers from strange places that just happened to be sitting on
> my hard drive in the default install location, since those headers were not
> used to build clang at all.
>
>
I was under the impression that we were trying to move a away from this
"clang picks up headers from the toolchain it was built with" logic?
Clang's default triple is determined at configure time which is a bit
unfortunate. I think most people would agree that msvc compatible triple
should be the default for windows version of clang.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140925/d18678ec/attachment.html>