From owner-freebsd-bugs@FreeBSD.ORG Thu Sep 5 17:59:36 2013 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id A2BAF50B; Thu, 5 Sep 2013 17:59:36 +0000 (UTC) Date: Thu, 5 Sep 2013 17:59:36 +0000 From: Alexey Dokuchaev To: "Simon J. Gerraty" Subject: Re: bin/178819: bmake w/ WRKDIRPEFIX=/tmp breaks Ports Collection Message-ID: <20130905175936.GB58718@FreeBSD.org> References: <201309030703.r8373BSU072280@freefall.freebsd.org> <20130905164552.3639E5807E@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130905164552.3639E5807E@chaos.jnpr.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-bugs@FreeBSD.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2013 17:59:36 -0000 Yes, I've seen the fresh import; will test it tomorrow. I'm not sure what is the problem, but "ports should be able to control the value of MAKEFILE as desired" looks strange. MAKEFILE is one of the standard bsd.port.mk's variables, and ports were always able to control it. Are you referring to something else (e.g. internal bmake(1)'s variable)? And how does this all got affected by WRKDIRPREFIX=/tmp?