Package Details: riscv64-unknown-elf-gcc 13.1.0-2

Git Clone URL: https://aur.archlinux.org/riscv64-unknown-elf-gcc.git (read-only, click to copy)
Package Base: riscv64-unknown-elf-gcc
Description: The GNU Compiler Collection - cross compiler for 32bit and 64bit RISC-V bare-metal
Upstream URL: http://gcc.gnu.org/
Keywords: risc-v
Licenses: GPL, LGPL, FDL
Submitter: esmil
Maintainer: Maxr1998
Last Packager: Maxr1998
Votes: 7
Popularity: 0.81
First Submitted: 2017-09-10 11:59 (UTC)
Last Updated: 2023-05-28 14:38 (UTC)

Latest Comments

fnv_required commented on 2023-04-15 12:30 (UTC)

was fixed in https://github.com/cnlohr/ch32v003fun/commit/3c4fdca3a75d8c30b2c0aaf2607f7a78f9fb93cb

fnv_required commented on 2023-04-10 07:07 (UTC) (edited on 2023-04-10 09:58 (UTC) by fnv_required)

Hi, I'm trying to build https://github.com/cnlohr/ch32v003fun but when I install this and riscv64-unknown-elf-newlib, then try to "make" the "blink" example I get:

../../ch32v003fun/ch32v003fun.c: Assembler messages: ../../ch32v003fun/ch32v003fun.c:770: Error: unrecognized opcode csrw mstatus,a0', extensionzicsr' required ../../ch32v003fun/ch32v003fun.c:772: Error: unrecognized opcode csrw 0x804,a3', extensionzicsr' required ../../ch32v003fun/ch32v003fun.c:775: Error: unrecognized opcode csrw mtvec,a0', extensionzicsr' required ../../ch32v003fun/ch32v003fun.c:802: Error: unrecognized opcode csrw mepc,a5', extensionzicsr' required lto-wrapper: fatal error: riscv64-unknown-elf-gcc returned 1 exit status compilation terminated. /usr/lib/gcc/riscv64-unknown-elf/12.2.0/../../../../riscv64-unknown-elf/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status

can anyone help me here?

ch32v003fun recommends to install on ubuntu/debian, there the packages are libnewlib-dev and gcc-riscv64-unknown-elf. tested it in a VM, with them make works instantly.

Maxr1998 commented on 2022-07-01 17:12 (UTC) (edited on 2022-07-01 18:44 (UTC) by Maxr1998)

Adopted the package and updated everything to the latest version. Some patches were required to get it to build again.

Eragon commented on 2022-01-16 21:22 (UTC)

The current isl hosting platform seems to be sourceforge

https://libisl.sourceforge.io/

ftheile commented on 2019-09-30 07:10 (UTC)

I get multiple errors regarding existing symbolic links, e.g.:

==> Starting prepare()... ln: failed to create symbolic link 'isl/isl-0.21': File exists

Adding -f to all ln -s commands in the PKGBUILD fixed the problem for me.

esmil commented on 2018-03-01 09:32 (UTC)

Yeah, that confused me too. The riscv toolchain is a little funny in that way. Upstream recommends you just build the riscv64-unknown-elf-gcc and then compile with -march=rv32i -mabi=ilp32 (or whatever suits your platform).

You can see (or steal from) my experiments with the hifive1 board at https://github.com/esmil/pentagram

catalin.hritcu commented on 2018-02-28 20:53 (UTC)

Description says that this supports 32bit RISC-V, but no riscv32-unknown-elf-gcc binary is generated. Am I missing anything?

esmil commented on 2018-02-15 12:23 (UTC)

I assume you mean dtc rather than dct.

That's odd. I don't have dtc installed and it compiles fine for me. Also I don't see why gcc should use the dtc. Devicetrees are used to describe hardware memary map layout, IRQ numbers etc. so u-boot and the linux kernel uses it (although the linux kernel has a version of dtc in-tree). But I don't see why gcc would need that.

Almin commented on 2018-01-15 16:57 (UTC)

How about addingt the dct package (device-tree-compiler) to the dependencies? Otherwise it won't build for me and dct is in the official repositories.