[Picolibc] Integrating Picolibc into a GCC toolchain

[R. Diez]

> I would like to understand the implications of not having
> "--enable-cstdio=stdio_pure" when building GCC against Picolibc.
> [...]

The GCC guys just answered: It is apparently a cosmetic problem.

Option "--enable-cstdio=stdio_pure" is passed down, but the build log shows "stdio" regardless of the option actually passed.

Just in case: were you erroneously passing "--enable-stdio=xxx" instead of "--enable-cstdio=xxx" when running the automated test suite? Or just when doing manual tests on your PC?

Regards,
   rdiez