Opened 9 years ago

Closed 7 years ago

#15371 closed defect (fixed)

No easy-to-find and easy-to-follow doc on how to skip ATLAS installation

Reported by: darij Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: documentation Keywords: install, make, readme, documentation
Cc: tscrim, vbraun Merged in:
Authors: Reviewers: Darij Grinberg
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by darij)

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. 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).

Change History (10)

comment:1 Changed 9 years ago by darij

  • Description modified (diff)

comment:2 Changed 9 years ago by chapoton

Yes, I agree strongly. It is ok to compile ATLAS once in a while, but not every time !

Here is a excerpt of a message from William on sage-devel, that maybe deserves to be written somewhere in the doc, imho:

..., a reminder about how to use the systemwide ATLAS (at least on Ubuntu 12.04 LTS). Just do this before building Sage:

         apt-get install libatlas3gf-base liblapack-dev
         cd /usr/lib/
         ln -s
         ln -s
         ln -s
         export SAGE_ATLAS_LIB="/usr/lib/"

comment:3 Changed 9 years ago by darij

By now it's also explained in (thanks, Mathieu!), but of course it should be in a more appropriate place like the installation guide.

comment:4 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:5 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:6 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:7 Changed 8 years ago by darij

  • Cc vbraun added

Here is a better question: Is there a way to tell the Sage installer to use some set of defaults for ATLAS installation rather than using ATLAS's autotuning (or "search" as they seem to call it)? This should be a matter of passing some variables. It would be extremely convenient (or rather, what we have right now is extremely not so).

comment:8 Changed 8 years ago by vbraun

Use SAGE_ATLAS_ARCH=base, its documented in the installation instuctions

comment:9 Changed 8 years ago by darij

Ah, thanks! This has worked. Feel free to close the ticket then.

comment:10 Changed 7 years ago by vbraun

  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Resolution set to fixed
  • Reviewers set to Darij Grinberg
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.