Date: Thu, 27 Feb 2014 15:24:04 +0100 From: Tijl Coosemans <tijl@FreeBSD.org> To: marino@freebsd.org Cc: svn-ports-head@freebsd.org, Baptiste Daroussin <bapt@FreeBSD.org>, Gerald Pfeifer <gerald@pfeifer.com>, svn-ports-all@freebsd.org, freebsd.contact@marino.st, ports-committers@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> <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> <530F458B.1050209@marino.st> <20140227150915.15e44b44@kalimero.tijl.coosemans.org> <530F4818.2040300@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140227152404.50bdaa2b>