RE: configure.in:420: m4: ERROR: Recursion limit of 1024 exceeded???

["Spencer Marshall" <gdsmarshall at hotmail dot com>]

Thank you, that did the trick, and got a bit further, I need to troll 
through gcc.gnu.org for the new error

In file included from gthr-default.h:1,
                 from ../../src/gcc/gthr.h:98,
                 from ../../src/gcc/libgcc2.c:2977:
../../src/gcc/gthr-posix.h:37:21: pthread.h: No such file or directory
make[2]: *** [libgcc/./_eh.o] Error 1
make[2]: Leaving directory `/export/dalmany/gdsm/build/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory `/export/dalmany/gdsm/build/gcc'
make: *** [all-gcc] Error 2

Many thanks for your help,

Spencer

>From: "Rupert Wood" <me@rupey.net>
>To: "'Spencer Marshall'" <gdsmarshall@hotmail.com>
>CC: <gcc-help@gcc.gnu.org>
>Subject: RE: configure.in:420: m4: ERROR: Recursion limit of 1024 
>exceeded???
>Date: Fri, 19 Apr 2002 09:36:45 +0100
>
>Spencer Marshall wrote:
>
> > make[1]: Entering directory `/export/dalmany/gdsm/build/gcc'
> > cd ../../src/gcc && autoheader
> > configure.in:420: m4: ERROR: Recursion limit of 1024 Exceeded
>
>Regenerating the GCC configure etc. isn't trivial. (I can't remember the
>magics involved to make it work.) They shouldn't need regenerating
>anyway.
>
>From the top level of your source tree, run either:
>
>     contrib/gcc_update --touch
>or
>     contrib/egcs_update --touch
>
>and it should leave most of the pregenerated files alone. (2.95 has
>egcs_update and 3+ has gcc_update but I don't know which one 2.96 has.)
>
>This might instead be a make bug - but if you're running GNU/Linux then
>you probably already have GNU make.
>
>Rup.
>




_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com