On Sun, 2004-05-23 at 15:53, David Knox wrote: > Thanks Patrick, > Your suggestion appears to solve aclocal.m4 from getting overwritten. I > didn't realize that adding macros to m4 is a bad practice but knowing > what I've learned, I can see the problem. That's not quite correct. Adding macros to aclocal.m4 is a "no-no", because aclocal.m4 normally (when using automake) is a generated file. With automake, if you want to add macros, use acinclude.m4, and leave aclocal.m4 be automatically generated. > I very much would like to stop autoconf from generating the rules to > re-run aclocal, automake, and autoconf. You don't really want to do this. Automake generated Makefiles are supposed to trigger regeneration of files only if they must be regenerated, because something has changes that requires them to be regenerated. Ralf -- Ralf Corsepius Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung (FAW) Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690 mailto:corsepiu@xxxxxxxxxxxxxx FAX: +49/731/501-999 http://www.faw.uni-ulm.de _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://mail.gnu.org/mailman/listinfo/autoconf
