-
Notifications
You must be signed in to change notification settings - Fork 4.4k
problems when building bazel on mips64 #14097
Copy link
Copy link
Open
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)bad error messagingIssues where users get stuck because they don't understand what they did wrongIssues where users get stuck because they don't understand what they did wronghelp wantedSomeone outside the Bazel team could own thisSomeone outside the Bazel team could own thisnot staleIssues or PRs that are inactive but not considered staleIssues or PRs that are inactive but not considered staleteam-OSSIssues for the Bazel OSS team: installation, release processBazel packaging, websiteIssues for the Bazel OSS team: installation, release processBazel packaging, websitetype: support / not a bug (process)
Description
ATTENTION! Please read and follow:
- if this is a question about how to build / test / query / deploy using Bazel, or a discussion starter, send it to bazel-discuss@googlegroups.com
- if this is a bug or feature request, fill the form below as best as you can.
Description of the problem / feature request:
I downloaded bazel-pre-5.0.0-dist.zip and tried to build bazel on mips64 architecture. I builted with jdk 8 and jdk 11, the same bug happened.
ERROR: /tmp/bazel_twgOGtF0/out/external/bazel_tools/tools/jdk/BUILD:29:19: While resolving toolchains for target @bazel_tools//tools/jdk:current_java_runtime: no matching toolchains found for types @bazel_tools//tools/jdk:runtime_toolchain_type
ERROR: Analysis of target '//src:bazel_nojdk' failed; build aborted:
how to fix this bug?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)bad error messagingIssues where users get stuck because they don't understand what they did wrongIssues where users get stuck because they don't understand what they did wronghelp wantedSomeone outside the Bazel team could own thisSomeone outside the Bazel team could own thisnot staleIssues or PRs that are inactive but not considered staleIssues or PRs that are inactive but not considered staleteam-OSSIssues for the Bazel OSS team: installation, release processBazel packaging, websiteIssues for the Bazel OSS team: installation, release processBazel packaging, websitetype: support / not a bug (process)