Skip to content
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

Closed
pgagala opened this issue Sep 2, 2021 · 6 comments · Fixed by #12135
Closed

Bazel toolchain doesn't correctly figure out LLVM name for Suse distributions #9515

pgagala opened this issue Sep 2, 2021 · 6 comments · Fixed by #12135
Assignees

Comments

@pgagala
Copy link

pgagala commented Sep 2, 2021

🐞 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




➜  prysm git:(develop) bazel build //beacon-chain:beacon-chain --config=release
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Repository llvm_toolchain instantiated at:
  /home/pgagala/go-projects/src/prysm/WORKSPACE:29:15: in 
Repository rule llvm_toolchain defined at:
  /home/pgagala/.cache/bazel/_bazel_pgagala/f80ecb809416ccd6b5020a2975b0b48e/external/com_grail_bazel_toolchain/toolchain/rules.bzl:24:33: in 
ERROR: An error occurred during the fetch of repository 'llvm_toolchain':
   Traceback (most recent call last):
        File "/home/pgagala/.cache/bazel/_bazel_pgagala/f80ecb809416ccd6b5020a2975b0b48e/external/com_grail_bazel_toolchain/toolchain/internal/configure.bzl", line 110, column 37, in llvm_toolchain_impl
                _download_llvm_preconfigured(rctx)
        File "/home/pgagala/.cache/bazel/_bazel_pgagala/f80ecb809416ccd6b5020a2975b0b48e/external/com_grail_bazel_toolchain/toolchain/internal/llvm_distributions.bzl", line 177, column 13, in download_llvm_preconfigured
                fail("Unknown LLVM release: %s\nPlease ensure file name is correct." % basename)
Error in fail: Unknown LLVM release: clang+llvm-10.0.0-x86_64-linux-sles20210714.tar.xz
Please ensure file name is correct.
ERROR: no such package '@llvm_toolchain//': Unknown LLVM release: clang+llvm-10.0.0-x86_64-linux-sles20210714.tar.xz
Please ensure the file name is correct.
INFO: Elapsed time: 4.771s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

🌍 Your Environment

Operating System:

  
NAME="openSUSE Tumbleweed"
VERSION="20210714"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20210714"
PRETTY_NAME="openSUSE Tumbleweed"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20210714"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
  

What version of Prysm are you running? (Which release)

  
Version from develop branch commit hash: 95e07963fb920754536f91c4495bce8223f801b0
  
@pgagala
Copy link
Author

pgagala commented Sep 2, 2021

Following PR fix that issue: bazel-contrib/toolchains_llvm#86 (waiting for merged that and then the issue will be closed)

@rkapka rkapka assigned rkapka and pgagala and unassigned rkapka Sep 9, 2021
@pgagala
Copy link
Author

pgagala commented Oct 11, 2021

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

@rkapka
Copy link
Contributor

rkapka commented Oct 11, 2021

cc @prestonvanloon

@prestonvanloon
Copy link
Member

This is blocked by updating bazel to v4.0.0 then we can update to 0.6 of that toolchain.

@rkapka
Copy link
Contributor

rkapka commented Oct 20, 2021

This is unblocked now, right @prestonvanloon ?

@prestonvanloon prestonvanloon linked a pull request Jan 5, 2022 that will close this issue
@prestonvanloon
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants