bazelbuild/bazel

Illegal instruction (core dumped) in risc-v

Open

#23,051 opened on Jul 21, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-Coreteam-OSStype: bug

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Description of the bug:

nowadays, i am working on building bazel 6.1.0 from source. here are the ways.

  • first way:

$ cat /etc/os-release NAME="openEuler" VERSION="24.03 (LTS)" ID="openEuler" VERSION_ID="24.03" PRETTY_NAME="openEuler 24.03 (LTS)" ANSI_COLOR="0;31" $ uname -a Linux openeuler-riscv64-worker1 6.6.0 #1 SMP Tue Jul 2 11:21:06 CST 2024 riscv64 riscv64 riscv64 GNU/Linux

sudo dnf install bazel git clone https://github.com/bazelbuild/bazel.git cd bazel git checkout tags/6.1.0 bazel build //src:bazel-dev

$ bazel build //src:bazel-dev Illegal instruction (core dumped)

  • second way:

i download the dist file, and run env EXTRA_BAZEL_ARGS="--tool_java_runtime_version=local_jdk" ./compile.sh. happily, i get the bazel binary file. but when i run bazel version,i get the same error Illegal instruction (core dumped)

Contributor guide

Research direction
Investigate the illegal instruction by running under QEMU or checking CPU feature flags on RISC V. Look into Bazel's use of native code that may rely on x86 specific instructions.
Tech stack
java
Domain
backendbuild system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaBazel build systemRISC V architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30