https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
Keywords| |build
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
A lot of that's just the way that autoconf works. You'd probably have to change
the upstream implementation of certain autoconf macros to fix this.
Alternatively, you could also try configuring with the "-C" flag to your
configure script, which should cause configure results to be cached, but that
can be rather fragile, as the config.cache files can stop your build if the
slightest things to change. I suppose GCC could try sharing its config.cache
files more widely between its various subdirectories, but that would be
somewhat risky, given that some of the things that configure checks for could
change due to the whole bootstrap process (fixincludes changes the headers
available, the new compiler getting built changes which compiler should be
found, and what features it has, the new runtime libraries getting built change
what functions are available, and so on...)
