https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104301
Bug ID: 104301
Summary: --enable-cstdio=stdio_pure not passed down to
libstdc++-v3
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: rdiezmail-gcc at yahoo dot de
Target Milestone: ---
I have been using the following makefile for years to build a cross-compiler
GCC toolchain with Newlib:
https://github.com/rdiez/JtagDue/blob/master/Toolchain/Makefile
Now I would like to optionally replace Newlib with Picolibc.
Picolibc needs this option for libstdc++-v3:
--enable-cstdio=stdio_pure
So I tried to pass it to GCC's top-level 'configure' script, but
libstdc++-v3's 'configure' script is not run at that time, it runs
later on, when you invoke 'make' at GCC's top level. Then I see this
line in the 'make' output:
checking for underlying I/O to use... stdio
So it seems that the "--enable-cstdio=stdio_pure" option is not passed down
from the top-level 'configure' to libstdc++-v3's 'configure'.
I guess this is a bug in the top-level 'configure' logic. It has probably gone
unnoticed for a long time because it is only recently that you can specify
options other than 'stdio' in --enable-cstdio=xxx .
Or is the GCC user expected to delve down and configure GCC's components
separately?
