search for: bulidbot

...shared object; recompile with -fPIC > ../../lib/libLLVMAArch64CodeGen.a: could not read symbols: Bad value > clang-3.4: error: linker command failed with exit code 1 (use -v to > see invocation) > [ 95%] make[2]: *** [lib/libLTO.so] Error 1 > > The same can be seen on some of our bulidbots (those that use Clang and > CMake). This *could* be the same thing I suppose... If my fix actually helps, please let me know. But I don't completely see how this particular error happens so I'll be intrigued. -------------- next part -------------- An HTML attachment was scrubbed... U...

Chandler, I may be doing this wrong, but I'm getting a weird error in building LLVM with Clang via CMake. On x86_64: $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True On ARM: $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../install

Hi, I would like to start using GitHub Actions[1] for CI testing on the release/* branches. As far as I know we don't have any buildbots listening to the release branches, and I think GitHub Actions are a good way for us to quickly bring-up some CI jobs there. My proposal is to start by adding two post-commit CI jobs to the release/9.x branch. One for building and testing (ninja checka-all)