Re: gcc and libtool-fortran

[Greg Troxel <gdt%lexort.com@localhost>]

Chuck Cranor <chuck%ece.cmu.edu@localhost> writes:

> On Thu, Feb 20, 2025 at 08:05:15PM -0500, Greg Troxel wrote:
>> We have multiple styles in pkgsrc
>> 
>>   A) configure which version is wanted, and use it
>> 
>>   B) among acceptable, look for what's installed, and act like it has been configured.
>> 
>> I have come to prefer, at least mildly, style A, as being more predictable.
>
>
> my concern with style A as it is currently deployed is that the
> configuration settings are down in pkgsrc/mk/compilers/gfortran.mk
> where it is not that easy to find.  e.g. compared to the C/C++
> compiler settings which I think come from the bootstrap script's
> "--compiler" flag and are placed in $prefix/etc/mk.conf...

There are two parts to compiler.  One is the configured compiler for
bootstrap and the other is the compiler used for something, which might
be forced to be a newer version of gcc, built by pkgsrc.

It may well be that the desired gfortran version should be part of the
bootstrap args and set.  I didn't mean to claim that things were
optimal, just that "it didn't just decide to use what I built" has pros
and cons.

>>   Given that gcc12 is troubled on some macOS versions, maybe we should
>>   just be switching macOS fortran to 14.  I suspect that fortran is
>>   straightforward and that gcc12 and gcc14 behave pretty much the same
>>   if they build (but tell me if that's wrong).  But I don't know if
>>   gcc14 is going to fail where 12 succeeds, on older macOS versions, or
>>   x86-64, etc.
>
> yeah, i don't know either, but it's clear the gcc12 setting is
> starting to bit rot...

It would be reasonable to either propose and bump to 14 or just bump
(for mac), assuming among us we can see if 14 builds.

I can kick off a build of gcc14. on 13/Ventura.  We might need to have a
os version conditional.

It would be great if somebody could make gcc12 work but that may be too
hard.