Re: [Lapackpp-devel] undefined reference problem

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

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

Hi,

Andrew Oh schrieb:
> 
> I added -lblas -lg2c and -llapack to the linker flags and my errors
> have been reduced to this:
> 
> /usr/local/apps/intel/compiler8/lib/libimf.so.6: warning: log2l is not
> implemented and will always fail
> /usr/local/apps/intel/compiler8/lib/libimf.so.6: warning: exp2l is not
> implemented and will always fail
^^^^ those can be ignored

> /usr/lib/liblapack.so: undefined reference to `f_cpstr'
> /usr/lib/libblas.so: undefined reference to `f_iob'
> /usr/lib/liblapack.so: undefined reference to `f_cpystr'
> /usr/lib/liblapack.so: undefined reference to `f_concat'
> /usr/lib/libblas.so: undefined reference to `f_stop'
> 
> Is there anyway I can find out which linker flags I need to add so
> that the undefined references go away? I'm really sorry but I don't
> know how to use automake, autoconfig or libtool... I guess I should
> start reading up on tutorials =[.

Sigh... obviously you also need to link against some fortran library,
but I can't tell the name as this depends on your system. Hm... have you
been able to compile the lapackpp tarball completely? Can you also run
"make check" in the tarball? The command "make check" will compile
several executables, e. g. in the testing/ directory. During "make
check", you can look at the commands and see which additional linker
flags are being used. Or in the file ./config.status, look for the line
that contains @FLIBS@ and this should tell you the library flags as well.

Christian

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

iQCVAwUBRHQYO2XAi+BfhivFAQJ4eAP/cfzH/F91husnqAhZFxqXiy90Avyp/379
8nGKuGcN6sOZNmB+LULb9Pk3jiRCMg7UV5NsHzYMLaUPVCbUjeke+nduflwS6S+6
24RpVvS39go41uL37H9XCwCdCeDm8JB6OpQUI7gXYxFmo+OmuP+0GGO7Z5aO9CCA
YSDY0eKQq4Q=
=0Fo/
-----END PGP SIGNATURE-----