Ticket #1767 (new defect)

Opened 3 years ago

Last modified 2 years ago

Add SAGE_ATLAS_LIB, SAGE_ATLAS_TARGZ flags to allow use of external atlas

Reported by: jkantor Owned by: mabshoff
Priority: major Milestone: sage-4.5.3
Component: packages Keywords:
Cc: Author(s):
Report Upstream: Reviewer(s):
Merged in: Work issues:

Description

We currently provide a SAGE_FORTRAN flag that lets external fortran be used if the user desires. Since atlas takes a long time to build, we should have an optional SAGE_ATLAS_LIB flag that would accept the path to a directory that contained libatlas, libcblas, libf77blas, and liblapack. The atlas install script will do some tests to ensure these work and will then create symlinks to them in $SAGE_LOCAL/lib

There should also be a SAGE_ATLAS_TARGZ with would be the path to a tar or tar.gz with libatlas, libcblas, libf77blas, and liblapack. These would just be copied into $SAGE_LOCAL/lib

As mentioned some checking needs to be done to ensure the atlas provided is compatible with the fortran we are using, that it actually works, as well as to check that the lapack is the full lapack (8Mb or so) and not a crippled lapack.

Change History

Changed 2 years ago by mabshoff

  • milestone changed from sage-3.2 to sage-3.1.3
Note: See TracTickets for help on using tickets.