Date: Mon, 13 May 2002 19:33:49 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Gregory Sutter <gsutter@zer0.org> Cc: cvs-all@FreeBSD.org, <cvs-committers@FreeBSD.org> Subject: Re: buildworld speed (was: Re: GCC bugs (was: cvs commit: src/sys/alpha/include atomic.h)) Message-ID: <20020513192732.E12860-100000@gamplex.bde.org> In-Reply-To: <20020513080401.GC85170@klapaucius.zer0.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 May 2002, Gregory Sutter wrote: > On 2002-05-13 17:30 +1000, Bruce Evans <bde@zeta.org.au> wrote: > > > > Running makeworld fast is important to me. Anything longer than 5-10 > > minutes is too long, since it is not reasonable to check every commit > > using makeworld if it takes longer. I was hoping to get a 20 minute > > makeworld on the Athlon1400XP, but my best time so far was 23 minutes > > 42 seconds using my version of makeworld back on Feb 24. The current > > version took about 2 minutes longer. Now with gcc-3, the buildworld > > time for -current has bloated to 37 minutes 48 seconds. > > How does ccache (ports/devel/ccache) affect your build time? Its use > has resulted in some very fast builds on systems here. I haven't tried it. Does it handle changes in include files and nonstandard paths to include files properly? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020513192732.E12860-100000>