tags 10700 + moreinfo severity 10700 minor thanks Reference: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10700>
Hi Oleg, thanks for the report. > ============================================= > GNU Automake 1.11: tests/test-suite.log > ============================================= > Consider that 1.11 is already some years old, and, most importantly, suffers from a know security vulnerability: <http://thread.gmane.org/gmane.comp.sysutils.autotools.announce/131> I'd advise you to install the latest version 1.11.3 instead. Now, let's come to the bug report ... > 578 of 589 tests failed. (140 tests were not run). > WOW! This is clearly the result of a weird failure in the Automake build system, or of some system misconfiguration ... > FAIL: aclibobj.test (exit: 2) > ============================= > > [SNIP] > > === Running test ./aclibobj.test > ++ pwd > /cygdrive/c/m2sync/automake-1.11/tests/aclibobj.dir > + cat > + cat > + : > + : > + aclocal-1.11 -Werror > Can't open perl script "/cygdrive/c/m2sync/automake-1.11/aclocal": No such > file or directory > [SNIP a ton of similar failures] It seems the wrapper scripts in the testsuite are unable to execute the just-built aclocal and automake scripts ... Which commands have you used to run the testsuite? Have the 'aclocal' and 'automake' scripts been created correctly? Could you please post the results of these commands? $ cd /cygdrive/c/m2sync/automake-1.11/ $ ls -l aclocal automake $ sed 5q aclocal $ sed 5q automake $ cat tests/aclocal-1.11 $ cat tests/auatomake-1.11 $ echo 'x:; @echo $(PERL) && $(PERL) -V' | make -f Makefile -f - x > FAIL: acloca20.test (exit: 2) > ============================= > > [SNIP] > > === Running test ./acloca20.test > ++ pwd > /cygdrive/c/m2sync/automake-1.11/tests/acloca20.dir > + set -e > + cat > + cat > + cat > + autoconf > Can't open perl script > "/cygdrive/c/Xilinx/12.4/ISE_DS/EDK/cygwin/bin/autom4te": No such file or > directory > + exit_status=2 > Since the autom4te and autoconf scripts are only used by Automake, but not installed nor managed by it (they are part of the Autoconf package), this failure suggests that the fault does not lie in the Automake build system, but rather in some system misconfiguration ... Are you sure your Cygwin installation is correct and sane? Thanks, Stefano
