picolibc: Add initial support for picolibc#109
Conversation
|
I tested the build in Docker using this PR and the PR in RIOT. It works on samr21 and simplify things when one just wants to do a quick test. |
|
Do you think the |
|
please rebase |
9504759 to
58138f4
Compare
Rebased |
and please squash. the way I see it, this is not used in master, so we cannot break much. |
0786dcd to
828c078
Compare
|
Squashed! |
|
Would be great if we can test the picolibc code paths in CI :) Not sure how long this takes to compile, but there is also a Debian package. |
|
Let's see... |
|
Looks like there is a conflict with the RISC-V toolchain: examples/gnrc_minimal/hifive1:gnu.txt |
|
When I try to build RIOT-OS/RIOT#15011 with This does not happen when I use the host-installed picolibc from the Debian package.
|
116: Dockerfile: install picolibc & ARM/RISC-V GCC via package manager r=maribu a=benpicco There seems to be a problem with the picolibc install in riotdocker. (#109 (comment)) Instead of trying to sort that out by ourself, just use the package [provided by Debian](https://packages.debian.org/search?suite=bullseye&searchon=names&keywords=picolibc). It has ~~no dependencies~~ the respective gcc packages as dependencies. So instead of manually downloading the toolchain, also install that from the repository. Co-authored-by: Benjamin Valentin <benpicco@googlemail.com> Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com>
Add support for picolibc in the docker image.
This builds the picolibc implementation for arm, esp32 and riscv32. The riscv implementation seems to work with RIOT-OS/RIOT#12305, but I haven't tested it yet on actual hardware as I don't own one of the hifive boards.
Meson is grabbed from pip and not from the bionic repos because the version in bionic is too old (0.45 vs 0.50)
An alternative approach would be to simply grab the debian buster deb's and install those. Please let me know what is preferred here.