William Stein wrote: >> From a practical point of view, is anyone actually going to try to get Sage >> working with gcc 3.4.x? > > Based on my experience with the Sage project, I think the probability > somebody is going to serious try to get Sage to build with GCC 3.4.x, > and that they will call it "porting" is... 100%.
I'm not sure how to interpret what you are saying there, and hence what you view as the best approach. Personally I think exiting, but allowing 'SAGE_PERMIT_OLD_GCC' override this would be best. I doubt anyone will actually try to fix bits in Sage to build with an old gcc, but I would not want to stop them if they wanted to. >> On a related point, on Solaris one *must* install a GCC with Fortran >> support, as >> the sage_fortran binary in Sage has no compiler for Solaris. In which case, >> perhaps we should consider exiting on Solaris, AIX, HP-UX, IRIX and Tru64 >> unless >> there is a Fortran compiler. (i.e. if gcc is used, we check it supports >> Fortran). I'm not sure what binaries that does contain (Linux and OS X >> perhaps??). > > I think in sage-4.3 on, we should *only* include fortran compilers for > OS X, and *nothing* else. In which case, I guess we should check there is a working Fortran compiler on any platform except OS X. If not, we should exit. Dave -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
