Closed gitttt closed 8 years ago
I confirm the problem, a workaround, rebuild with verbose: VERBOSE=1 TOOL_VERBOSE=1 make -f ../news2e/Makefile Then identify the failing command and relaunch it by hand: make -C /home/vagrant/projects/news2e-build/llvm-3.2.src.native/projects/compiler-rt \ ProjSrcRoot=/home/vagrant/projects/news2e-build/llvm-3.2.src.native/projects/compiler-rt \ ProjObjRoot=/home/vagrant/projects/news2e-build/llvm-native/tools/clang/runtime/compiler-rt \ CC="/home/vagrant/projects/news2e-build/llvm-native/Release/bin/clang" \ LLVM_ANDROID_TOOLCHAIN_DIR="" \ clang_linux
Strangely this succeeds and allows to relaunch the compilation ( i.e. make -f ../news2e/Makefile again). This seem to be a known problem with the path: https://groups.google.com/forum/#!topic/llvm-dev/U4gGLywLwu0
I added a step to the provisioning script to restart the build. While being an ugly workaround, this should fix the problem for now.
When trying to build the vagrant machine: