You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using rust_register_toolchains, if I use dev_components = True and ios (or android) in extra_target_triples, I get this error during a bazel build:
ERROR: An error occurred during the fetch of repository 'rust_linux_x86_64__aarch64-linux-android__nightly_tools':
Traceback (most recent call last):
File "/home/runner/.cache/bazel/_bazel_runner/1fa4b8b6e5f813a6f30004917b5fca72/external/rules_rust/rust/repositories.bzl", line 374, column 31, in _rust_toolchain_tools_repository_impl
load_rustc_dev_nightly(ctx, target_triple)
File "/home/runner/.cache/bazel/_bazel_runner/1fa4b8b6e5f813a6f30004917b5fca72/external/rules_rust/rust/private/repository_utils.bzl", line 582, column 24, in load_rustc_dev_nightly
load_arbitrary_tool(
File "/home/runner/.cache/bazel/_bazel_runner/1fa4b8b6e5f813a6f30004917b5fca72/external/rules_rust/rust/private/repository_utils.bzl", line 733, column 42, in load_arbitrary_tool
result = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://static.rust-lang.org/dist/2024-02-22/rustc-dev-nightly-aarch64-linux-android.tar.xz] to /home/runner/.cache/bazel/_bazel_runner/1fa4b8b6e5f813a6f30004917b5fca72/external/rust_linux_x86_64__aarch64-linux-android__nightly_tools/temp11823504000632298494/rustc-dev-nightly-aarch64-linux-android.tar.xz: GET returned 404 Not Found
When using
rust_register_toolchains
, if I usedev_components = True
and ios (or android) inextra_target_triples
, I get this error during abazel build
:Here is how I use rust_rules:
I added some prints in
rust/repositories.bzl
and I discovered that 49 toolchains were being declared:Which is the cartesian product between my
extra_target_triples
and rules_rust'sDEFAULT_TOOLCHAIN_TRIPLES
I was able to fix my problem by patching the rules_rust
http_archive
this way:Is there a way for me to avoid that problem without relying on a rules_rust patch?
The text was updated successfully, but these errors were encountered: