#9356: make SAGE_ATLAS_LIB work on Solaris
-------------------------------+--------------------------------------------
Reporter: jhpalmieri | Owner: drkirkby
Type: defect | Status: closed
Priority: minor | Milestone: sage-4.5.3
Component: solaris | Resolution: fixed
Keywords: | Author: John Palmieri
Upstream: N/A | Reviewer: David Kirkby
Merged: sage-4.5.3.alpha0 | Work_issues:
-------------------------------+--------------------------------------------
Comment(by fbissey):
Replying to [comment:21 drkirkby]:
> Replying to [comment:20 drkirkby]:
> > So it seems if you want to make use of a pre-existing `liblapack.a`
from ATLAS, which means creating a symbolic link, would need to remove the
`liblapack.a` created by LAPACK first, then create the link. (Otherwise, I
think creating the link might fail, though I'm not sure.) I need to rush
out, so dont have time to test that. Dave
> On checking, just creating the link will overwrite the old file, so
there's no need to delete anything first. But if I'm not mistaken,
`liblapack.a` does get created twice - once by LAPACK and once by the
script in ATLAS. Dave
That is correct.[[BR]]
The lapack spkg produce liblapack.a, ATLAS takes it as an input, unbundles
it
and then build some optimized routines to replace the original ones.
Finally it recreates a library liblapack.a which is meant to replace the
original.
You should read the ATLAS installation guide it is very instructive. There
is even
a section about solaris on sparc.
Francois
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9356#comment:22>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac?hl=en.
