[GRASS-user] Unable to locate LAPACK library

GRASS GRASS user
1

I am installing GRASS 6.2 on a x86_64 machine running Fedora Core 6. I want to include LAPACK, but when I run configure I get the following message:

checking for location of LAPACK library... /usr/lib64
checking for dgesv_ in -llapack... no
configure: error: *** Unable to locate LAPACK library.

LAPACK is installed on this machine and the libraries are in /usr/lib64. I am not having this problem with BLAS.

Jim

2

James McManus wrote:

I am installing GRASS 6.2 on a x86_64 machine running Fedora Core 6. I

want to include LAPACK, but when I run configure I get the following
message:

checking for location of LAPACK library... /usr/lib64
checking for dgesv_ in -llapack... no
checking for dgesv_ in -llapack... no
configure: error: *** Unable to locate LAPACK library.

LAPACK is installed on this machine and the libraries are in
/usr/lib64. I am not having this problem with BLAS.

from REQUIREMENTS.html:

LAPACK / BLAS (libraries for numerical computing) for GMATH library
(GRASS numerical lib)
[http://www.netlib.org/lapack\] (usually available on Linux distros)
Note: the support is intended for future module implementations, no need
to use it at time!

so just leave --with-blas and --with-lapack off the ./configure string.

Hamish

3

James McManus wrote:

I am installing GRASS 6.2 on a x86_64 machine running Fedora Core 6. I
want to include LAPACK, but when I run configure I get the following
message:

checking for location of LAPACK library... /usr/lib64
checking for dgesv_ in -llapack... no
checking for dgesv_ in -llapack... no
configure: error: *** Unable to locate LAPACK library.

LAPACK is installed on this machine and the libraries are in /usr/lib64.
I am not having this problem with BLAS.

First, as Hamish mentions, the code which uses BLAS/LAPACK isn't
currently used for anything. There is no reason to enable it unless
you intend to write your own code which uses those functions.

That aside, the config.log file contains all commands which are run by
the configure script, along with their output. Any error messages
which are generated by the tests will appear near the end of that
file.

--
Glynn Clements <glynn@gclements.plus.com>