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

Re: sudo autotools - recursion limit of 1024



Peter Vrabec píše v Čt 23. 08. 2007 v 18:02 +0200:
> Hi folks,
> 
> could you help me with this:
> 
> $ cvs -d anoncvs anoncvs sudo ws:/cvs get sudo
> $ cd sudo
> $ autoreconf
> /usr/bin/m4:configure.in:2321: ERROR: recursion limit of 1024 exceeded,
> use -L<N> to change it
> autom4te: /usr/bin/m4 failed with exit status: 1
> /usr/bin/m4:configure.in:2321: ERROR: recursion limit of 1024 exceeded,
> use -L<N> to change it
> autom4te: /usr/bin/m4 failed with exit status: 1
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> 
> any idea how to locate the problem?
> 

The cause is probable some bad macro quotation or unclosed brace.

I have tried it a bit with deleting parts of configure.in (which should
eliminate the buggy macro) and now I can run autoreconf successfully.
The included patch deletes a part of configure.in and now it is possible
to run autoreconf => the buggy macro is there. Also Google is saying
that there was a problem somewhere in libtool.


		Dan

--- configure.in.old	2007-08-23 19:22:17.000000000 +0200
+++ configure.in	2007-08-23 19:27:24.000000000 +0200
@@ -1138,52 +1138,6 @@
 AC_PROG_CPP
 
 dnl
-dnl Libtool magic; enable shared libs and disable static libs
-dnl XXX - disable static, require shared
-dnl
-AC_CANONICAL_HOST
-AC_CANONICAL_TARGET([])
-LT_PREREQ([1.9f])
-LT_INIT([disable-static])
-
-dnl
-dnl Defer with_noexec until after libtool magic runs
-dnl
-if test "$enable_shared" = "no"; then
-    with_noexec=no
-else
-    eval _shrext="$shrext_cmds"
-fi
-AC_MSG_CHECKING(path to sudo_noexec.so)
-AC_ARG_WITH(noexec, [  --with-noexec[=PATH]      fully qualified pathname of sudo_noexec.so],
-[case $with_noexec in
-    yes)	with_noexec="$libexecdir/sudo_noexec$_shrext"
-		;;
-    no)		;;
-    *)		;;
-esac], [with_noexec="$libexecdir/sudo_noexec$_shrext"])
-AC_MSG_RESULT($with_noexec)
-NOEXECDIR="`echo $with_noexec|sed 's:^\(.*\)/[[^/]]*:\1:'`"
-
-dnl
-dnl It is now safe to modify CFLAGS and CPPFLAGS
-dnl
-if test "$with_devel" = "yes" -a -n "$GCC"; then
-    CFLAGS="${CFLAGS} -Wall"
-fi
-
-dnl
-dnl Find programs we use
-dnl
-AC_CHECK_PROG(UNAMEPROG, uname, uname)
-AC_CHECK_PROG(TRPROG, tr, tr)
-AC_CHECK_PROG(NROFFPROG, nroff, nroff)
-if test -z "$NROFFPROG"; then
-    MANTYPE="cat"
-    mansrcdir='$(srcdir)'
-fi
-
-dnl
 dnl What kind of beastie are we being run on?
 dnl Barf if config.cache was generated on another host.
 dnl

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