_includes: update RISC-V toolchain build#339
Conversation
|
Wouldn't it be better to recommend people use the RISC-V toolchain from their repositories like we do for ARM? I don't think I've ever compiled it from source. Maybe it wss necessary 5 years ago when it was much less mature. |
|
I just had to compile it right now for Ubuntu :-) (that's how I remembered that I wanted to remove that). Although I did that because of the verification side, so I'm not sure we really need to recommend it here. One problem is that we know that the version that ships with Debian Trixie (14.2.0) is broken. The one you get from building yourself is now 16.1. Maybe also a bit experimental because we're not testing that anywhere. I'm still not quite sure what to do about all that in terms of docs, because it'll be very annoying for people to get a different gcc version for Trixie for all architectures, and we mostly have worked around it. But of course there is a good probability people will run into the same issue if they have inline asm anywhere in their code and use -O3. |
The RISC-V toolchain no longer needs a separate submodule init. (Now part of its build system.) Signed-off-by: Gerwin Klein <gerwin.klein@proofcraft.systems>
|
(fixing the gitlint failure) |
2 participants
The RISC-V toolchain no longer needs a separate submodule init. (Now part of its build system.)