On Sunday 14 November 2010, Ralf Wildenhues wrote: > Hello Stefano, > > I think it is time to reevaluate some of the work that has been done in > the last few weeks. I'd like to ask you to postpone pushes of pending > stuff that has a clock ticking, and look at the lots of new failures > that a testsuite run shows on a few hosts; you can find them in some > minutes on <http://autobuild.josefsson.org/automake/>.
Log: <http://autobuild.josefsson.org/automake/log-201011141902214780000.txt> Minimal system information: configure: autobuild project... GNU Automake configure: autobuild revision... v1.11-225-gcdd3cf3 configure: autobuild hostname... yawara configure: autobuild mode... default configure: autobuild timestamp... 20111412T185841Z running CONFIG_SHELL=/bin/sh /bin/sh ../automake/configure -C --prefix=/tmp/local/powerpc-ibm-aix5.3.0.0 checking build system type... powerpc-ibm-aix5.3.0.0 -*-*-*- > FAIL: ansi.test (exit: 2) > ========================= > > /tmp/am/build-powerpc-ibm-aix5.3.0.0/tests:/tmp/local/powerpc-ibm-aix5.3.0.0/bin:/tmp/bin > :/usr/vac/bin:/usr/vacpp/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/X11:/etc:/usr/etc > + pwd > /tmp/am/build-powerpc-ibm-aix5.3.0.0/tests/ansi.dir > + set -e > + cat > + 1> Makefile.am 0< /tmp/sh663580.2 > + cat > + 1>> configure.in 0< /tmp/sh663580.4 > + : > + 1> ansi2knr.c > + : > + 1> ansi2knr.1 > + aclocal-1.11a -Werror > + automake-1.11a --foreign -Werror -Wall > + /bin/grep -F -v @SET_MAKE@ Makefile.in > + 1> Makefile.sed > + make -f Makefile.sed SHELL=/bin/sh test1 > echo ' @top_srcdir@/configure.in @top_srcdir@/aclocal.m4 > @srcdir@/Makefile.am \ > @srcdir@/Makefile.in @top_srcdir@/configure ansi2knr.1 > ansi2knr.c \ > depcomp install-sh missing ' | grep ' ansi2knr\.c ' > @SHELL@: not found > make: 1254-004 The error code from the last command is 1. > Stop. > + exit_status=2 IMHO this is a spurious failure due to the old hackish check: $FGREP -v @SET_MAKE@ Makefile.in > Makefile.sed $MAKE -f Makefile.sed SHELL=$SHELL test1 retained from older versions of ansi.test; since this check is superseded by the later ones: $AUTOCONF ./configure $MAKE test1 my suggested fix is to just drop the hackish check. -*-*-*- > FAIL: colon5.test (exit: 2) > FAIL: colon6.test (exit: 2) These tests fail for the same resons of ansi.test; I suggest to drop the older hackish checks and do more proper checks with autoconf, ./configure and make. BTW, there is a pending patch of mine aimed at making the `colon*.test' tests more "semantic"; see: <http://lists.gnu.org/archive/html/automake-patches/2010-09/msg00110.html> -*-*-*- > FAIL: fn99.test (exit: 2) > FAIL: fn99subdir.test (exit: 2) I'm pretty sure these tests haven't been affected by my (or yours) latest patches: the failure is pre-existent IMO. Also, the tests fails due to a segmentation fault in the (make-spawned) shell, so the failures are better investigated by someone having direct access to the system in question. -*-*-*- Regards, Stefano