On 08/02/2010 03:33 PM, John H Palmieri wrote: >> I'm trying to reproduce this, but on skynet's taurus I don't even get a >> liblapack.so, but only liblapack.a. (The build isn't done yet, but the lapack >> package is done.) >> >> Am I missing something? I checked, but none of my recent sage builds on >> multiple machines seem to have liblapack.so. > > I bet at the end of the ATLAS log they all say > > ld: cannot find -lgfortran > > when trying to build the shared libraries. This happens for me on > sage.math, for example. It doesn't seem to hurt anything, as far as I > can tell, but I could be wrong about this...
On 08/02/2010 05:20 PM, Willem Jan Palenstijn wrote: > I haven't looked into what makes liblapack.so appear/disappear yet. Does > anyone > familiar with atlas/lapack know this offhand? I'm not very familiar with these packages, but if liblapack.so disappears or does not appear because ATLAS can't find libgfortran, the steps in http://trac.sagemath.org/sage_trac/ticket/9356#comment:7 might make it (re)appear. Should we do $ cd SAGE_LOCAL/lib $ ln -s libgfortran.so.2 libgfortran.so or a generalization, in the Fortran package? -- 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
