Re: [Lapackpp-devel] lapack++ install

[Christian S. <sti...@tu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Andrew Oh schrieb:
> Right now I'm trying to install lapack++ for SuSE 10.x, i586. I
> already installed blas and lapack using the rpms that came with the
> SuSE dvd and have a g77 compiler installed as well.
> 
> I think that I just have to manually tell the compile program where
> the blas and lapack libraries are located. Everything is in /usr/lib.
> I'm not sure what would be the correct command. Here are some examples
> I have tried.

Can you post the last 20 lines of ./configure output, so that we know
what is actually going wrong? I have a suse10.0 system at hand (which
version do you have exactly?), and there I can compile lapackpp without
any further ./configure arguments.

The package with the fortran compiler is called "gcc-fortran-4.0.2" on
that suse10.0 system. There is an issue with gcc-3.x packages vs.
gcc-4.x packages -- both cannot be mixed. So if your standard gcc is
4.x, then you need to make sure you also installed the gcc-4.x fortran
compiler, which on suse is probably called gcc-fortran and *not* g77.

> ./configure --prefix=/whatever --with-blas=blas.a --with-lapack=lapack.a
> 
> ./configure --prefix=/whatever --with-blas=blas.so --with-lapack=lapack.so
> 
> ./configure --prefix=/whatever --with-blas=/usr/lib/blas.a
> --with-lapack=/usr/lib/lapack.a
> 
> ./configure --prefix=/whatever --with-blas=blas.a
> --with-lapack=lapack.a --with-lapack-libs=/usr/lib
> 
> and other variations. none of these have worked. Also, the LDFLAGS (
> i.e.  -L/usr/lib ) is not recognized as an argument. So how can I get
> ./configure to recognize blas and lapack? Thanks again.

If the blas/lapack library has a different name, say blasfoo, then
- --with-blas=blasfoo would work and add the "-lblasfoo" arguments to the
linker commands. On the other hand, if the argument to --with-blas=
starts with a minus, then the full string will directly be passed into
the linker commands. THis means --with-blas="-L/usr/foolibs -lblasfoo"
would add "-L/usr/foolibs -lblasfoo" into the linker commands. Same with
lapack.

But in your case this is probably not the problem. I guess you're rather
seeing problems with the fortran compiler, but please post the output of
configure and maybe the relevant parts of config.log.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRFhf9GXAi+BfhivFAQLPEQP/Xn5zZHJXFEhH2YzNhQTlvmMfAzCiVLJs
sJ4COkX7kF+59YbwnmS+R6FP10/FtmLLLZ5kWNm/7ra2E7EI0Npsddju5L+yJGXW
5vawqBeCWXT9iiKfY4KxRlIBLZI8gGwhJn/qPnndDcXWK5JxWI9kuYV64kj6mtwh
G6RKk4ScR0U=
=g36n
-----END PGP SIGNATURE-----