-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel toolchain doesn't correctly figure out LLVM name for Suse distributions #9515
Comments
Following PR fix that issue: bazel-contrib/toolchains_llvm#86 (waiting for merged that and then the issue will be closed) |
PR merged. 0.6 release from https://github.com/grailbio/bazel-toolchain/releases/tag/0.6 should be used in a system in order to fix that issue |
This is blocked by updating bazel to v4.0.0 then we can update to 0.6 of that toolchain. |
This is unblocked now, right @prestonvanloon ? |
This is fixed now that we have switched to the zig based toolchain, which does a much better job of loading the c++ compiler. Closed by #12135 |
🐞 Bug Report
Description
It isn't possible to install Prysm from the source (https://docs.prylabs.network/docs/install/install-with-bazel)
on Suse Linux distributions (leap, tumbleweed).
Bazel toolchain (https://github.com/grailbio/bazel-toolchain) currently doesn't correctly figure out the LLVM name for Suse distributions.
Has this worked before in a previous version?
Rather not but I didn't check all previous versions of the Bazel toolchain.
🔬 Minimal Reproduction
Precondition: Operating system - any of Suse distribution
Type
bazel build //beacon-chain:beacon-chain --config=release
in main Prysm folder.🔥 Error
🌍 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
The text was updated successfully, but these errors were encountered: