autoconf 2.50 tests and cache

[mike burrell]

In addition to the problem outlined in the message below, it seems the
address address@hidden listed in the README is erroneous :)

Cheers

----- Forwarded message from Mail Delivery System <address@hidden> -----

From: Mail Delivery System <address@hidden>
To: address@hidden
Subject: Mail delivery failed: returning message to sender
Date: Tue, 22 May 2001 09:54:44 -0600
Message-Id: <address@hidden>

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:

  address@hidden:
    SMTP error from remote mailer after RCPT TO:
    <address@hidden>:
    host fencepost.gnu.org [199.232.76.164]:
    550 Unknown local part autoconf-bugs in <address@hidden>

------ This is a copy of the message, including all the headers. ------

Return-path: <address@hidden>
Received: from mikpos by mikpos.dyndns.org with local (Exim 3.03 #1)
        id 152EUc-0000OI-00
        for address@hidden; Tue, 22 May 2001 09:54:42 -0600
Date: Tue, 22 May 2001 09:54:41 -0600
From: mike burrell <address@hidden>
To: address@hidden
Subject: autoconf 2.50 tests and cache
Message-ID: <address@hidden>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: "mike burrell,,," <address@hidden>

I am having problems installing the newly released autoconf 2.50.

I use a single cache file for all packages I configure (by setting
cache_file).  When doing the tests ("make check" IIRC) for autoconf 2.50, it
seems to pollute this cache file.  Specifically, it seems to be happening
around compile.at:154, where it sets CPP to "./mycpp".  This value is then
stored in the cache file, and then all further tests involving CPP fail,
because they are (presumably) expecting a real pre-processor.

I have temporarily unset cache_file as a work-around.  All the tests are
passing now.

I haven't supplied a patch because I'm not familiar with the structure of
autoconf, but hopefully you can fix this somehow for the next release.

----- End forwarded message -----