hpc gfortran

[Sean Farley]

Lawrence Velázquez writes:

> On Mar 25, 2013, at 3:58 PM, Sean Farley <sean at macports.org> wrote:
>
>> Joshua Root writes:
>> 
>>> On 2013-3-26 05:44 , Sean Farley wrote:
>>>> 
>>>> I would say it is worth it because currently there is no sane way to
>>>> specify a sole fortran compiler.
>>> 
>>> What do you mean by this exactly? What is the problem with e.g.
>>> 
>>> depends_build port:gcc47
>>> configure.fc ${prefix}/bin/gfortran-mp-4.7
>>> ?
>> 
>> Then what does configure.fc get set to in the +clang variant?
>
> Technically, you could do something like this.
>
>     depends_build       port:clang-3.2 \
>                         port:gcc47
>     configure.compiler  macports-clang-3.2
>     configure.fc        [portconfigure::configure_get_compiler fc macports-gcc-4.7]

That's right. This is (practically) what ports already do but your code
is much cleaner and nicer. Though, this solution still lacks an
equivalent of:

$ sudo port select fortran gfortranXY

> But I think that dependency on full-bore GCC is what bothers you.

Actually, not as much as an 'incorrect' dependency graph. The gfortran
subport would solve both, I think.