Open sgowroji opened 1 month ago
Thanks for the report! Esp thanks for the repro steps with USE_BAZEL_VERSION, super helpful.
I found the migration guide linked from the culprit a lacking here. It just says _"If you are depending on anything in @bazel_tools//tools/cpp, you should use the version from @rulescc instead." - IIUC this dependency came from the PR that migrated glog to bzlmod, but I figured I'd take a shot at migrating it.
no repo visible as '@rules_cc' here
bazel_dep(name = "rules_cc", version = "0.0.12")
from https://github.com/bazelbuild/bazel/commit/1c4e78a9ceab9794140324d64833c628e382a3da, fails with no such package '@@rules_cc+//tools/cpp'
"@rules_cc//cc/private/toolchain:clang-cl"
and "@rules_cc//cc:extensions.bzl"
from the above commit, fails with ERROR: /usr/local/google/home/rodrigoq/git/glog/BUILD.bazel:7:13: While resolving toolchains for target //:strip_include_prefix_hack (77ef3ef): invalid registered toolchain '@local_config_cc//:cc-toolchain-x64_windows-clang-cl': no such target '@@rules_cc++cc_configure_extension+local_config_cc//:cc-toolchain-x64_windows-clang-cl': target 'cc-toolchain-x64_windows-clang-cl' not declared in package '' defined by /usr/local/google/home/rodrigoq/.cache/bazel/_bazel_rodrigoq/dd880f2ce084c0dadd188a0a46eacfcd/external/rules_cc++cc_configure_extension+local_config_cc/BUILD
.Created https://github.com/google/glog/pull/1136 and hoping I'm on the right track given that I don't have a way to actually test the fix.
CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4200#01928e5d-1434-461c-a9de-dd55737653e3
Platform: Windows
Logs:
Culprit: https://github.com/bazelbuild/bazel/commit/1c4e78a9ceab9794140324d64833c628e382a3da
Steps:
CC Greenteam @meteorcloudy