Package Details: riscv64-unknown-elf-gcc 9.2.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: esmil
Last Packager: esmil
Votes: 3
Popularity: 0.000000
First Submitted: 2017-09-10 11:59
Last Updated: 2019-10-26 13:21

Latest Comments

ftheile commented on 2019-09-30 07:10

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

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

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

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

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.