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

No toolchain after 19.1.0 can be downloaded #417

Open
arvid-norlander opened this issue Nov 8, 2024 · 3 comments
Open

No toolchain after 19.1.0 can be downloaded #417

arvid-norlander opened this issue Nov 8, 2024 · 3 comments

Comments

@arvid-norlander
Copy link

bazel_dep(name = "toolchains_llvm", version = "1.2.0")
llvm = use_extension("@toolchains_llvm//toolchain/extensions:llvm.bzl", "llvm")
llvm.toolchain(
    llvm_version = "19.1.0",
)
use_repo(llvm, "llvm_toolchain")

works, but this does not:

bazel_dep(name = "toolchains_llvm", version = "1.2.0")
llvm = use_extension("@toolchains_llvm//toolchain/extensions:llvm.bzl", "llvm")
llvm.toolchain(
    llvm_version = "19.1.3",
)
use_repo(llvm, "llvm_toolchain")

Yet https://github.com/llvm/llvm-project/releases/tag/llvmorg-19.1.3 is the most recent release as of writing this. The error is as follows:

INFO: Repository toolchains_llvm~~llvm~llvm_toolchain_llvm instantiated at:
  <builtin>: in <toplevel>
Repository rule llvm defined at:
  /home/USER/.cache/bazel/_bazel_USER/01afa9c2444d0e5461c9c78c1470582d/external/toolchains_llvm~/toolchain/rules.bzl:27:23: in <toplevel>
ERROR: An error occurred during the fetch of repository 'toolchains_llvm~~llvm~llvm_toolchain_llvm':
   Traceback (most recent call last):
        File "/home/USER/.cache/bazel/_bazel_USER/01afa9c2444d0e5461c9c78c1470582d/external/toolchains_llvm~/toolchain/internal/repo.bzl", line 311, column 35, in llvm_repo_impl
                updated_attrs = _download_llvm(rctx)
        File "/home/USER/.cache/bazel/_bazel_USER/01afa9c2444d0e5461c9c78c1470582d/external/toolchains_llvm~/toolchain/internal/llvm_distributions.bzl", line 617, column 56, in download_llvm
                urls, sha256, strip_prefix = _distribution_urls(rctx)
        File "/home/USER/.cache/bazel/_bazel_USER/01afa9c2444d0e5461c9c78c1470582d/external/toolchains_llvm~/toolchain/internal/llvm_distributions.bzl", line 660, column 13, in _distribution_urls
                fail("Unknown LLVM release: %s\nPlease ensure file name is correct." % basename)
Error in fail: Unknown LLVM release: LLVM-19.1.3-Linux-X64.tar.xz
Please ensure file name is correct.
ERROR: no such package '@@toolchains_llvm~~llvm~llvm_toolchain_llvm//': Unknown LLVM release: LLVM-19.1.3-Linux-X64.tar.xz
Please ensure file name is correct.
ERROR: /home/USER/.cache/bazel/_bazel_USER/01afa9c2444d0e5461c9c78c1470582d/external/toolchains_llvm~~llvm~llvm_toolchain/BUILD.bazel:203:14: @@toolchains_llvm~~llvm~llvm_toolchain//:clang-tidy depends on @@toolchains_llvm~~llvm~llvm_toolchain_llvm//:bin/clang-tidy in repository @@toolchains_llvm~~llvm~llvm_toolchain_llvm which failed to fetch. no such package '@@toolchains_llvm~~llvm~llvm_toolchain_llvm//': Unknown LLVM release: LLVM-19.1.3-Linux-X64.tar.xz
Please ensure file name is correct.

Looking at it, I don't think they changed the naming scheme, but something clearly broke.

@jwbee
Copy link

jwbee commented Nov 25, 2024

Is this just because the artifacts trickle in after the fact? It looks like the archive is there now, for 19.1.3.

For ARM the situation is worse. The last upstream release with linux-aarch64 binaries is 18.1.8.

@jwbee
Copy link

jwbee commented Nov 25, 2024

Ah no, I see the issue: you are using this repo at v1.2.0 but the compiler you want is newer! You need to use toolchains_llvm at master or the master commit to get those newer archives.

@arvid-norlander
Copy link
Author

Ah I see, I would have assumed I could use the latest version of LLVM, since the upstream archives follow a predictable naming scheme. I guess the reason then is to handle checksums? What is the release cadence of this repo?

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

No branches or pull requests

2 participants