bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Autoconf 2.69] 141 suite failed


From: Vladimir Kraljević
Subject: Re: [GNU Autoconf 2.69] 141 suite failed
Date: Wed, 24 Oct 2012 03:12:34 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121017 Thunderbird/16.0.1

Indeed - when I omitted the map file generation, only one test failed
(279: AC_PROG_CPP without warnings), I attached the testsuite.log, if it
can be of any use to you.

Thank you on your fast response!

Best,
Vladimir


On 10/23/2012 09:50 PM, Eric Blake wrote:
> On 10/23/2012 12:23 PM, Vladimir Kraljević wrote:
>>
>> [GNU Autoconf 2.69] testsuite: 270 273 274 276 277 278 279 280 281 283
> 
> Thanks for the report.  It looks like most (all?) of the tests have the
> same failure pattern:
> 
> ./compile.at:390: at_check_env
> --- /dev/null 2012-10-23 10:44:10.100839502 +0200
> +++
> /home/vlaad/work/autoconf-2.69/tests/testsuite.dir/at-groups/270/stdout
> 2012-10-23 19:21:56.214660033 +0200
> @@ -0,0 +1,8 @@
> +--- state-ls.before  2012-10-23 19:21:55.121658875 +0200
> ++++ state-ls.after   2012-10-23 19:21:56.159659977 +0200
> +@@ -4,4 +4,5 @@
> + configure
> + configure.ac
> + install-sh
> ++output.map
> + testsuite.log
> ./compile.at:390: exit code was 1, expected 0
> 
> That is, your compilation environment is creating a file named
> output.map, but the 'at_check_env' test is not accounting for this file.
>  It may mean that autoconf needs to do a better job of deleting this
> file when cleaning up after a test of $CC.
> 

Attachment: 201210240306-testsuite.tar.xz
Description: application/xz

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]