Paolo Bonzini writes: > Here is an idea for writing a multiprocessor-friendly autoconf. > Basically, the idea is to change the configure phase into a Makefile > target, and use caching as a way to split it into various sub-targets that > can be executed in parallel. The shell script might run the "sane build" > test and then spawn the Makefile.
How will you write config.status and config.log in a serial manner? Use a bunch of little files and assemble them at the end? If the configure script aborts with an error, where will the user find the diagnostic information? -- Peter Eisentraut [EMAIL PROTECTED]
