The presence of this file indicates that Ed's CRAY C90/T3E patch file
was used.  Using an LAPACK 3 tar file with a date of October 31, 1999 or
later, the correct sequence of patches is

tar xvf lapack.tar               # LAPACK 3 distribution
tar xvf LAPACK3patch_120400.tar  # Ed's update of December 4, 2000

Details of the bug fixes and enhancements provided with this update
are described at

http://www.cs.utk.edu/~eanderso/lapack3.html

To install the LAPACK 3 supplement on your CRAY system,
first edit LAPACK/make.t3e or LAPACK/make.pvp to set the environment
variable LAPACKPATH to the location of your LAPACK directory.

Copy one of LAPACK/make.t3e or LAPACK/make.pvp to LAPACK/make.inc.

If you are compiling on a T3E, do this:

   cd LAPACK; make

or if you are compiling on a PVP platform, do this:

   cd LAPACK; make -f Makefile.pvp

The Makefiles create a library

   LAPACK/lib/liblapack3.a

which can be linked before the usual libsci.a to resolve references to
those subroutines new to LAPACK 3.   A set of man pages for the
LAPACK 3 supplement (cleaned up from the automatically-generated
man pages on netlib) plus pages for 32 auxiliary routines that
could be of interest to users are found in the directory

   LAPACK/man

created by the patch file.

The easiest way to add new libraries and man pages to one's search paths
on a Cray machine is by creating and loading a module.  A sample module
file for the LAPACK 3 supplement is provided in LAPACK/lapack3.

This patch file, like LAPACK itself, is free software.  It is made
available in the hope that it will be useful, but WITHOUT ANY WARRANTY,
either expressed or implied, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.
The entire risk as to the quality and performance of this software is
with you; should the library prove defective, you assume the cost of all
necessary servicing, repair, or correction.

If you have any bugs in LAPACK to report, please send them to

   lapack@cs.utk.edu

If you have comments on this patch file, please send them to me.

Ed Anderson
eanderso@cs.utk.edu
December 4, 2000