On 6/9/2026 7:01 AM, Kyrylo Tkachov wrote:
Hi all,
A native "make bootstrap" runs every subdirectory's autoconf configure
three times, once per stage, because each stage is built in a fresh
directory (stageN-MODULE is created empty and renamed to MODULE), so the
per-directory config.cache that the build system already requests with
--cache-file=./config.cache starts out empty in every stage. The
configure scripts are serial, and the host-module configures are
serialized with respect to each other, so on a machine with many cores
the configure phases leave it almost completely idle.
[ ... ]
I've throw this into my tester which has native testing for riscv64,
x86_64 & aarch64 along with QEMU user mode emulated native testing for a
variety of other targets like alpha, hppa, sh4, etc.
I haven't seen any problems, but I'm also not seeing major
improvements. Yea, there's perhaps a small positive effect, but I kind
of expected more.
It looks like Andrew would rather we clean up our configure tests as an
alternative. IMHO doing both seems best, but there's clearly not
consensus on any path right now.
Jeff
