-
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
[riscv][risc-v][riscv64]Cannot build Bazel 7.1.0 on RISC-V 64 (Lichee PI4A) #23018
Comments
For Bazel 6.1.0 I got this error:
|
For Bazel 7.1.0 and JDK 17:
|
Seems like https://github.com/bazelbuild/rules_python/pull/1907/files is required to be able to build on riscv64. Which means that only Bazel v8.00+ will be able to properly build, see 01f6dec. One has to backport this commit 01f6dec to 7.1.0 and hope it builds. |
From the documentation, I do not see a way to bootstrap without having a .dist release, how can I do it though with the git repo? Otherwise, I ll need to wait for a new tag and a release of 8.x. |
RISC-V master is broken because this commit has been reverted/changed b34be09 and it was not applied when it got reverted in the main repo and the functionality was switched to using the bazel_rules repository https://github.com/bazelbuild/rules_java/blame/master/toolchains/BUILD#L141 I opened a PR here: bazelbuild/rules_java#198 |
Temporarily use PyPI's source package to build python-protobuf instead of using Bazel to prevent loop makedepends. Will be reverted once Bazel is built (see bazelbuild/bazel#23018)
Temporarily use PyPI's source package to build python-protobuf instead of using Bazel to prevent loop makedepends. Will be reverted once Bazel is built (see bazelbuild/bazel#23018)
@lazyprogrammerio hi
you know something about it? |
Required to be able to build rules_java for RISC-V. Fixes: bazelbuild#23018
@lazyprogrammerio
|
Description of the bug:
Hello,
I am running Ubuntu 24.04 stock (riscv64) on the LicheePi 4A.
When trying to build bazel from source (7.1.0), I get an error, as it weirdly tries to build Bazel with Bazel (?) and it fails.
My first question is: why is it trying to build Bazel with Bazel ->
Building Bazel with Bazel
?Reproduction steps:
Which category does this issue belong to?
Core
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release
?No response
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: