autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Latest CVS - possible serious bug using it in UnixWare 7.1.1


From: Akim Demaille
Subject: Re: Latest CVS - possible serious bug using it in UnixWare 7.1.1
Date: 29 Jan 2001 15:13:02 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Crater Lake)

| /* Define if you have the <iconv.h> header file. */
| #undef HAVE_ICONV_H"
| /usr/local/bin/m4: configure.in: 462: ERROR: Recursion limit of 250 exceeded, 
use -L<N> to change it
| ----------------------------------------------------------------------------
| 
| 
| The error refers to      gcc/gcc/configure.in

Yeah, line 462.  Shrink configure.in, and show us the guilty line.


| Sooo, I made a shell script to raise the limit to 2000
| by calling the shell script /usr/local/bin/gm4 which is
| searched by configure when it tries to find an m4 to use.
| It would use the gm4 version, which only had this coomand:
| 
|    /usr/local/bin/m4 -L2000 $@
| 
| I tried various values of -L, 400, 500, 800, 1000, 2000.
| They all failed with the same error, saying the limit I 
| chose had been exceeded.
| 
| Nothing woirked until I removed the gm4 script and switched
| back to autoconf 2.13.

Do exactly the converse: have a smallest limit to be able to find
quickly what was wrong without having zillions of logs.  Here is my
advice:

my-m4:

        /usr/local/bin/m4 -L40 -dV $@ -o /tmp/m4-$$.log


and study in /tmp/m4-$$.log the circular dependency.  You should
easily find some losage such as

        AC_MSG_ERROR($0: invalid blah blah)

which, obviously, will keep on expanding the current macro (since $0
is it's name).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]