Closed aranguyen closed 8 months ago
I'm not able to build rules_cc
on my machine and got this error ERROR: /Users/aranguyen/rules_cc/examples/custom_toolchain/BUILD:81:19: in cc_toolchain_suite rule //examples/custom_toolchain:legacy_selector: cc_toolchain_suite '//examples/custom_toolchain:legacy_selector' does not contain a toolchain for cpu 'darwin'
If someone could guide me to build rules_cc
, I could help with the deps update.
We should get rid of the federation indirection. No one is actively maintaining that so it becomes a boondoggle.
Without addressing removing the federation indirction, I think #142 is a fix.
Stale
Description of the problem / feature request:
The flag
--incompatible_use_platforms_repo_for_constraints
has been flipped and we're seeing CI failures inrules_cc
for downstream pipeline https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2600#_Issue: https://github.com/bazelbuild/continuous-integration/issues/1404
Feature requests: what underlying problem are you trying to solve with this feature?
My quick analysis points to the remaining references of
bazel_tools//platforms
inio_bazel_rules_go
. Sincerules_go
came frombazel_federation
https://github.com/bazelbuild/rules_cc/blob/ddc0791fa66deaf3d70925fbc8048e5b0e2fe999/internal_deps.bzl#L17 , please do the following: 1) Make a PR to updatebazel_federation
with the most recentrules_go
https://github.com/bazelbuild/bazel-federation/blob/8ce885a3a89da83228cd845c6ab13bb0175ca105/repositories.bzl#L161 2) Make a PR to updatebazel_federation
to the most recent commit with updatedrules_go
https://github.com/bazelbuild/rules_cc/blob/cb6d32e4d1ae29e20dd3328109d8cb7f8eccc9be/WORKSPACE#L6Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
What's the output of
bazel info release
?release 5.2.0
What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
rules_cc at HEAD