-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
riotbuild: update RISC-V Toolchain #248
Conversation
Citing https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack: > DEPRECATED! Replaced by xpack-dev-tools/riscv-none-elf-gcc-xpack So let's do that.
So, if we merge this, it might fail some builds in RIOT master and possibly the release branch. @maribu if you're "on it" I'm ok with merging this now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. (merging when @maribu or others promise to watch RIOT master for fall-out)
I think I can do some local testing first, e.g. all apps for a single RISC-V board should be doable on my machine. |
Yeah, there are some issue uncovered by the toolchain update. I think I can prepare a PR soonish that would fix that. |
This should be updated in lock-step with RIOT-OS/RIOT#20380 |
Let's go. |
So once this shows "merged", the master workflow needs to complete building & publishing the containers, then ~15min more to deploy, then we need to merge RIOT-OS/RIOT#20380. |
Citing https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack:
So let's do that.
Note: Depends on and includes: