On Thu, Feb 4, 2010 at 7:41 PM, Dan Drake <[email protected]> wrote: > On Thu, 04 Feb 2010 at 05:16PM -0800, A. Jorge Garcia wrote: >> So, I tried running SAGE in a terminal from the SAGE dir that was >> created. I got a welcome message about typing notebook() to start the >> GUI and then some sort of error message about not being able to run an >> executable. It looks like it was in the bin/python dir when it >> crashed. Anyone know what went wrong here and how to fix it? > > If you post a log of what happened, we might be able to figure out what > went wrong. :) > >> One thing comes to mind. The download page (Harvard?) said something >> about apt-getting gfortran before running SAGE. Well, that's a Debian >> command, so I tried "yum install gfortran" but Fedora didn't find it. >> I was hoping that gfortran was only needed when compiling from source, >> not when running the binaries.... > > Actually, I believe that now you do need gfortran just to run the > binaries. It's not the compiler that you need, but rather the shared > library that comes along with it.
This will change for the next Sage release, by the way. If nothing else, I'm going to just copy the gfortran lib into local/lib/ when creating the binaries on the build machines. However, -bdist or sage_fortran should I think do this automatically. -- William -- You received this message because you are subscribed to the Google Groups "sage-edu" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sage-edu?hl=en.
