Patrick Welche <prlw1@xxxxxxxxxxxxxx> writes: > The attached patch is necessary as if you set the environment variable M4 > to "m4 --nesting-limit=2048", the regexp won't match as there is a '=' > rather than a ' ' after nesting-limit. > > BTW if even 2048 is too small what could be wrong with my configure > script? (In fact this is apr, at the autoheader stage) Hard to say, other than the obvious "you've got a recursive loop". Thanks for reporting the problem. I installed the following slightly-different patch into CVS. Does it work for you? 2005-07-04 Paul Eggert <eggert@xxxxxxxxxxx> * bin/autom4te.in ($m4): Catch usages like --nesting-limit=2048. Problem reported by Patrick Welche. Index: bin/autom4te.in =================================================================== RCS file: /cvsroot/autoconf/autoconf/bin/autom4te.in,v retrieving revision 1.95 diff -p -u -r1.95 autom4te.in --- bin/autom4te.in 14 May 2005 07:00:39 -0000 1.95 +++ bin/autom4te.in 5 Jul 2005 06:45:24 -0000 @@ -95,7 +95,7 @@ fatal "need GNU m4 1.4 or later: $m4" # Set some high recursion limit as the default limit, 250, has already # been hit with AC_OUTPUT. Don't override the user's choice. $m4 .= ' --nesting-limit=1024' - if " $m4 " !~ / (--nesting-limit|-L) /; + if " $m4 " !~ / (--nesting-limit(=[0-9]+)?|-L[0-9]*) /; # @M4_BUILTIN -- M4 builtins and a useful comment. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
