Build Instructions: ------------------ 1. Change directory to \LAPACK 3.1.1 for Windows. 2. Execute "set_environment.bat" script from command prompt with the following arguments: a. Machine architecture to be used: This parameter is mandatory and currently 32-bit and 64-bit machine architectures are supported. b. Compiler to be used: This parameter is mandatory and currently Intel and PGI compilers are supported. c. BLAS library to be used: This parameter is optional and by default it uses BLAS library shipped with the package. Here is the usage of the set_environment.bat script: set_environment.bat [BLAS Library Path] Type /? to get the help/usage message on command prompt. 3. Please execute "nmake cleanall" command if you have built the package earlier in different environment i.e. by using different compiler and/or for different machine architecture. 4. Type 'nmake /NOLOGO all' on command prompt to build and test LAPACK package. Notes: - It is recommended to use new terminal to setup the development environment for buidling LAPACK for different machine architecture and/or using different compiler. - If you have not installed PGI compiler at default location, modify set_environment.bat script to specify approprite path of pgi_dos.bat. - LAPAACK Fortran Interface: a. Using 64-bit PGI compiler: The FORTRAN interface names are similar to AMD's 64-bit ACML library and they can be called directly. b. Using 32-bit PGI compiler: The FORTRAN interface names are similar to AMD's 32-bit ACML library and they can be invoked by providing -Munix flag to the pgf77 compiler. c. Using 64-bit Intel compiler: The FORTRAN interface names are similar to AMD's ACML and Intel's MKL 64-bit library and they can be called directly. d. Using 32-bit Intel compiler: The FORTRAN interface names are similar to AMD's ACML and Intel's MKL 32-bit library and they can be called directly.