severity 12276 minor close 12276 thanks Hi Elham, thanks for the report.
> On 08/25/2012 10:59 PM, elham abbaszade wrote: > > GNU Automake 1.11.3: tests/test-suite.log > This Automake version is quite outdated, and suffers from a known security vulnerability: <http://lists.gnu.org/archive/html/automake/2012-07/msg00023.html> I suggest you to upgrade to 1.11.6, or (even better) to 1.12.3. That said, let's see the failure you've reported ... > FAIL: conffile-leading-dot.test (exit: 1) > ========================================= > > /sources/automake-1.11.3/tests:/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin > conffile-leading-dot: running make --version -v | grep GNU > GNU Make 3.82 > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > === Running test ./conffile-leading-dot.test > ++ pwd > /sources/automake-1.11.3/tests/conffile-leading-dot.dir > + set -e > + cat > + echo foo = barbarbar > + touch a.in b.in c.in > + aclocal-1.11 -Werror > + AUTOMAKE_fails -Wnone -Wunsupported > + AUTOMAKE_run 1 -Wnone -Wunsupported > + expected_exitcode=1 > + shift > + exitcode=0 > + automake-1.11 --foreign -Werror -Wall -Wnone -Wunsupported > + exitcode=1 > + cat stderr > configure.in:3: omit leading './' from config file names such as './Makefile'; > configure.in:3: remake rules might be subtly broken otherwise > configure.in:4: omit leading './' from config file names such as './foo'; > configure.in:4: remake rules might be subtly broken otherwise > + cat stdout > + test 1 = 1 > + grep '^configure\.in:3:.*'\''\./Makefile'\''' stderr > configure.in:3: omit leading './' from config file names such as './Makefile'; > + grep '^configure\.in:3:.* omit leading '\''\./'\''' stderr > configure.in:3: omit leading './' from config file names such as './Makefile'; > + grep '^configure\.in:3:.*remake rules might be subtly broken' stderr > configure.in:3: remake rules might be subtly broken otherwise > + grep '^configure\.in:4:.*'\''\./foo'\''' stderr > configure.in:4: omit leading './' from config file names such as './foo'; > + grep '^configure\.in:4:.* omit leading '\''\./'\''' stderr > configure.in:4: omit leading './' from config file names such as './foo'; > + grep '^configure\.in:4:.*remake rules might be subtly broken' stderr > configure.in:4: remake rules might be subtly broken otherwise > + autoconf -B /no/such/dir > + automake-1.11 --foreign -Werror -Wall -Wall -Wno-unsupported > + ./configure > checking for a BSD-compatible install... /usr/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 make sets $(MAKE)... yes > configure: creating ./config.status > config.status: creating ./Makefile > config.status: creating ./foo > + make > make: Nothing to be done for `all'. > + grep barbarbar Makefile > foo = barbarbar > + echo foo = bazbazbaz > + make > cd . && /bin/sh > /sources/automake-1.11.3/tests/conffile-leading-dot.dir/missing --run > automake-1.11 --foreign ./Makefile > make: Nothing to be done for `all'. > + cat stderr Exit 1 > configure.in:3: omit leading './' from config file names such as './Makefile'; > configure.in:3: remake rules might be subtly broken otherwise > configure.in:4: omit leading './' from config file names such as './foo'; > configure.in:4: remake rules might be subtly broken otherwise > cat: Exit: No such file or directory > cat: 1: No such file or directory > + exit_status=1 > + set +e > + cd /sources/automake-1.11.3/tests > + case $exit_status,$keep_testdirs in > + test 0 '!=' 0 > + echo 'conffile-leading-dot: exit 1' > conffile-leading-dot: exit 1 > + exit 1 This sounds exactly as the spurious failure already fixed in commit v1.11-764-gd6f2cc9: tests: fix a timestamp issue, and other minor buglets Cherry picked from commit v1.11-1988-g82616f0 of 21-02-2012. Reported by Panther Martin in automake bug#10848. See also automake bug#11093. * tests/conffile-leading-dot.test: Add a proper '$sleep' invocation, to avoid spurious failures on fast systems without sub-second timestamp resolutions. Add other minor related and unrelated improvements and fixlets since we are at it. See also: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10848> Since that issue has already been fixed, I'm closing this bug report. Thanks, Stefano