On Wed, 18 Nov 2009 10:05:55 Jason Grout wrote: > > I haven't modified anything: > > /dev/shm/sage-4.2.1/local/bin% cat sage_fortran > > #!/bin/sh > > sage_fortran.bin -fPIC $...@% > > > > Of course, sage_fortran.bin is a binary executable. > > Checking the SAGE_FORTRAN bit: > > /dev/shm/sage-4.2.1% ./sage -sh > > > Starting subshell with Sage environment variables set. > Be sure to exit when you are done and do not do anything > with other copies of Sage! > > Bypassing shell configuration files ... > > /dev/shm/sage-4.2.1\nsage subshell$ env | grep SAGE_FORTRAN > SAGE_FORTRAN=/usr/bin/gfortran > > So it appears that SAGE_FORTRAN is set, at least from the sage -sh > environment. > Well then it hasn't been taken into account by the fortran spkg when it got installed. My sage_fortran read: #!/bin/sh
gfortran -fPIC This is still sage-4.2 - I haven't updated to 4.2.1 yet may be it is a bug. There is also no traces of sage_fortran.bin in my install. So I'd say it didn't work as expected. Francois -- 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
