Ok, then I'll look at sage_fortran --version.
On Nov 7, 1:00 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Nov 7, 2007 12:52 PM, Joshua Kantor <[EMAIL PROTECTED]> wrote: > > > > > Thats expected, since the fix I made was for g95 builds and it worked > > by linking in f95, which won't be around using gfortran. Should be > > easy to add a test for gfortran. > > > I was going to test whether or not $SAGE_FORTRAN was set and use an > > appropriate setup.py depending on whether or not this is true. > > > (if not assume g95, else assume gfortran) > > Watch out, since SAGE_FORTRAN need *not* be set. > All that matters is that when the fortran spkg was installed the variable > SAGE_FORTRAN was set. The important thing is the contents > of local/bin/sage_fortran/. > > -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
