- According to this new scheme, the next major version of Automake
(the one that had previously been labelled as "1.14") will actually
- become "Automake 2.0". Automake 1.14 is *this* release (which is
- a minor one). It introduces new features, deprecations and bug
- fixes, but no serious backward incompatibility. A partial exception
- is given by the behavioural changes in the AM_PROG_CC_C_O macro
- (described in details below) but such changes can also be seen as a
- fix for the old suboptimal and somewhat confusing behaviour.
+ become "Automake 2.0". Automake 1.14 has already been released as
+ the last minor release, and the present one is a bug-fixing release
+ following up on that one.
- See discussion about automake bug#13578 for more details and
background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
Ulrich Eckhardt eckhardt@satorlaser.com
Václav Haisman V.Haisman@sh.cvut.cz
Vadim Zeitlin Vadim.zeitlin@dptmaths.ens-cachan.fr
+Vasyl Khalak basiliomail@gmail.com
Vincent Lefevre vincent@vinc17.org
Vladimir Serbinenko phcoder@gmail.com
Volker Boerchers vboerchers@tecon.de
#! /bin/sh
# test-driver - basic testsuite driver script.
-scriptversion=2012-06-27.10; # UTC
+scriptversion=2013-07-13.22; # UTC
# Copyright (C) 2011-2013 Free Software Foundation, Inc.
#
Usage:
test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
[--expect-failure={yes|no}] [--color-tests={yes|no}]
- [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
+ [--enable-hard-errors={yes|no}] [--]
+ TEST-SCRIPT [TEST-SCRIPT-ARGUMENTS]
The '--test-name', '--log-file' and '--trs-file' options are mandatory.
END
}
-# TODO: better error handling in option parsing (in particular, ensure
-# TODO: $log_file, $trs_file and $test_name are defined).
test_name= # Used for reporting.
log_file= # Where to save the output of the test script.
trs_file= # Where to save the metadata of the test run.
--enable-hard-errors) enable_hard_errors=$2; shift;;
--) shift; break;;
-*) usage_error "invalid option: '$1'";;
+ *) break;;
esac
shift
done
+missing_opts=
+test x"$test_name" = x && missing_opts="$missing_opts --test-name"
+test x"$log_file" = x && missing_opts="$missing_opts --log-file"
+test x"$trs_file" = x && missing_opts="$missing_opts --trs-file"
+if test x"$missing_opts" != x; then
+ usage_error "the following mandatory options are missing:$missing_opts"
+fi
+
+if test $# -eq 0; then
+ usage_error "missing argument"
+fi
+
if test $color_tests = yes; then
# Keep this in sync with 'lib/am/check.am:$(am__tty_colors)'.
red='\e[0;31m' # Red.
|| rm -rf $distdir || exit 1
test ! -e $distdir
fi
- xz -dc $tarball | tar xf -
- cd $distdir
+ export $env
"'
am_extra_acdir=$HOME/.am-test/extra-aclocal
am_extra_bindir=$HOME/.am-test/extra-bin
export PATH=$am_extra_bindir:$PATH
fi
'"
- export $env
+ xz -dc $tarball | tar xf -
+ cd $distdir
if test -f \"\$am_extra_setup\"; then
. \"\$am_extra_setup\"
fi
# in the environment "by hand" before calling the testsuite.
export CC CPPFLAGS
echo "$me: running $CC -?"
- $CC -? || skip_all_ "Microsoft C compiler '$CC' not available"
+ # The IRAF package (http://iraf.noao.edu/) contains a 'cl' program
+ # which is interactive, and which could cause the testsuite to hang
+ # if its standard input is not redirected. See automake bug#14707.
+ $CC -? </dev/null \
+ || skip_all_ "Microsoft C compiler '$CC' not available"
;;
etags)
# Exuberant Ctags will create a TAGS file even
$AUTOCONF
./configure 2>stderr || { cat stderr >&2; exit 1; }
cat stderr >&2
-test ! -s stderr
+# Ignore warning messages sometimes seen on Mac OS X; they are
+# not automake's fault anyway, but either autoconf's or Mac's.
+sed '/rm:.* conftest\.dSYM/d' stderr >stderr2
+test -s stderr2 && { cat stderr2; exit 1; }
: