Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
- Add this new target to the root BUILD file.
platform(
name="darwin_arm64",
constraint_values= [
"@platforms//os:macos",
"@platforms//cpu:arm64",
],
visibility = ["//visibility:public"],
)$ USE_BAZEL_VERSION=last_green bazelisk build --cpu=darwin_arm64 --platforms=//:darwin_arm64 //src:bazel
What operating system are you running Bazel on?
macOS 11.0.1 (Intel cpu)
What's the output of bazel info release?
2020/12/08 06:35:42 Using unreleased version at commit a1b19dfa09abe6d7d3b62f2253e4bfa718aec089
INFO: Invocation ID: 102faae3-4a02-497c-a296-94f262246490
development version
If bazel info release returns "development version" or "(@Non-Git)", tell us how you built Bazel.
I use Bazelisk.
What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?
https://github.com/bazelbuild/bazel.git
f8f66f36ad299a0ea019c94100d5a8e2018f5ab5
f8f66f36ad299a0ea019c94100d5a8e2018f5ab5
Any other information, logs, or outputs that you want to share?
2020/12/08 06:34:15 Using unreleased version at commit a1b19dfa09abe6d7d3b62f2253e4bfa718aec089
2020/12/08 06:34:15 Downloading https://storage.googleapis.com/bazel-builds/artifacts/macos/a1b19dfa09abe6d7d3b62f2253e4bfa718aec089/bazel...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 57f11e01-ca6d-451e-b5ba-5f55d36295ab
DEBUG: /private/var/tmp/_bazel_admin/058bf0aeee6f9b65e93a9de41f4a4c2c/external/bazel_toolchains/rules/rbe_repo/version_check.bzl:59:14:
Current running Bazel is not a release version and one was not defined explicitly in rbe_autoconfig target. Falling back to '3.1.0'
DEBUG: /private/var/tmp/_bazel_admin/058bf0aeee6f9b65e93a9de41f4a4c2c/external/bazel_toolchains/rules/rbe_repo/checked_in.bzl:103:14: rbe_ubuntu1804_java11 not using checked in configs as detect_java_home was set to True
DEBUG: /private/var/tmp/_bazel_admin/058bf0aeee6f9b65e93a9de41f4a4c2c/external/bazel_toolchains/rules/rbe_repo/version_check.bzl:59:14:
Current running Bazel is not a release version and one was not defined explicitly in rbe_autoconfig target. Falling back to '3.1.0'
DEBUG: /private/var/tmp/_bazel_admin/058bf0aeee6f9b65e93a9de41f4a4c2c/external/bazel_toolchains/rules/rbe_repo/checked_in.bzl:103:14: rbe_ubuntu1604_java8 not using checked in configs as detect_java_home was set to True
ERROR: While resolving toolchains for target //src/main/cpp:client: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
ERROR: Analysis of target '//src:bazel' failed; build aborted: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
INFO: Elapsed time: 12.898s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (101 packages loaded, 741 targets configured)
Bugs: 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?
macOS 11.0.1 (Intel cpu)
What's the output of
bazel info release?If
bazel info releasereturns "development version" or "(@Non-Git)", tell us how you built Bazel.I use Bazelisk.
What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD?Any other information, logs, or outputs that you want to share?