Date: Mon, 13 May 2002 11:38:49 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bruce Evans <bde@zeta.org.au> Cc: Gregory Sutter <gsutter@zer0.org>, 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: <12094.1021282729@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 13 May 2002 19:33:49 %2B1000." <20020513192732.E12860-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020513192732.E12860-100000@gamplex.bde.org>, Bruce Evans writes: >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. You mean "fast *r*e*builds", right ? >I haven't tried it. Does it handle changes in include files and >nonstandard paths to include files properly? It can be made to. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?12094.1021282729>