On 11/19/2012 02:32 PM, Richard Stallman wrote:
> I personally spent quite a significant amount of time fixing a few
> configure.{ac,in} files in various packages, but in the end, we gave up
> with this idea and no longer use the autoconf cache.
>
> If we use the cache for standard tests only, could that fix this
> problem?
Therein lies the problem. How do you identify which tests are standard,
vs. those tests that are dependent on compiler options currently in
effect or previously detected libraries in effect, when each package's
choice of earlier actions before running the same standard test may have
led to different results when run without the cache?
I'm all ears for a solution that allows cache reuse across multiple
projects, but so far, have not seen any patches that have solved the
issue, nor am I able to devote the significant amount of time that I
think it would take to get a working solution that isn't also a source
of a slowdown in the common case.
--
Eric Blake eblake@xxxxxxxxxx +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
