Hi Keith So, my (non multilib for now) build of the RISC-V tools with newlib, newlib-nano and picolibc succeeded. I also had to disable the PIC option. With it enabled the picolibc build failed with an error about not being able to find the dynamic linker (sorry, forgot to save the verbatim error). Do you have the idea why that happens? I guess that PIC is largely, or maybe totally, irrelevant for a bare metal toolchain with no shared lib requirements? Thanks again for your help in making progress on this. ________________________________ From: Tommy Murphy Sent: Saturday, August 27, 2022 3:22:42 PM To: Keith Packard ; crossgcc@sourceware.org Subject: Re: Can CT-NG build a RISC-V picolibc toolchain? Ok - maybe it was a bit of a dumb question! I completely overlooked the fact that the Companion Libraries section of menuconfig has options for newlib-nano and picolibc. I was fixated on the C Library section so missed these. I'm trying a new build now with these enabled (newlib, newlib-nano and picolibc). Thanks again for the assistance.