From owner-freebsd-ports@FreeBSD.ORG Mon Jun 9 15:48:20 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 084149AD; Mon, 9 Jun 2014 15:48:20 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 823CE2475; Mon, 9 Jun 2014 15:48:19 +0000 (UTC) Received: from [192.168.200.105] (c-50-131-4-11.hsd1.ca.comcast.net [50.131.4.11]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 0FB401936DE; Mon, 9 Jun 2014 15:48:18 +0000 (UTC) Subject: Re: gcc vs gcc48 From: Sean Bruno Reply-To: sbruno@freebsd.org To: Alex Dupre In-Reply-To: <5395D387.8020902@FreeBSD.org> References: <1402327321.76875.8.camel@bruno> <5395D387.8020902@FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Date: Mon, 09 Jun 2014 08:48:15 -0700 Message-ID: <1402328895.76875.11.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: ports list X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 15:48:20 -0000 On Mon, 2014-06-09 at 17:32 +0200, Alex Dupre wrote: > Sean Bruno ha scritto: > > Ended up in a weird position today running a build. My poudriere > > instance ended up building gcc and gcc48 at the same time. > > > > I thought this was odd. Shouldn't gcc48 supplant gcc for requirements? > > Every port is built independently from the others, so gcc48 is not found > when building other ports that doesn't strictly require it. > Understood. lang/gcc isn't successfully building at the moment. So, when I restart this build, gcc48 will be detected as built so it will be pulled in. Which will in turn start building the ports that were failed on the previous run. This seems like a broken "feature" of ports IMO. I.e. non-consistent runs. sean