On Wed, Feb 22, 2017 at 5:13 PM, Simon King <simon.k...@uni-jena.de> wrote: > PS: > > On 2017-02-22, Simon King <simon.k...@uni-jena.de> wrote: >> Aha. Although I did "apt-get install gcc-fortran", gfortran is not there. > > And the reason is that apparently I didn't read the development manual > with enough care. It advises to install gfortran (resp gcc-gfortran on > redhat), and probably I tried gcc-fortran instead (which has failed, so, > I really wonder why I didn't notice). > > Anyway, I now have SageMath on yet another laptop, and am looking > forward to SageDays!
I've been bitten by the gfortran thing a couple times before. IIRC the main reason Sage started building its own gcc in the first place was to get around bugs on OSX. But it stuck around and has since been used to add its own version of gcc in cases where the user's gcc was too old as well (due to bugs in that older gcc). IMHO building Sage should not just forge ahead with building its own gcc without asking. I think it's bad enough that it's a package at all, but as long as it is it should be strictly optional, and if the version check fails for gcc/gfortran the build should just refuse to continue (i.e. `./configure` would exit with an error) providing information on what version checks were performed, what failed, and mention that if desired sage can be built --with-gcc or something in which case it will add gcc to the build. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
