#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):
Not sure I like the smell of being cc to a can of worms first thing on
Saturday morning.
I will need to see what the ATLAS spkg builds and install exactly. Glad
that I
have definitely dealt with that on sage-on-gentoo.
To summarize BLAS and LAPACK are technically a set of well defined linear
algbra operations. There are standards on what they should be named and
what they should do.
Which is why you can have a variety of implementation.
You may find some info here useful:
[http://www.gentoo.org/proj/en/science/blas-lapack.xml]
Anyway, BLAS is the reference implementation it produces libf77blas.{a,so}
but
no cblas. lapack is lapack reference, it builds liblapack.{a,so} you can
build
lapack-reference on top of most BLAS implementations.
ATLAS builds a tuned version of BLAS routines it build libcblas.{a,so} as
well as
low level libraries in libatlas.{a,so}.
A wrapper for fortran77 code is then produced [another copy of
libf77blas.{a,so}].
It is not compulsory to build these. There is a standard way documented
upstream in ATLAS to include lapack-reference code in ATLAS and produce a
set of lapack libraries. A lapack library produced by ATLAS in this way
will also ship a clapack.h header - there is no standards for clapack.
I mentioned clapack because scipy looks for this. It will produce a
different
set of low levels routines depending on whether it can find it or not. I
think.
Your scipy will be slightly different depending on it. I could show the
exact
differences if absolutely needed.
If your lapack libraries has been compiled with atlas it will requires
libatlas.
ATLAS shouldn't depend on lapack. If anything it should be the other way
around.
Unless we use the dependency to get access to the source code.
I'll inspect the ATLAS spkg to see what is exactly done there.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9356#comment:17>
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.
