[Top][All Lists]

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

Re: configure -C by default?

From: Eric Blake
Subject: Re: configure -C by default?
Date: Mon, 07 Feb 2011 08:30:51 -0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7

On 02/06/2011 03:11 PM, Ralf Wildenhues wrote:
> Apparently, a lot of users do not even know about configure -C aka.
> --config-cache which of course doesn't help Autoconf's reputation about
> producing configure scripts which are slow even for development.
> So one question would be what about making -C the default?
> We could have --force or --no-cache to turn it off.

I prefer to keep it off by default, but wouldn't mind advertising that
(when used correctly) it does provide great speedups within a single

Personally, I use it all the time.  It makes a HUGE difference for
cygwin, but even on Linux, it is a noticeable speed improvement.  And
yes, stale caches are still very much a real issue - cross-package
caches are too dangerous, and I have run into issues where stale caches
bite me (for example, if gnulib enhances a configure test that marks a
platform's function as non-compliant where it used to be compliant);
I've gotten into the habit of nuking config.cache any time I update
gnulib as a result.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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