From owner-svn-ports-all@FreeBSD.ORG Thu Feb 27 14:25:22 2014 Return-Path: Delivered-To: svn-ports-all@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 AD4D5A91; Thu, 27 Feb 2014 14:25:21 +0000 (UTC) Received: from mailrelay009.isp.belgacom.be (mailrelay009.isp.belgacom.be [195.238.6.176]) by mx1.freebsd.org (Postfix) with ESMTP id 94F611E32; Thu, 27 Feb 2014 14:25:19 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsGAN5JD1NR8Zjl/2dsb2JhbABagwaBBr4OgwmBGhd0giUBAQU6HCMQCxgJJQ8qHogWAcpmF45VBxaEIQEDlE2DapIrgy47 Received: from 229.152-241-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.241.152.229]) by relay.skynet.be with ESMTP; 27 Feb 2014 15:24:08 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.8/8.14.8) with ESMTP id s1REO4HG002922; Thu, 27 Feb 2014 15:24:05 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Thu, 27 Feb 2014 15:24:04 +0100 From: Tijl Coosemans To: marino@freebsd.org Subject: Re: svn commit: r336343 - in head: . Mk/Uses Message-ID: <20140227152404.50bdaa2b@kalimero.tijl.coosemans.org> In-Reply-To: <530F4818.2040300@marino.st> References: <201312131322.rBDDMWZC038800@svn.freebsd.org> <20131217215533.3c0d9fcb@kalimero.tijl.coosemans.org> <20131217210048.GM99753@ithaqua.etoilebsd.net> <20140227145638.4d6d9307@kalimero.tijl.coosemans.org> <530F458B.1050209@marino.st> <20140227150915.15e44b44@kalimero.tijl.coosemans.org> <530F4818.2040300@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: svn-ports-head@freebsd.org, Baptiste Daroussin , Gerald Pfeifer , svn-ports-all@freebsd.org, freebsd.contact@marino.st, ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list 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:25:22 -0000 On Thu, 27 Feb 2014 15:13:44 +0100 John Marino wrote: > On 2/27/2014 15:09, Tijl Coosemans wrote: >> On Thu, 27 Feb 2014 15:02:51 +0100 John Marino wrote: >>> 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. >> >> Can you explain what that problem is exactly? > > Unreferenced symbols during linking IIRC. I don't have a representative > error log handy, nor do I remember a specific port that would fail if > built with gcc4.8 and fortran 4.6, but there are some. Hmm, one thing I can think of is the combination of the -rpath flags from both versions. If they end up in the wrong order then it's possible that gcc48 tries to use the runtime libraries from gcc46 during linking.