From owner-freebsd-ports@FreeBSD.ORG Mon Jan 20 15:28:34 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1A2BEDA for ; Mon, 20 Jan 2014 15:28:34 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB4411A69 for ; Mon, 20 Jan 2014 15:28:34 +0000 (UTC) Received: from [192.168.0.23] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 4C59A438BC; Mon, 20 Jan 2014 09:28:19 -0600 (CST) Message-ID: <52DD4081.8030800@marino.st> Date: Mon, 20 Jan 2014 16:28:01 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: nano Subject: Re: Build fail: Do not define STAGEDIR in command line References: <52DCFD62.5020603@bsdbox.co> <52DD3FC9.1050002@bsdbox.co> In-Reply-To: <52DD3FC9.1050002@bsdbox.co> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 15:28:34 -0000 On 1/20/2014 16:24, nano wrote: > Trying to build ports with "portmaster -f" after > upgrading to 10.0-RELEASE results in build error: > > ===> $PORTNAME Do not define STAGEDIR in command line. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/$PORTSCATEGORY/$PORTSDIR > > > All ports with "NO_STAGE=yes" in $PORTSDIR/Makefile are failing with the > above error. I suspect your portstree isn't up to date. That should have been fixed this morning. John