Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failed to compile with bazel-7.2.0 (on arm64) #359

Open
DwarKapex opened this issue Jun 13, 2024 · 1 comment
Open

Failed to compile with bazel-7.2.0 (on arm64) #359

DwarKapex opened this issue Jun 13, 2024 · 1 comment

Comments

@DwarKapex
Copy link

We updated the bazel version recently (from 7.1.2 to 7.2.0) and it started failing to build from source with the linker issue:

#13 357.0 [62 / 67] Compiling third_party/icu/data/conversion_data.c; 0s processwrapper-sandbox ... (2 actions running)
#13 358.8 Analyzing: 539 targets (130 packages loaded, 9117 targets configured)
#13 358.8 [64 / 67] [Prepa] Linking third_party/icu/data/libconversion_data.lo ... (3 actions, 0 running)
#13 358.9 ERROR: /opt/lingvo/third_party/icu/data/BUILD.bazel:37:11: Linking third_party/icu/data/libconversion_data.so failed: (Exit 1): gcc failed: error executing CppLink command (from target //third_party/icu/data:conversion_data) /usr/bin/gcc @bazel-out/aarch64-opt/bin/third_party/icu/data/libconversion_data.so-2.params
#13 358.9 
#13 358.9 Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
#13 358.9 ld.lld: error: unable to find library -lrt -lm
#
@DwarKapex DwarKapex changed the title Failed to compile with bazel-7.2.0 Failed to compile with bazel-7.2.0 (on arm64) Jun 13, 2024
@DwarKapex DwarKapex mentioned this issue Jun 13, 2024
Merged
@DwarKapex
Copy link
Author

Interesting, that building on x86 has no issues like that.

olupton pushed a commit to NVIDIA/JAX-Toolbox that referenced this issue Jun 14, 2024
@DwarKapex
WAR to build upstream-pax for ARM64 (#898)
b4d6332 
Upstream-pax for ARM64 fails to build lingo with the latest
`bazel-7.2.0`, but OK with `bazel-7.1.2`. Force to use last but one
version of bazel, while lingvo team address this issue.

(a bug to lingvo upstream
tensorflow/lingvo#359)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DwarKapex