On Sep 9, 5:09 am, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > There's odd bits code scattered around in Sage that do tests for g95, which is > an old Fortran 95 compiler that in any modern Linux or Unix systems. > > According to Wikipedia > > http://en.wikipedia.org/wiki/G95 > > gfortran was forked from g95 in 2003 - i.e. 7 years ago. > > I'm not sure at what point gfortran became the dominant compiler, but I've not > seen g95 used in the last few years. It might still exist on some systems, but > people tend to use gfortran instead, as that is part of gcc. > > Do others, like me, believe we just remove such bits of code as and when we > come > across them? i.e. don't make specific tests for gfortran vs g95? > > g95 binaries have already been removed from Sage > > http://trac.sagemath.org/sage_trac/ticket/7485 > > There's a few bits of code in the ATLAS package which make such tests - one of > them uses the "readelf" program to determine if a pre-installed version of > ATLAS > was built with g95. > > William said here > > http://groups.google.com/group/sage-devel/browse_thread/thread/1b6235... > > "Probably the only platforms that get g95 are older OS X."
It seems like PowerPC gets it. > Since ATLAS is not installed on OS X, it seems even less worthwhile having > such > a test in the ATLAS package. True; we use the system one. Sage also needs fortran for R, at least. Anywhere else? If someone knows how to test for the Sage fortran in a compiled build, I can quick see which one is installed on my PPC box; the command local/bin/ sage_fortran --version yielded an error (interestingly, a different error on 10.6 than on 10.4). Maybe the fortrans get axed after the build is done? - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
