On Apr 30, 2007, at 7:37 PM, David Liontooth wrote:
Andrew Church wrote:
It seems to accept both, but still fails even for high numbers:
transcode$ M4="/usr/bin/m4 -L16384" autoreconf -i -f
configure.in:1419: /usr/bin/m4: ERROR: Recursion limit of 16384
exceeded, use -L<N> to change it
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
Hmm. Well, autoreconf works fine for me (and apparently for
others), so
I can only assume there's something wrong with the ones that come
with OSX.
Try building and installing the most recent versions of autoconf,
automake,
and m4 from source (and make sure you set up your PATH so they're
found
before the system ones).
macports has recent versions of all these:
m4 1.4.9
autoconf 2.61
automake 1.10
We're clearly running into problems with the build environment on
macintel OSX -- PPC doesn't have the same problems.
The new m4 is first on my path:
transcode$ which gm4
/opt/local/bin/gm4
But autoreconf still finds the older version in /usr/bin/gm4 --
where is
this set?
transcode$ autoreconf -i -f
configure.in:1419: /usr/bin/gm4: ERROR: Recursion limit of 1024
exceeded, use -L<N> to change it
That version is older:
transcode$ /usr/bin/gm4 --version
GNU m4 1.4.2
However, even if I use the new /opt/local version, it still fails:
M4="/opt/local/bin/gm4 -L4096" autoreconf -i -f
/opt/local/bin/gm4:configure.in:1419: ERROR: recursion limit of 4096
exceeded, use -L<N> to change it
Dave,
make sure to grab the latest sources with:
cd transcode && cvs -z3 update -dP
Apply the patch I sent you.
Make sure in your environment you do:
export LIBTOOLIZE=glibtoolize
Those were the main things I needed to do to get my environment in
good shape aside from updating to the latest automake.
I haven't run into this recursion limit on my x86-based Mac. Maybe
you and I can take this off-list and troubleshoot it between ourselves.
cr
