Verified
Status Update
No update yet.
Comments
lu...@gmail.com
[Empty comment from Monorail migration]
lu...@gmail.com
NOTE: There is no way to apply this fix on v3.4 or v3.5, because the workaround proposed at [1] isn't feasible.
gi...@appspot.gserviceaccount.com
The following revision refers to this bug:
https://gerrit.googlesource.com/gerrit/+/5d7becc82a6266fb1738df2ec5e388720b31b8ba
commit 5d7becc82a6266fb1738df2ec5e388720b31b8ba
Author: Luca Milanesio <luca.milanesio@gmail.com>
Date: Tue Oct 04 22:14:14 2022
Fix Bazel build on Apple M2 ARM64 chip
According to [1] Bazel fails to select the correct java-tools
binaries for Apple's ARM64 chip and download the generic x86.
Apple the workaround suggested at [1] by disabling the download
of the pre-compiled java_tools, allowing Bazel to build them
locally using the correct architecture.
[1]https://github.com/bazelbuild/bazel/issues/13944
Bug:https://crbug.com/gerrit/16306
Release-Notes: Fix Bazel build on Apple M2 ARM64 chip
Change-Id: I1b6900045b9835c95ada2a4e54342d1764a5de04
[modify]https://gerrit.googlesource.com/gerrit/+/5d7becc82a6266fb1738df2ec5e388720b31b8ba/tools/BUILD
commit 5d7becc82a6266fb1738df2ec5e388720b31b8ba
Author: Luca Milanesio <luca.milanesio@gmail.com>
Date: Tue Oct 04 22:14:14 2022
Fix Bazel build on Apple M2 ARM64 chip
According to [1] Bazel fails to select the correct java-tools
binaries for Apple's ARM64 chip and download the generic x86.
Apple the workaround suggested at [1] by disabling the download
of the pre-compiled java_tools, allowing Bazel to build them
locally using the correct architecture.
[1]
Bug:
Release-Notes: Fix Bazel build on Apple M2 ARM64 chip
Change-Id: I1b6900045b9835c95ada2a4e54342d1764a5de04
[modify]
ka...@gmail.com
[Comment Deleted]
gi...@appspot.gserviceaccount.com
The following revision refers to this bug:
https://gerrit.googlesource.com/gerrit/+/a7b7ae1c79af1307a57d9da26cff969840ae7f06
commit a7b7ae1c79af1307a57d9da26cff969840ae7f06
Author: Luca Milanesio <luca.milanesio@gmail.com>
Date: Tue Oct 04 22:14:14 2022
Fix Bazel build on Apple M2 ARM64 chip
According to [1] Bazel fails to select the correct java-tools
binaries for Apple's ARM64 chip and download the generic x86.
Apple the workaround suggested at [1] by disabling the download
of the pre-compiled java_tools, allowing Bazel to build them
locally using the correct architecture.
[1]https://github.com/bazelbuild/bazel/issues/13944
Bug:https://crbug.com/gerrit/16306
Release-Notes: Fix Bazel build on Apple M2 ARM64 chip
Change-Id: I1b6900045b9835c95ada2a4e54342d1764a5de04
(cherry picked from commit 5d7becc82a6266fb1738df2ec5e388720b31b8ba)
[modify]https://gerrit.googlesource.com/gerrit/+/a7b7ae1c79af1307a57d9da26cff969840ae7f06/tools/BUILD
commit a7b7ae1c79af1307a57d9da26cff969840ae7f06
Author: Luca Milanesio <luca.milanesio@gmail.com>
Date: Tue Oct 04 22:14:14 2022
Fix Bazel build on Apple M2 ARM64 chip
According to [1] Bazel fails to select the correct java-tools
binaries for Apple's ARM64 chip and download the generic x86.
Apple the workaround suggested at [1] by disabling the download
of the pre-compiled java_tools, allowing Bazel to build them
locally using the correct architecture.
[1]
Bug:
Release-Notes: Fix Bazel build on Apple M2 ARM64 chip
Change-Id: I1b6900045b9835c95ada2a4e54342d1764a5de04
(cherry picked from commit 5d7becc82a6266fb1738df2ec5e388720b31b8ba)
[modify]
is...@google.com
Edits were made to reflect the following in Monorail: auto-CCs.
Description
*************************************************************************
*** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!
*** Do not submit bugs for chrome/android and issues with your company's
*** Gerrit setup here. Those issues belong in different issue trackers.
*************************************************************************
What steps will reproduce the problem?
1. Clone Gerrit source code on Apple M2
2. Run 'bazelisk build gerrit'
What is the expected output?
The Gerrit build succeeds
What do you see instead?
The build fails with the following error:
src/main/tools/process-wrapper-legacy.cc:80: "execvp(external/remote_java_tools_darwin/java_tools/ijar/ijar, ...)": Bad CPU type in executable
Please provide any additional information below.
According to [1] the java_tools pre-built binaries for ARM64 are actually NOT compatible with ARM64 but only with x86.
The solution is to just NOT download the pre-built binaries and let Bazel build them for you locally.
[1]https://github.com/bazelbuild/bazel/issues/13944