#15371: No easy-to-find and easy-to-follow doc on how to skip ATLAS installation
-------------------------------------------------+-------------------------
Reporter: darij | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-5.13
Component: documentation | Resolution:
Keywords: install, make, readme, | Merged in:
documentation | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Description changed by darij:
Old description:
> This is getting more annoying with git than it was with mercurial because
> sometimes checking out a different branch without merging new master into
> it might set one back to an older version of Atlas, triggering a 6-hour
> makefest. Not only would most patches hardly mind a newer version of
> Atlas, but there is also the fact that most sage development doesn't
> really depend on Atlas at all, so an older version of Atlas should be
> fine for most of us, too. I certainly wouldn't want to have to go through
> the Atlas autotune every time I download a new sage.
>
> http://sagemath.org/doc/installation/source.html#environment-variables
> only says:
> {{{
> SAGE_ATLAS_LIB - if you have an installation of ATLAS on your system and
> you want Sage to use it instead of building and installing its own
> version of ATLAS, set this variable to be the directory containing your
> ATLAS installation. It should contain the files libatlas, liblapack,
> libcblas, libptcblas, libf77blas, and libptf77blas, with extensions .a,
> .so, or .dylib. For backward compatibility, the libraries may also be in
> the subdirectory SAGE_ATLAS_LIB/lib/.
> }}}
>
> IMHO this info should be much more prominent, and could also be a bit
> more user-friendly:
> * it should say where Sage install its atlas into, and
> * it would help to explain how to change an environment variable (yes,
> this is googleable, but I remember it being nontrivial to understand).
New description:
This is getting more annoying with git than it was with mercurial because
sometimes checking out a different branch without merging new master into
it might set one back to an older version of Atlas, triggering a 6-hour
makefest. Not only would most patches hardly mind a newer version of
Atlas, but there is also the fact that most sage development doesn't
really depend on Atlas at all, so an older version of Atlas should be fine
for most of us, too. I certainly wouldn't want to have to go through the
Atlas autotune every time I download a new sage.
http://sagemath.org/doc/installation/source.html#environment-variables
only says:
{{{
SAGE_ATLAS_LIB - if you have an installation of ATLAS on your system and
you want Sage to use it instead of building and installing its own version
of ATLAS, set this variable to be the directory containing your ATLAS
installation. It should contain the files libatlas, liblapack, libcblas,
libptcblas, libf77blas, and libptf77blas, with extensions .a, .so, or
.dylib. For backward compatibility, the libraries may also be in the
subdirectory SAGE_ATLAS_LIB/lib/.
}}}
IMHO this info should be much more prominent (readme?), and could also be
a bit more user-friendly:
* it should say where Sage install its atlas into, and
* it would help to explain how to change an environment variable (yes,
this is googleable, but I remember it being nontrivial to understand).
--
--
Ticket URL: <http://trac.sagemath.org/ticket/15371#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
