science ports upgrade to gcc47

[Srinath Vadlamani]

I think using the entire gcc-suite for the compilation will help those that
use macports as a base/toolchain for local development of software that may
be deployed on other platforms.  The mixing of compilers (clang+gcc4X
fortran) will make for challenging debugging..
<>Srinath
=================================
Srinath Vadlamani
=================================


On Mon, Aug 6, 2012 at 12:18 PM, Eric A. Borisch <eborisch at macports.org>wrote:

> On Mon, Aug 6, 2012 at 11:44 AM, Sean Farley
> <sean.michael.farley at gmail.com> wrote:
> >> arpack
> >> cfitsio
> >> dotwrp
> >> fftw-3
> >> fftw-3-long
> >> fftw-3-single
> >> qrupdate
> >> wgrib2
> >
> > These are all bogus because they only have a +gcc4X for the fortran
> > compiler. The C/C++ code is still compiled with clang (or whichever is
> > the default C compiler from MacPorts).
>
> I'm curious where the consensus lies with respect to this difference.
>
> I've taken the approach (in the ports I manage with said variants)
> that +gccNN means "please ignore all other compilers and use this
> (family) for everything." Other ports, like those above and some
> others, use the +gccNN flag just to enable fortran bindings, an choose
> to only use the gccNN port's gfortran as described by Sean above.
>
> Any thoughts / best practices for this? I'm in favor of the all-in
> approach when a compiler variant is provided, but perhaps there are
> counter-examples where this is broken?
>
> Thanks,
>  Eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120806/f8caa487/attachment.html>