lowRISC / lowRISC/lowrisc-chip

Error building GCC for RISC-V

Open
#212 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
601
Forks
147
PR merge metrics
No merged PRs in 30d

Description

I have follow the instructions by [lowrisc](https://lowrisc.org/docs/tagged-memory-v0.1/setup/) step by step starting from "downloading the lowRISC chip repository" section..and yet i have encountered this error..
```
rrm cpp.pod gcc.pod fsf-funding.pod gfdl.pod
make[3]: Leaving directory '/home/aaron/low/lowrisc-chip/riscv-tools/riscv-gcc/build/build-gcc-linux-stage2/gcc'
make[2]: *** [Makefile:5284: all-gcc] Error 2
make[2]: Leaving directory '/home/aaron/low/lowrisc-chip/riscv-tools/riscv-gcc/build/build-gcc-linux-stage2'
make[1]: *** [Makefile:890: all] Error 2
make[1]: Leaving directory '/home/aaron/low/lowrisc-chip/riscv-tools/riscv-gcc/build/build-gcc-linux-stage2'
make: *** [Makefile:140: build-gcc-linux-stage2] Error 2
```
I have tried to use `sudo su` after the error and reran `make linux` again to give permission to write..and yet it still fail. I found out a lot of people have been facing this error and i couldnt find the solution for them. So how do i fix this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the lowRISC setup instructions and the riscv-tools/riscv-gcc build entry point used by `make linux`. Capture the compiler output before the summarized `Makefile` errors, then reproduce the failure and identify a documented fix or the missing environment detail needed to diagnose it.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.