This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
David Rothenberger wrote On 10/21/2007 9:12 AM -0800: > Perhaps a cygcheck output? David, cygcheck -s output attached. >> autoreconf-2.61: running: automake --add-missing --copy --force-missing >> automake-1.9: autoconf failed with exit status: 1 > > I have a different version of automake: 1.10 > > % automake --version > automake (GNU automake) 1.10 I get the above output as well. While it doesn't make sense to me, it appears that the autotools scripts search for the version of aclocal/automake that was used to build aclocal.m4/Makefile.in originally, and to reuse that version, in this case 1.9, EVEN IF I set WANT_AUTOMAKE to 1.10, in the environment, or the .cygport file. Here's a snippet of this in action, after adding 'set -x' to the .cygport file: +++ gawk '{ if (match($0, "[[:space:]]*\\[?AM_AUTOMAKE_VERSION\\(\\[?([0-9].[0-9]+)[^)]*\\]?\\)", res)) { print res[1]; exit } }' aclocal.m4 ++ echo 1.9 + confversion_am=1.9 + for v in '${vers}' + '[' 1.9 = 1.10 ']' + '[' 1.9 = 1.10 ']' + '[' 1.9 = 1.10 ']' + for v in '${vers}' + '[' 1.9 = 1.9 ']' + binary=binary_1_9 + binary=/usr/bin/automake-1.9 + break So my guess it's using 1.9 on your system as well. What stumps me is why it works for you, and fails for me. Perhaps I should fire up VMWare, and install Cygwin in a pristine XP SP2, and see if I'm still getting this error. I just can't believe the hoops we have to jump thru when working with Windows. -Ross
Attachment:
cygcheck.txt
Description: application/unknown
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |