> How are you transitioning libnewlib-arm-none-eabi and the ecosystem > behind it?
I'm starting to upload PRs to salsa for these with a plan to migrate
them to the new toolchain:
https://salsa.debian.org/rubund/ubertooth/-/merge_requests/2
If necessary, I can NMU these, but as they're dependent on embedded
hardware that I don't have access to, any patches would be untested.
As you can see, the list is pretty short, so I'm hoping the process will
be quick.
* firmware-microbit-micropython
* hackrf (for libnewlib-arm-none-eabi)
* pico-sdk (for libnewlib-arm-none-eabi)
* ubertooth (for libnewlib-arm-none-eabi)
* qmk (for libnewlib-arm-none-eabi)
Should have patches ready in the next couple of days.
* libstdc++-arm-none-eabi (for libnewlib-arm-none-eabi)
New version has already been uploaded.
I've already uploaded a new gcc-arm-none-eabi with the autopkgtest
fixes; -2 missed the check for running on 32-bit systems where
qemu-system-aarch64 is unavailable, -3 should pass everywhere.
--
-keith
signature.asc
Description: PGP signature
