-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Failed to detect cc toolchain when cross-compiling from darwin_x86_64 to darwin_arm64 with --platforms #12655
Comments
There's a dummy cc toolchain that should have been picked up and been unused (since Need to debug and figure out why. |
Apparently the dummy toolchainwas successfully removed, which means there's nothing left to be resolved. Are you compiling on a Mac (with xcode tools)? We should be able to configure those to handle an arm64/darwin build. |
I'm compiling on a Mac with the latest stable Xcode and command line tools. Is there anything I'm missing? |
No, we need to update the mac autoconfig (in https://cs.opensource.google/bazel/bazel/+/master:tools/cpp/osx_cc_configure.bzl and https://cs.opensource.google/bazel/bazel/+/master:tools/osx/crosstool/BUILD.tpl) needs to also write a |
Do you know what needs to be updated? It looks like bazel/tools/osx/crosstool/osx_archs.bzl Lines 17 to 20 in daaa6cf
bazel/tools/osx/crosstool/osx_archs.bzl Lines 28 to 36 in daaa6cf
bazel/tools/osx/crosstool/BUILD.tpl Lines 14 to 25 in daaa6cf
|
You're right, they do exist. I don't have a mac to test with, can you run the following command and report back the output?
This will list all toolchains that are being registered. |
|
I see you noticed the problem, because you opened bazelbuild/platforms#22 . For future readers: the issue is that the Mac autodetection is using aarch64 for the darwin exec constraint in the toolchains, but @thii is using amd64. |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
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 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
?Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: