Subject: bug#29638: Five failed tests in automake 1.15.1 with RHEL 7.4

From: Dennis Clarke <[email-masked]>
Date: Sun, 10 Dec 2017 00:43:32 -0500

This is on Red Hat Enterprise Linux 7.4 and a fairly trivial config.

============================================================================
Testsuite summary for GNU Automake 1.15.1
============================================================================
# TOTAL: 2695
# PASS:  2420
# SKIP:  230
# XFAIL: 40
# FAIL:  5
# XPASS: 0
# ERROR: 0
============================================================================

Failures were :

FAIL: t/aclocal.sh
FAIL: t/automake-cmdline.tap 4 - list of options terminated by '--' (stderr)
FAIL: t/automake-cmdline.tap 17 - unambiguous incomplete long option
FAIL: t/maken3.sh
FAIL: t/maken3-w.sh

The configure was trivial :

$ ./configure --libdir=/usr/local/lib64
checking whether /usr/local/bin/gmake supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether /usr/local/bin/gmake sets $(MAKE)... yes
checking whether ln -s works... yes
checking for perl... /bin/perl
checking for tex... no
checking for yacc... no
checking for byacc... no
checking for bison... no
checking for lex... no
checking for flex... no
checking whether autoconf is installed... yes
checking whether autoconf works... yes
checking whether autoconf is recent enough... yes
checking whether ln works... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
configure: will now look for a sturdy POSIX shell, for our testsuite
checking for sh... /bin/sh
checking for sh5... no
checking for dash... no
checking for ash... no
checking for bash... /bin/bash
checking for zsh... no
checking for ksh... no
checking for pdksh... no
checking whether /bin/sh supports $(cmd)... yes
checking whether /bin/sh supports $((expr))... yes
checking whether /bin/sh supports ${#var}... yes
checking whether /bin/sh supports ${var#glob} and ${var%glob}... yes
checking whether /bin/sh preserves exit traps with "set -e"... yes
checking whether /bin/sh can define exit traps in a shell function... yes
checking whether /bin/sh corrupts stderr with "set -x"... no
checking whether /bin/sh can return early from "dot-sourced" files... yes
checking whether /bin/sh supports alias named like shell builtins... yes
checking whether /bin/sh supports "test -e"... yes
configure: shell /bin/sh is good enough, stop looking
configure: will use /bin/sh as the testsuite shell
configure: will now look for generic compilers
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking whether cc understands -c and -o together... yes
checking for aCC... no
checking for CC... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for c++... c++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking for xlf95... no
checking for f95... f95
checking whether the Fortran compiler works... yes
checking for Fortran compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU Fortran compiler... yes
checking whether f95 accepts -g... yes
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for g77... no
checking for gfortran... gfortran
checking whether the Fortran 77 compiler works... yes
checking for Fortran 77 compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
configure: will now look for GNU compilers
configure: cc is already a GNU C compiler
configure: c++ is already a GNU C++ compiler
configure: f95 is already a GNU Fortran compiler
configure: gfortran is already a GNU Fortran 77 compiler
checking for gcj... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating t/wrap/aclocal-1.15
config.status: creating t/wrap/automake-1.15

See test-suite.log.xz attached.

Dennis Clarke