-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
Arm64 support on Linux #1550
Arm64 support on Linux #1550
Conversation
That one looks great, and might even make split configurations work when building ios and android multi arch targets. |
Change looks good, but it's failing tests. Something about toolchains not being registered. I'll take a look today and figure out what's happening. |
It's almost certainly because the cpu constraint isn't exported in bazel-tools/platform. That export is in my pull request #5360. Should I withdraw and resubmit once the dependant pull request is complete? |
Ok, that makes sense. Let's keep this PR open and wait until bazelbuild/bazel#5360 has been merged and released in a new version of Bazel. At that point, rebase to |
This was used to work around a linker bug in Xcode 7.2 and earlier. We probably don't need to support those old versions anymore. This enables debugging binaries on macOS. Fixes bazel-contrib#1553
…b#1562) Also: clean up the race tests, move to tests/core, and test that the race tag is set. Fixes bazel-contrib#1559
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Bazel 0.15.0 is now released. I'd like to to one more major release of rule_go (likely early next week) before merging this PR and making Bazel 0.15.0 the minimum supported version. |
The Bazel 0.15.0 release issue is here: bazelbuild/bazel#5057 for reference. |
I updated this PR to tip of |
Thanks @jayconrod . What is the release cadence for Bazel? Trying to determine at what pace I need to track this to get these changes incorporated into projects up and downstream. |
@vielmetti Bazel aims for a release every month, but they are quite late this month. You can track this month's release at bazelbuild/bazel#5058. |
@jayconrod root@bin:/go/src/github.com/google/gvisor-debug# bazel build runsc |
@lubinsz This breaks on Bazel 0.15, which is our minimum supported version. I'm planning to tag a release of rules_go next week. We can bump the minimum supported Bazel version after that and then merge this. |
This might need rebasing on master too |
I'll rebase it once 0.17 is out, allow us to get some more issues with the Arm64 port resolved. |
@ArielleA @jayconrod @steeve |
@lubinsz Now that Bazel 0.17 is out, we should be fine. Merged. |
@jayconrod |
@lubinsz I expect we'll tag a major release this week. |
Squashed and backported all commits in PR [1] from Arielle Albon <[email protected]> [1] bazel-contrib#1550 Signed-off-by: Alexandru Avadanii <[email protected]>
Arm64 support fixes #1506 requires pull request bazelbuild/bazel#5360