Date: Mon, 30 Jul 2012 21:28:39 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: lang/gcc46 building stuff in $TMPDIR Message-ID: <alpine.LNX.2.00.1207302121030.2533@gerinyyl.fvgr> In-Reply-To: <5015AC6F.2040001@FreeBSD.org> References: <4FD004F7.6090401@FreeBSD.org> <alpine.LNX.2.00.1206070808380.2395@gerinyyl.fvgr> <4FD37AD7.7010304@FreeBSD.org> <4FFC5189.1000102@dougbarton.us> <alpine.LNX.2.00.1207292039220.2303@gerinyyl.fvgr> <5015AC6F.2040001@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 29 Jul 2012, Doug Barton wrote: >>> My suggestion would be to create a directory in $WRKDIR and assign >>> $TMP (or whatever the right envar is) to it. >> That could be done, but has one significant drawback: those of us >> who have /tmp on fastest storage, and $WRKDIR on slower storage, >> could lose a lot of speed. > Have you measured that? 1:15:27 for a full build of lang/gcc48 when /tmp was used, versus 1:34:25 on the same system when TMPDIR was set to a network drive. This is just one scenario, and it may go both ways. It does show that having temporary files on fast storage is significant. [i386 host, build including Java, storage on spindles.] >> Finally, you indicated that you also saw Java create a large >> temporary file. If you want to avoid building Java, the GCC >> ports have an option to disable Java. > Reducing functionality to handle build infrastructure problems is > not a desirable solution. But thanks for the response in any case. :) Reducing functionality if that cuts the cost of building in half and you do not actually use that functionality (only a single port does, from what I know) actually looks quite desirable to me. ;-) Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.1207302121030.2533>