toolchains_llvm
toolchains_llvm copied to clipboard
bazel-contrib
LLVM toolchain for bazel
The one at the root of the repo isn't very interesting, the one with the sysroot toolchain defined lives in `tests` (as they were split [here](https://github.com/grailbio/bazel-toolchain/commit/489dbca4808ffd0bf2ed81a93bbea03ab1bb9d5b))
This project has been super helpful for configuring toolchains. I've made some pretty extensive changes, adding support for: * Cross compilation (tested from Linux to Linux in both directions between...
(this PR builds on #75; that PR should be reviewed/merged before this one) This PR is not ready for merging yet but I thought I'd open the PR anyways to...
Manjaro is based on Arch and the toolchain to use should be similar to arch and not ubuntu. Currently for the LLVM 10 toolchain I got the following error: ```...
Currently, the container [tests in our CI](https://github.com/grailbio/bazel-toolchain/runs/6015015149?check_suite_focus=true) are failing for Leap and Tumbleweed with messages like: ``` ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol 'stdout'; recompile with -fPIC...
We should test if our builds are bytewise reproducible with the default flags. An example of such a test is [in rules_r](https://github.com/grailbio/rules_r/blob/master/tests/repro/repro_test.sh). I think because we are not setting `ZERO_AR_DATE=1`...
Google folks have contributed Bazel support for LLVM in the llvm-project tree. The full configuration could be found here https://github.com/llvm/llvm-project/tree/main/utils/bazel and sample usages could be found here https://github.com/llvm/llvm-project/blob/main/utils/bazel/examples/http_archive/WORKSPACE It seems...
I just got an M1 MacBook Pro today, and am looking into how to use this project to generate arm64 binaries (for the record: everything works fine using this project...
My understanding is that [`--fission`](https://docs.bazel.build/versions/main/user-manual.html#flag--fission) is supposed to be a cross-platform way to generate separate debug info files for C/C++ rules (this is definitely stretching it a bit; I think...
H/t to @vinistock for finding [this issue](https://github.com/grailbio/bazel-toolchain/issues/88#issuecomment-1021579070). The below is mostly copied from #88; the issue is essentially that we're parsing `-install_path @executable_path/...` and similar flags as param files, incorrectly....