builds: make bazelw support arm64 builds#2096
Conversation
Signed-off-by: Cerek Hillen <cerekh@gmail.com>
Signed-off-by: Cerek Hillen <cerekh@gmail.com>
Signed-off-by: Cerek Hillen <cerekh@gmail.com>
|
I'm seeing the same issue on my M1 Mac as I did when I reverted a similar change in January: #1998 Here's what I'm seeing now: That command builds cleanly with the x86_64 bazelisk binary. |
|
I'd be supportive if you wanted to narrow this change to support Linux arm64/amd64. |
|
Strange! I had tested it locally and it works. bazelw outputI'm happy to downscope, but I'd also love to root-cause! I remember running into a similar golang toolchain issue when using the x86_64 bazelisk before using the arm64 bazelisk. A couple of questions:
|
|
Ran I'll do some more testing with some of our downstream integrations before signing off. |
jpsim
left a comment
There was a problem hiding this comment.
Some light downstream testing didn't surface any issues that couldn't be resolved with a ./bazelw clean --expunge. 👍
For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Modifies the
bazelwshell script to bootstrapbazeliskfor arm64 on both Darwin and Linux. This unblocks work to re-enable Python builds for py-envoy-mobile internally. Note that this may not work until #2085 is in, as (iirc) it includes fixes to arm64 builds for Envoy.Risk Level: Low
Testing: No unit testing, but tested on arm64 both on macOS (natively) and Linux (Docker). See below. I don't have an x86_64 laptop on hand at the moment, so if someone wouldn't mind checking that this still works on x86_64, that'd be much appreciated!
Docs Changes: N/A
Release Notes: N/A
macOS
Note that there is no "Extracting Bazel installation..." step as I've been running this already.
Linux