This question has been asked before, but ignored (https://community.arm.com/support-forums/f/compilers-and-libraries-forum/52220/gnu-arm-embedded-what-were-the-newlib-compilation-options).
I would dare to ask it again:
Exactly what compilation options were used to build Newlib?
The versions of GCC tools of interest are:
It's not just an idle interest, or an attempt to waste your valuable time. I've got a practical need to rebuild Newlib as position-independent code, if you need to know why.
Is any real developer with access to build scripts reading this?
Thank you in advance,
Is that in the "manifests" here: https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/downloads-1
The arm-none-eabi manifest says:
# Component data for newlib
newlib_configure="--disable-newlib-supplied-syscalls --enable-newlib-io-long-long --enable-newlib-io-c99-formats --enable-newlib-mb --enable-newlib-reent-check-verify"
Hi both,Sadly, those options have changed a little since the GCC 9, 10 Embedded releases... For those releases the options should have been:
Thanks a lot, this is exactly what I was after. I suspected that those listed in GCC 11 manifest, as Bill suggested, are not all options.