Re: [Lapackpp-devel] Problem of setup lapack++ on Scientific Linux 64bit

[Christian S. <chr...@cs...>]

Am Dienstag, 27. März 2012, 13:22:50 schrieb Guilhem BLES:
> Hello,
> 
> First, thank you very much for your Lapackpp code lines. They are very
> helpful for me.
> 
> But, at the present moment, I do not succeed to setup Lapackpp on
> Scientific Linux 64 bit.
> 
> [root@xxx lapackpp-2.5.4]# make check
> Making check in include
> make[1]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/include'
> make  check-am
> make[2]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/include'
> make[2]: Nothing to be done for `check-am'.
> make[2]: Leaving directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/include'
> make[1]: Leaving directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/include'
> Making check in blaspp
> make[1]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/blaspp'
> Making check in src
> make[2]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/blaspp/src'
> make[2]: Nothing to be done for `check'.
> make[2]: Leaving directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/blaspp/src'
> Making check in testing
> make[2]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/blaspp/testing'
> make  tblasd++ check_blas1pp \
> 	  blas++_test
> make[3]: Entering directory
> `/root/Documents/outilsInfo/lapackpp/lapackpp-2.5.4/blaspp/testing'
> /bin/sh ../../libtool --tag=CXX   --mode=link g++  -g -O2
> -Wall  ../../src/liblapackpp.la  -o tblasd++ tblasd++.o
> libtool: link: g++ -g -O2 -Wall -o .libs/tblasd++ tblasd
> ++.o  ../../src/.libs/liblapackpp.so
> ../../src/.libs/liblapackpp.so: undefined reference to `zgesdd_'

Your build process is missing the linker flags to link against the "lapack" 
(without "pp") and "blas" libraries, such as "-llapack -lblas". However, 
./configure should have found those. Didn't you already get an error when 
running "make"? If not, you're probably fine and can ignore this error.

Regards,

Christian