The ticket https://trac.sagemath.org/ticket/27016 has been sitting for several weeks in needs_review status, which is not all that unusual and normally I wouldn't care. However, people trying to build Sage for the first time on Linux keep getting bitten by this irritating gfortran issue.
They can avoid it by ensuring that a gfortran is *correctly* installed on their system, though personally I don't care if they wind up (unnecessarily) building the gfortran SPKG either so long as it works. If the diff looks daunting, it really isn't. As I have explained multiple times on the ticket, it is mostly just refactoring of existing scripts: The spkg-install scripts for the gcc and gfortran packages were nearly identical, so I just merged them into one that could be reused. I then added a patch, which comes from Debian, to prevent gcc from installing libraries into some lib64/ directory, which we don't want in Sage. That's all it does, and I have tested it on multiple platforms myself including macOS. Thanks, E -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
