Date: Thu, 27 Feb 2014 15:02:51 +0100 From: John Marino <freebsd.contact@marino.st> To: Tijl Coosemans <tijl@FreeBSD.org>, Gerald Pfeifer <gerald@pfeifer.com> Cc: svn-ports-head@freebsd.org, Baptiste Daroussin <bapt@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r336343 - in head: . Mk/Uses Message-ID: <530F458B.1050209@marino.st> In-Reply-To: <20140227145638.4d6d9307@kalimero.tijl.coosemans.org> References: <201312131322.rBDDMWZC038800@svn.freebsd.org> <alpine.LSU.2.11.1312160847420.2366@tuna.site> <20131217215533.3c0d9fcb@kalimero.tijl.coosemans.org> <20131217210048.GM99753@ithaqua.etoilebsd.net> <alpine.LSU.2.11.1402242318220.2233@tuna.site> <20140227145638.4d6d9307@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?530F458B.1050209>