Re: Moving to gcc7

> On Oct 10, 2017, at 09:17, Jack Howarth <[email protected]> wrote:
> 
> On Mon, Oct 9, 2017 at 12:07 PM, Alexander Hansen
> <[email protected] <mailto:[email protected]>> wrote:
>> 
>>> On Oct 9, 2017, at 08:32, Remko Scharroo <[email protected]> wrote:
>>> 
>>> Dear Fink Developers,
>>> 
>>> I see that some packages are being changed from linking against gcc6 to gcc7. For example: floppy, flow, ftidy, snoopy, to-f90.
>>> I have a few Fortran related packages that I maintain.
>>> Is the general consensus that Fink now goes with gcc7 as source for gfortran?
>>> 
>>> Regards,
>>> Remko
>>> 
>>> 
>> 
>> There’s no policy in that regard.  When packages get updated, it’s pretty common to update them to use the latest versions of their dependencies at that time.
>> 
> 
> There is at least one exception to that rule.The r-baseXY packages
> embed a specific versioned gfortran release (such as gfortran-fsf-5)
> into its internal build commands for compiling cran modules. In that
> case, it would be best practices to switch the r-baseXY packages and
> all of the cran modules with gcc5-shlibs dependencies over to the same
> gcc release in one go.
>            Jack
> 

This reminds me of another exception along similar lines.  Some octave modules actually depend on gcc5, and if someone were to update Octave to build with a newer gcc* those would need to be updated at the same time.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel