The failure is because you pass -std=c++0x, but MS's headers indirectly included by config_info use C++14 features. Should work with -std=c++14.
Actually no, it was because I needed to set _MSC_VER using -fmsc-version=1910. using clang : 4.0 : "C:/LLVM/bin/clang.exe" : <compileflags>-fmsc-version=1910 <linkflags>-v ; And now it fails to link with the usual mysterious clang-linux.link ..\..\bin.v2\libs\preprocessor\test\config_info.test\clang-linux-4.0\debug\config_info.exe clang version 4.0.0 (tags/RELEASE_400/final) Target: i686-pc-windows-msvc Thread model: posix InstalledDir: C:\LLVM\bin "link.exe" "-out:..\\..\\bin.v2\\libs\\preprocessor\\test\\config_info.test\\clang-linux-4.0\\debug\\config_info.exe" -defaultlib:libcmt -nologo -debug --start-group "..\\..\\bin.v2\\libs\\preprocessor\\test\\config_info.test\\clang-linux- 4.0\\debug\\config_info.obj" -Bstatic -Bdynamic --end-group clang.exe: error: unable to execute command: program not executable clang.exe: error: linker command failed with exit code 1 (use -v to see invocation) about which problem I can't find anything sensible.
Not sure why you'd want to use clang-win at present; I use clang-linux for everything.
So here's why, I suppose. Either way, I can't link, but at least the PP lib works (once the __GNUC__ checks are removed).