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 CI] Error toolchain_config_utils.bzl' is invalid because 'cc/toolchains' is not a package #266

Open
sgowroji opened this issue Oct 17, 2024 · 2 comments

Comments

@sgowroji
Copy link
Member

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4205#019298aa-849f-4471-85cc-a73fde9e8b96

Platform: MacOS

Logs:

ERROR: Error computing the main repository mapping: at /private/var/tmp/_bazel_buildkite/329b41a3c1f921e4a88581c508c63727/external/bazel_tools/tools/cpp/cc_configure.bzl:18:6: Label '@@rules_cc//cc/toolchains:toolchain_config_utils.bzl' is invalid because 'cc/toolchains' is not a package; perhaps you meant to put the colon here: '@@rules_cc//cc:toolchains/toolchain_config_utils.bzl'?

Culprit: bazelbuild/bazel@1c4e78a

Steps:

git clone https://github.com/bazelbuild/rules_android
git reset 4cfa8833a15808f6d8675658c5fc032549b85d9f  --hard
export USE_BAZEL_VERSION=1d022f403d26505d6edda73a50e08da53109dd3b
bazel build --enable_bzlmod --enable_workspace  -- //android/... //src/... -//src/java/com/example/sampleapp/... //test/... -//test/rules/... //toolchains/... //tools/... -//tools/android/... 

CC Greenteam @meteorcloudy

@ted-xie
Copy link
Contributor

ted-xie commented Oct 18, 2024

I get a completely different set of errors related to things like the deletiong of native sh_binary in Bazel. The error reported here doesn't show up for me (or maybe my build couldn't even get that far). I'm also building on Linux, but a repo mapping error like what's reported here should be platform-agnostic...

@ted-xie
Copy link
Contributor

ted-xie commented Oct 25, 2024

I was eventually able to reproduce this after fixing a bunch of other errors. This should be fixed when #269 eventually lands.

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