[LLVMdev] Self compiling latest clang from SVN

[Russell Wallace]

I tried checking out the latest llvm/clang from SVN (as of a few hours ago)
and compiling it (clang 3.6.1 doesn't compile 3.7 because it fails a
version check, so I repeated the technique of compiling with Microsoft C++
first, then using the resulting clang-cl.exe). It fails with a bunch of
error messages along the lines of:

LLVMSupport.lib(Atomic.obj) : error LNK2019: unresolved external symbol
__faststorefence referenced in function "void __cdecl
llvm::sys::MemoryFence(void)" (?MemoryFence at sys@llvm@@YAXXZ)
[C:\llvm-svn\build\utils\FileCheck\FileCheck.vcxproj]
LLVMSupport.lib(Host.obj) : error LNK2019: unresolved external symbol
_xgetbv referenced in function "class llvm::StringRef __cdecl
llvm::sys::getHostCPUName(void)"
(?getHostCPUName at sys@llvm@@YA?AVStringRef at 2@XZ)
[C:\llvm-svn\build\utils\FileCheck\FileCheck.vcxproj]
LLVMSupport.lib(Host.obj) : error LNK2019: unresolved external symbol
__cpuidex referenced in function "class llvm::StringRef __cdecl
llvm::sys::getHostCPUName(void)"
(?getHostCPUName at sys@llvm@@YA?AVStringRef at 2@XZ)
[C:\llvm-svn\build\utils\FileCheck\FileCheck.vcxproj]

Anyone know what the problem is here?

More generally, is it considered useful to run these sort of tests on the
SVN version as we go along, or is it more the case that the SVN version is
expected to have bugs and it would be better to wait for a release
candidate?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150611/0fbeca55/attachment.html>