On Tue, Aug 23, 2016 at 5:33 PM, Christian Weisgerber
wrote:
> Christian Weisgerber:
>
>> > > Then shouldn't this layer cover the gcc/4.9 and g77 cases?
>> > > If ports that require a newer fortran compiler can't even use that
>> > > abstraction, then it's useless.
>> >
>> >
On Mon, Aug 22, 2016 at 05:03:16PM +0200, David Coppa wrote:
> On Mon, 22 Aug 2016, Christian Weisgerber wrote:
>
> > On 2016-08-22, Marc Espie wrote:
> >
> > >> - to use the newer fortran (egfortran) from gcc 4.9, it's better
> > >> to use the MODGCC4_* macros (see math/R)
>
On Mon, 22 Aug 2016, David Coppa wrote:
> On Mon, 22 Aug 2016, Christian Weisgerber wrote:
>
> > On 2016-08-22, Marc Espie wrote:
> >
> > >> - to use the newer fortran (egfortran) from gcc 4.9, it's better
> > >> to use the MODGCC4_* macros (see math/R)
> > >>
> > >> After
On Mon, 22 Aug 2016, Christian Weisgerber wrote:
> On 2016-08-22, Marc Espie wrote:
>
> >> - to use the newer fortran (egfortran) from gcc 4.9, it's better
> >> to use the MODGCC4_* macros (see math/R)
> >>
> >> After all this reasoning,
On 2016-08-22, Marc Espie wrote:
>> - to use the newer fortran (egfortran) from gcc 4.9, it's better
>> to use the MODGCC4_* macros (see math/R)
>>
>> After all this reasoning, ports/infrastructure/mk/fortran.port.mk
>> has become a simple four-liner:
>>
>> So, why not just
On Mon, 22 Aug 2016, Marc Espie wrote:
> Nope, you never know when it might come back.
> I'm for still having the extra layer in that case.
No problem.
So here's the alternative diff:
Index: fortran.port.mk
===
RCS file:
On Mon, Aug 22, 2016 at 11:01:53AM +0200, David Coppa wrote:
>
> Hi,
>
> Given that:
>
> - lang/g77-old devel/libf2c-old are long dead
>
> - lang/gfortran will go to the Attic in the same way
>
> - to use the newer fortran (egfortran) from gcc 4.9, it's better
> to use the MODGCC4_* macros
Hi,
Given that:
- lang/g77-old devel/libf2c-old are long dead
- lang/gfortran will go to the Attic in the same way
- to use the newer fortran (egfortran) from gcc 4.9, it's better
to use the MODGCC4_* macros (see math/R)
After all this reasoning, ports/infrastructure/mk/fortran.port.mk
has