From owner-freebsd-ports@FreeBSD.ORG  Thu Jun  7 06:23:33 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id BFDF4106566C;
	Thu,  7 Jun 2012 06:23:33 +0000 (UTC)
	(envelope-from gerald@pfeifer.com)
Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66])
	by mx1.freebsd.org (Postfix) with ESMTP id 9DA588FC14;
	Thu,  7 Jun 2012 06:23:33 +0000 (UTC)
Received: from [192.168.0.130] (vie-91-186-145-172.dsl.sil.at [91.186.145.172])
	by ainaz.pair.com (Postfix) with ESMTPSA id 3498B3F47C;
	Thu,  7 Jun 2012 02:15:28 -0400 (EDT)
Date: Thu, 7 Jun 2012 08:15:28 +0200 (CEST)
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Doug Barton <dougb@FreeBSD.org>
In-Reply-To: <4FD004F7.6090401@FreeBSD.org>
Message-ID: <alpine.LNX.2.00.1206070808380.2395@gerinyyl.fvgr>
References: <4FD004F7.6090401@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: freebsd-ports@FreeBSD.org
Subject: Re: lang/gcc46 building stuff in $TMPDIR
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2012 06:23:33 -0000

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
stash really temporary things (coming from an individual invocation
of GCC such as assembly files if any) in /tmp for short periods of
time.

I am not aware of anything we could do beyond what I already have
in the port, but then this is the first time I hear about this, in
the context of FreeBSD and also upstream.

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?

Gerald