Brian Ford wrote:
$ aclocal
[snip underquoted macro definition warnings]
ac-wrapper: /usr/bin/autom4te-2.13 is missing or not executable.
Something is very wrong.
aclocal: autom4te failed with exit status: 1
Any ideas? Thanks.
BTW, according to the http://cygwin.com/packages search, atuom4te-2.31
doesn't exist in any cygwin package. So, why is it looking for it?
Short version:
you're running the wrong aclocal. The automake tools no longer try to
figure out which version of themselves to use; you need to tell them. Run
/usr/sbin/alternatives --set automake /usr/bin/automake-1.4
to make automake-1.4 (and aclocal-1.4) the 'active' version on your machine.
Long version:
You're running aclocal from automake-1.9, which tries to invoke
unversioned autom4te from (some) autoconf package. There IS an
unversioned autom4te in /usr/bin -- which is a new (linux-derived and
not home-grown-for-cygwin) wrapper script.
All autoconf wrapper scripts will attempt to deduce the corrent version
of their underlying tools to run. This is happening properly in your
case; the autom4te script figures out that you need to use the
autoconf-2.13 distribution.
So, it tries to launch autom4te-2.13. But that's the ONE case where the
wrappers will bomb: because there is no autom4te in -2.13.
The real problem is that aclocal should not have tried to call autom4te
in your case -- but its behavior is normal for the automake-1.9.x
distribution because 1.9.x REQUIRES autoconf-2.5x or better.
So, ensure that you are using aclocal-1.4 NOT aclocal-1.9. See short
version, above.
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
