From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Experiment: confcache patch for portage-2.0.50-r10
Date: Fri, 10 Sep 2004 10:06:07 +0200 [thread overview]
Message-ID: <200409101006.15081.pauldv@gentoo.org> (raw)
In-Reply-To: <200409092212.21995.stuart@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Thursday 09 September 2004 23:12, Stuart Herbert wrote:
> Hi,
>
> GNU autoconf is a bottleneck for compiling packages - especially on
> multi-processor boxes. It supports the idea of a cache, but provides
> no tools for maintaining the cache at all.
>
> I've put together an experimental patch for Portage 2.0.50-r10, which
> maintains a cache for configure to reuse. You can find it here:
>
> http://dev.gentoo.org/~stuart/confcache/
>
> Once you've patched and re-installed Portage, to activate the cache,
> make sure you have both 'sandbox' and 'confcache' set in FEATURES in
> /etc/make.conf. This feature only helps ebuilds which call 'econf'.
>
> I'd be interested in getting some feedback on this patch, as well as
> any suggested improvements.
Great. One other thing is that many configure functions also support some
kind of presets where the answers can be provided (site configuration) in
`PREFIX/etc/config.site'. This is not a cache but a way to set defaults.
I think we could also look into that.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-10 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 21:12 [gentoo-dev] Experiment: confcache patch for portage-2.0.50-r10 Stuart Herbert
2004-09-10 8:06 ` Paul de Vrieze [this message]
2004-09-10 17:40 ` Stuart Herbert
2004-09-10 8:32 ` Paul de Vrieze
2004-09-10 17:42 ` Stuart Herbert
2004-09-10 21:14 ` Paul de Vrieze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409101006.15081.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox