From owner-svn-ports-all@FreeBSD.ORG Thu Feb 27 14:03:30 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6D433B26; Thu, 27 Feb 2014 14:03:30 +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 C77571C05; Thu, 27 Feb 2014 14:03:28 +0000 (UTC) Received: from [192.168.0.21] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 21DA4438BC; Thu, 27 Feb 2014 08:03:10 -0600 (CST) Message-ID: <530F458B.1050209@marino.st> Date: Thu, 27 Feb 2014 15:02:51 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Tijl Coosemans , Gerald Pfeifer Subject: Re: svn commit: r336343 - in head: . Mk/Uses References: <201312131322.rBDDMWZC038800@svn.freebsd.org> <20131217215533.3c0d9fcb@kalimero.tijl.coosemans.org> <20131217210048.GM99753@ithaqua.etoilebsd.net> <20140227145638.4d6d9307@kalimero.tijl.coosemans.org> In-Reply-To: <20140227145638.4d6d9307@kalimero.tijl.coosemans.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Baptiste Daroussin , svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 14:03:30 -0000 On 2/27/2014 14:56, Tijl Coosemans wrote: > On Wed, 26 Feb 2014 23:03:08 +0100 (CET) Gerald Pfeifer wrote: > >> And it makes USES=fortran picking up the compiler specified with >> USE_GCC=X.Y, as a number of committers/users have asked the last >> months, harder. > > There are no ports with that combination at the moment, but I'm also not > sure it would be a good thing to let the choice of Fortran compiler > depend on USE_GCC=x.y. It's much safer to have all Fortran code on a > system compiled with one compiler. Er, no, Gerald is correct. The fortran compiler used needs to be the same as USE_GCC. I know this from experience with use of my ALTCOMPILER patch (pending approval). The fact that fortran was hardcoded to gcc4.6 was the source of breakage. Gerald fixed something that I've had a pending patch for a few months now. John