From owner-svn-ports-head@freebsd.org Sun Nov 15 23:30:47 2015 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B4F5A30E63; Sun, 15 Nov 2015 23:30:47 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 5AEB8104C; Sun, 15 Nov 2015 23:30:46 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from [192.168.0.130] (vie-188-118-240-003.dsl.sil.at [188.118.240.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 5EFAC3F44C; Sun, 15 Nov 2015 18:30:43 -0500 (EST) Date: Mon, 16 Nov 2015 00:30:41 +0100 (CET) From: Gerald Pfeifer To: John Marino cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r384521 - head/Mk In-Reply-To: <5540A388.5070005@marino.st> Message-ID: References: <201504222129.t3MLTLut046445@svn.freebsd.org> <5538D221.2090804@marino.st> <5540A388.5070005@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 23:30:47 -0000 On Wed, 29 Apr 2015, John Marino wrote: > To follow up on this topic, I realized the situation was not > sustainable. I wrote a replacement file called bsd.df.gcc.mk which gets > pulled in by bsd.port.mk instead of bsd.gcc.mk on DPorts. As a bonus, > the makefile "code" is much clearer than bsd.gcc.mk and it's easy for me > to maintain (and basically static). > > TLDR: DPorts doesn't use bsd.gcc.mk anymore, you can do what you want > with it without asking if it breaks DragonFly. Thanks for the heads up, John, and sorry for the breakage. I had not been aware that you had been using this on the DragonFly side as well and my simplifications were causing issues. And finally having been able to check out bsd.df.gcc.mk last weekend, I agree that this seems quite simpler and better for that use. Gerald