ATLAS now includes replacements for the following LAPACK routines:
   ?gesv ?getrf ?getrs
   ?posv ?potrf ?potrs
Where ? is replaced with the appropriate data type prefix, d, s, c, or z.

These routines are provided with both C and Fortran77 interfaces.  ATLAS's
LAPACK C interface, like the C interface to the BLAS, accepts both row- and
column-major arrays.  For details on the C interface API, consult the interface
code in
   ATLAS/interfaces/lapack/C/src/

The Fortran77 API is exactly that of LAPACK, and thus ATLAS's LU and Cholesky
routines can simply replace those provided by LAPACK.

************************** COMPILING A FULL LAPACK LIBRARY ********************
ATLAS does not provide a full lapack library.  However, there is a simple way
to get ATLAS to provide its faster LU and Cholesky to the LAPACK library.
ATLAS's internal routines are distinct from LAPACK's, so it is safe to compile
ATLAS's LAPACK routines directly into a netlib-style LAPACK library.  So, one
way to do this would be to first compile LAPACK from the source available on
netlib (www.netlib.org/lapack).  When this compile is finished, untar ATLAS,
run config, but before starting the install, copy the LAPACK library you
created earlier into 
   ATLAS/lib/<arch>/liblapack.a

Then, start the install, and the ATLAS interface routines will overwrite the
LAPACK routine in the lapack library, and at the end, you will have a full
LAPACK library with ATLAS's special LU and Cholesky routines.  In addition,
ATLAS provides a ATLAS-aware ILAENV routine, which should speed up many LAPACK
routines, provided you utilize ATLAS for your BLAS.

If you have already built ATLAS, you can still easily build one monolithic
LAPACK library.  First, obtain the LAPACK src from netlib and build the LAPACK
library as normal.  Then, go to your ATLAS/lib/<arch>, and issue the following
commands:
  mkdir tmp
  cd tmp
  ar x ../liblapack.a
  mv <your LAPACK lib & path> ../liblapack.a
  ar r ../liblapack.a *.o
  cd ..
  rm -rf tmp
