[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.63] testsuite: 144 failed
From: |
Eric Blake |
Subject: |
Re: [GNU Autoconf 2.63] testsuite: 144 failed |
Date: |
Wed, 10 Sep 2008 19:42:45 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Bob Friesenhahn <bfriesen <at> simple.dallas.tx.us> writes:
>
> The testsuite.log showing a failed test under Solaris 10 is attached.
And the interesting portion:
! 144. base.at:295: testing ...
! /home/bfriesen/src/gnu/autoconf-2.63/tests/base.at:302: autoconf --force
! /home/bfriesen/src/gnu/autoconf-2.63/tests/base.at:303: echo Hello |
! ./configure | grep -v 'configure: loading site script '
! 0a1,10
! > Applying settings for 32-bit build ...
! > Using GCC 4.2.3 ...
>
> Please let me know if the release is still safe to use based on what
> failed.
Looks like the culprit is a verbose config.site. Therefore, this represents a
testsuite bug, where the testsuite is not tolerant of the extra output from
your config.site, and not a bug in the built autoconf. You are safe to install
this release, and I will work on a patch to make the testsuite more tolerant of
setups like yours. In other words, the testsuite currently builds configure.ac
like so:
[[AC_INIT
cat <&AS_ORIGINAL_STDIN_FD >&AS_MESSAGE_FD
]])
when it should really do something like:
[[AC_INIT
echo >&AS_MESSAGE_FD
echo string not likely to be printed by verbose config.site >&AS_MESSAGE_FD
cat <&AS_ORIGINAL_STDIN_FD >&AS_MESSAGE_FD
]])
and swap from "grep -v 'configure...'" to "sed '1,/not likely/d'".
In the meantime, you may want to patch your config.site to be silent.
--
Eric Blake