From: rst@ai.mit.edu (Robert S. Thau)
Date: Tue, 16 Apr 1996 20:21:52 -0400
Message-Id: <199604170021.UAA21409@volterra.ai.mit.edu>
To: new-httpd@hyperreal.com
Subject: Re: conditional HTML
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com
Status: O

  Caching should help out here.  If you use caching (all the standard
  tests do), then the tests don't actually get re-run -- the results are
  just taken from the cache.

[pokes around, tries a few configure scripts out...]

Yep.  A cache file helps a great deal when the package you are
configuring has a configure script which is recent enough to create
one.  Yours is, which I guess is the important point for this
particular argument, and I concede the point.  (It sometimes winds up
rerunning a few tests anyway, but not enough to matter).

(I can't find a cache for gcc, but that seems to be an odd duck in a
lot of respects --- I can't catch it running any tests either.  This
is with the gcc-2.7.2 distribution that was lying around in our
/src/local directory; I diffed the configure script against the one
from a fresh distribution I pulled over from prep, and it didn't
*seem* to be any different, but on our systems there is always the
possibility of something a little screwy floating around, particularly
with odd things occasionally floating up from downstairs).

rst