Apparently, a lot of users do not even know about configure -C aka. --config-cache which of course doesn't help Autoconf's reputation about producing configure scripts which are slow even for development. So one question would be what about making -C the default? We could have --force or --no-cache to turn it off. This behavior actually used to be the default. It was reverted around commit 5ae14bc8c048ed9a2dda6b67794ba (and also see commit 4abad4e9bfbcedd018302059844f8), 10 years ago. Here's some discussion from back then, listed in the order in which I traced back things, that is, the last thread has the most info: http://sourceware.org/ml/autoconf-patches/2000-04/msg00000.html http://sourceware.org/ml/autoconf-patches/2000-03/msg00274.html http://sourceware.org/ml/autoconf/2000-02/msg00271.html Back then, the consensus was to not make it the default because that was deemed too dangerous for users. Various reports are cited, and also the problem is mentioned that such kinds of failures tend to be quiet very often and are hard to debug. Comments are appreciated. Thanks, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
