> On Mon, 2005-12-19 at 00:15 +0000, Harlan Stenn wrote: > > The problem with doing these things in configure is that one must rerun > > configure to regenerate the file. > > > > Sometimes it is better do produce these things in config.status. > > There is no need to do so, in this case, because the file is being > generated when running configure. For certain definitions of "need", I agree with you. > "config.status --recheck", runs configure, so changes to configure.ac > automatically get propagated to the generated file. For packages that are "big enough" (ie, that have a large/slow run of "configure"), this is an unnacceptable solution. H _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
