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,
>
On 07/29/2012 13:50, Gerald Pfeifer wrote:
> On Sat, 9 Jun 2012, Doug Barton wrote:
>>> Are you saying you actually noticed some leftovers in /tmp, or that
>>> there "just" has been more at certain points in time than you would
>>> expect?
>> I finally had time to watch this closely, and found the
On Sat, 9 Jun 2012, Doug Barton wrote:
>> Are you saying you actually noticed some leftovers in /tmp, or that
>> there "just" has been more at certain points in time than you would
>> expect?
> I finally had time to watch this closely, and found the culprit(s).
> While building the port creates a l
On 06/09/2012 09:33, Doug Barton wrote:
> On 06/06/2012 23:15, Gerald Pfeifer wrote:
>> On Wed, 6 Jun 2012, Doug Barton wrote:
>>> I purposely have a tiny /tmp, and while building gcc46 today it
>>> filled up with "stuff" from the gcc build. Is there any way to
>>> modify this process so that it ke
On 06/06/2012 23:15, Gerald Pfeifer wrote:
> On Wed, 6 Jun 2012, Doug Barton wrote:
>> I purposely have a tiny /tmp, and while building gcc46 today it
>> filled up with "stuff" from the gcc build. Is there any way to
>> modify this process so that it keeps everything in WRKDIR?
>
> GCC in general
On Wed, 6 Jun 2012, Doug Barton wrote:
> I purposely have a tiny /tmp, and while building gcc46 today it
> filled up with "stuff" from the gcc build. Is there any way to
> modify this process so that it keeps everything in WRKDIR?
GCC in general should put all its build stuff in WRKDIR and only
st
on 07/06/2012 04:33 Doug Barton said the following:
> I purposely have a tiny /tmp, and while building gcc46 today it filled
> up with "stuff" from the gcc build. Is there any way to modify this
> process so that it keeps everything in WRKDIR?
I think that gcc honors TMPDIR environment variable if
I purposely have a tiny /tmp, and while building gcc46 today it filled
up with "stuff" from the gcc build. Is there any way to modify this
process so that it keeps everything in WRKDIR?
Doug
--
This .signature sanitized for your protection
___
fre
