This is the right repo. Just a note for 15.4, your cross-arm-none-eabi g++ packages are one version behind the gcc package causing the need to downgrade gcc to install the g++ packages. But great job, grabbed pico-sdk and examples from github and and your cross-arm-none-eabi packages and everything built just fine. Thank you.

Another question years later on the same package. Your cross-arm-none-eabi produces libg.a that shows Tag_CPU_arch: v4T. From https://developer.arm.com/documentation/dui0471/m/key-features-of-arm-architecture-versions/about-the-arm-architectures that seems to be for older architectures than the PI Pico.

I'm experiencing failures with normal string.h functions like strcmp() and wonder if there is something in the way the library is built that could explain it? Or is the v4T just a minimum supported architecture and the Pico rpi-2040 should work just fine with it?

The reason I ask is the open issue at https://github.com/carlk3/no-OS-FatFS-SD-SPI-RPi-Pico/issues/91 where using this package causes strcmp() to hardlock the Pico (reproducible 100% of the time even with trivial examples that call strcmp())

The Msys2 build for windows do no show this behavior. Could this be the reason for the strcmp() hardlock issue?