We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 vendor
bazel vendor --vendor_dir=... fails due to ERROR: key "linux-arm64-gnu" not found in dictionary.
bazel vendor --vendor_dir=...
ERROR: key "linux-arm64-gnu" not found in dictionary
This is related to #289, and is caused by the upstream bug swc-project/swc#9769.
In short, upstream stopped publishing releases for linux-arm64-gnu after v1.7.14. The only other 64-bit ARM Linux Release is swc-linux-arm64-musl.
linux-arm64-gnu
swc-linux-arm64-musl
Also, it looks like some tests are missing. Somehow a 32-bit ARM Linux artifact made its way into TOOL_VERSIONS:
TOOL_VERSIONS
rules_swc/swc/private/versions.bzl
Line 8 in 1e339ca
But there is no 32-bit ARM Linux platform:
rules_swc/swc/private/toolchains_repo.bzl
Lines 39 to 50 in 1e339ca
Development (host) and target OS/architectures: 64-bit macOS Apple M2 and Intel
Output of bazel --version: bazel 8.0.1
bazel --version
Version of the Aspect rules, or other relevant rules from your WORKSPACE or MODULE.bazel file: 2.3.0
WORKSPACE
MODULE.bazel
Language(s) and/or frameworks involved: N/A
1. Clone https://github.com/amari/rules_swc_repro 2. Run `bazel vendor --vendor_dir=vendor`
bazel vendor pulls in all the toolchains regardless of constraint matching, so it would serve as a good basis for a test.
IIRC the *-gnu and *-musl ABIs have/expect different libc.so paths, so I'd expect things to break catastrophically if they were simply substituted.
*-gnu
*-musl
libc.so
I don't have an environment to test this.
The quickest remedy would be to drop support for 64-bit ARM Linux and add it again after proper testing has been done.
The text was updated successfully, but these errors were encountered:
Have you tried running bazel vendor with a target pattern such as //...? That would avoid the download of toolchains for other platforms.
//...
Sorry, something went wrong.
No branches or pull requests
What happened?
bazel vendor --vendor_dir=...
fails due toERROR: key "linux-arm64-gnu" not found in dictionary
.This is related to #289, and is caused by the upstream bug swc-project/swc#9769.
In short, upstream stopped publishing releases for
linux-arm64-gnu
after v1.7.14. The only other 64-bit ARM Linux Release isswc-linux-arm64-musl
.Also, it looks like some tests are missing. Somehow a 32-bit ARM Linux artifact made its way into
TOOL_VERSIONS
:rules_swc/swc/private/versions.bzl
Line 8 in 1e339ca
But there is no 32-bit ARM Linux platform:
rules_swc/swc/private/toolchains_repo.bzl
Lines 39 to 50 in 1e339ca
Version
Development (host) and target OS/architectures: 64-bit macOS Apple M2 and Intel
Output of
bazel --version
: bazel 8.0.1Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file: 2.3.0Language(s) and/or frameworks involved:
N/A
How to reproduce
1. Clone https://github.com/amari/rules_swc_repro 2. Run `bazel vendor --vendor_dir=vendor`
Any other information?
bazel vendor
pulls in all the toolchains regardless of constraint matching, so it would serve as a good basis for a test.IIRC the
*-gnu
and*-musl
ABIs have/expect differentlibc.so
paths, so I'd expect things to break catastrophically if they were simply substituted.I don't have an environment to test this.
The quickest remedy would be to drop support for 64-bit ARM Linux and add it again after proper testing has been done.The text was updated successfully, but these errors were encountered: