bug-autoconf
[Top][All Lists]
Advanced

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

Re: [GNU Autoconf 2.59] testsuite: 90 failed


From: Stepan Kasal
Subject: Re: [GNU Autoconf 2.59] testsuite: 90 failed
Date: Tue, 27 Sep 2005 18:08:54 +0200
User-agent: Mutt/1.4.1i

Hello,

On Mon, Sep 26, 2005 at 12:53:07PM -0400, ken koehler wrote:
> I encountered this failure while building Linux From Scratch 6.1 on an 
> athlon64 [...]

> Failed tests:
>   90: semantics.at:425   AC_C_BIGENDIAN
>       cross

first, thanks to Ken the bug report and for his support.

When I unpacked the tarball which Ken mailed me, I saw the reason:
the system was too quick, and autoheader, called without --force,
thought that the previous autom4te.cache/* files were up-to-date.

So this was a bug in the testsuite, not in the Autoconf itself.

The fix is to add --force to the autoheader call.

Actually, I think there are more places where this problem can appear.
I added --force to AC_CHECK_AUTOCONF; thus all autoconf calls
are with --force.

I committed the patch, as attached to this mail.

Please note that if "autoconf --force" regenerates autom4te.cache/*, then
the subsequent autoheader works: autoheader always creates config.hin,
but the problem was only with autom4te.

Couldn't autom4te also compute some checksums of the input files?

(If Bruno is here, he would suggest that the autom4te caching should be
swiched off by default, right?)

Have a nice day,
        Stepan

Attachment: autoconf-20050927-force.patch
Description: Text document


reply via email to

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