Keith Packard
Keith Packard
It "should" work as the toolchains are supposed to be the same. But you're pretty clearly picking up some newlib bits somehow?
Let's check how ios_init.cc gets compiled -- somehow it's pulling in a newlib header instead of the matching picolibc header.
> @keith-packard By any chance, have you had a chance to figure out what is wrong? I don't have any easy way to test on Windows or Mac OS, alas....
Looks like this increased the linux x86 toolchain from 1.59GB to 1.66GB?
GCC has a bug which breaks Zephyr's use case for 'dual' mode. Working on a fix.
This change is part of SDK 0.18, so this issue should be closed.
I'm working on llvm toolchain support in picolibc by building with the LLVM embedded toolchain for Arm. I've found a few compatibility issues with clang and llvm-as, along with some...
I'm having some adventures getting this toolchain to build picolibc with --multilib=true. I looked at how sdk-ng is building picolibc and it's using --multilib=false and then hand-coding all of the...
> @keith-packard that feature looks awesome, and as usual only two questions: > > 1. Any plans to get it submitted to the upstream Crosstool-NG? Yup, once we know how...
This is actually working when I disabled newlib-nano to keep the build times in check. The only testing failure occurred when a newlib-nano test slipped through; that should be fixed...