Install prob on debian Linux

[richardq]

Hi,
I need to install Lapack to use a program, as I am new in doing this obviously I have problems.

1) can I use gfortran (fortran 95) to compile Lapack instead of g77. I known that normally we can compile fortran 77 with fortran 95 but I want to be sur.

2)What the difference between lapack.deb (package lapack for debian) and the lapack I compile my self? My lib lapack is better, doesnot it?

3) I modified make.inc to adapt to my architecture (pentium 4 2.8Ghz) and to compile Lapack with the same option than BLAS lib (I know itisbetter to use optimized one, I am trying to compile ATLAS too):
FORTRAN : g77
OPTS : -O3 - fomit-frame-pointer -funroll-loops -malign-double -march=i386
NOOPTS :
LOADER: g77
LOADOPTS:

ARCH:ar
ARCHFLAGS : cr
RANLIB=ranlib
and I change the directory of BLAS to choose my BLAS Lib.

Whem the copile finished everything seems ok all the test seems ok.
BUT I would like to make now the test myself and the commade "make lapcke_testing" doesnot works.
I read on the manual that I could execute directly for instance testlsame but it doesnot exist.
I do not understand now how I can test my lapack lib to be sure that everything is ok.

Thank for help,

Richard

[Julie]

Richard

1) can I use gfortran (fortran 95) to compile Lapack instead of g77. I known that normally we can compile fortran 77 with fortran 95 but I want to be sur.

Yes, you can. You should have not problem compiling with gfortran

2)What the difference between lapack.deb (package lapack for debian) and the lapack I compile my self? My lib lapack is better, doesnot it?

Debian worked on the 3.0 version of Lapack to correct some bugs and optimized some part of the code. Now that the Lapack 3.1.0 from netlib is released, I will advice you to use the 3.1.0 from Netlib until Debian releases its "tuned" Lapack 3.1.0.

3) I modified make.inc to adapt to my architecture (pentium 4 2.8Ghz) and to compile Lapack with the same option than BLAS lib (I know itisbetter to use optimized one, I am trying to compile ATLAS too):

Your options seems fine, you can use just -O3, that should be enough
make lapack_testing is working, it is just that nothing has to be done because all the testings are done. It should answer something like: make[1]: Nothing to be done for `all'.

If you want to have a look at the results of the testings, go in the TESTING directory and open the .out files.
If you want to rerun the testings, go to the TESTING directory and remove the .out files then run make in the TESTING directory or make lapack_testing from the LAPACK directory.

Hope it helps
Julie

[richardq]

Julie,

Thank for your quick help.
I am going to recompile Lapack with gfortran.

One more question:
Where I can find information about the option NOOPTS, LOADOPTS, ARCH, ARCHFLAGS,
and RANLIB because I do not know what these value are good (default values ; I did not change them from example file). I would like to know more about it.
Thank

Richard

[Julie]

Richard, here is the link on the LAPACK installation guide for Lapack-3.0:
http://www.netlib.org/lapack/lawnspdf/lawn81.pdf
For the description of the options, here is what is in the make.inc says. I don't know what to add more.

Modify the FORTRAN and OPTS definitions to refer to the compiler and desired compiler options for your machine.
NOOPT refers to the compiler options desired when NO OPTIMIZATION is selected.
Define LOADER and LOADOPTS to refer to the loader (cad linker) and desired load options for your machine.

The archiver and the flag(s) to use when building archive (library)
If you system has no ranlib, set RANLIB = echo.ARCH = ar
ARCHFLAGS= cru
RANLIB = ranlib

These are the correct setting for a Linux system

Julie