On Wed, Feb 17, 2010 at 11:47 AM, Ondrej Certik <[email protected]> wrote: > On Wed, Feb 17, 2010 at 11:34 AM, Ethan Coon <[email protected]> wrote: >> Ok, so I uploaded an spkg, but it's not exactly right yet. A few issues: >> >> 1. my stupidity -- the flag should actually be --FLIBS="f95" , not >> --FFLAGS="-lf95*". This isn't necessary to get a working PETSc and >> petsc4py, but it is both more correct and necessary when you start >> adding on additional libraries to PETSc (like Hypre/ML/Trilinos/etc) >> that also need linked. I'll fix this and upload a new package in the >> next few hours (still testing the full installation with all bells and >> whistles). > > Thanks! > >> >> 2. I'm not exactly sure what fortran compilers are used with Sage. In >> my default installation, it used g95, so the necessary library to >> include is libf95.a. Is there ever a case where this should actually >> be libgfortran.so? Or are there different names for pgi fortran >> libraries? I'm not that familiar with this whole multi-platform game, >> so I'm leaving it at libf95 for now, but holler if we need to work out >> some name-mangling with which_fortran to get the right library linked. > > Yes, I am not so familiar with this either. CCing sage-devel, maybe > someone could help us over there. > > Ondrej >
We ship g95 on OS X. On all other platforms we require that gfortran be installed, or that the user set the SAGE_FORTRAN environment variable. When I build binaries, I copy libgfortran.so into local/lib/. William -- 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
