very similar to Lapack linking issue posted 11-10-09

Building lapack locally on RedHat, end goal is a static build of lapack++ that can be deployed as a 3rd party lib in a directory other than /usr/lib

make options for lapack/blas:
FORTRAN = gfortran -fimplicit-none -g
OPTS = -fpic -static
DRVOPTS = $(OPTS)
NOOPT =
LOADER = gfortran -g
LOADOPTS =
#


configure options for lapack++:
./configure --prefix=/home/dsmith/lapackpp-2.5.3-install-debug --enable-debug --enable-static=yes --enable-shared=no --with-pic --with-lapack=/home/dsmith/lapack-3.2.1/liblapack.a --with-blas=/home/dsmith/lapack-3.2.1/libblas.a

Note: had problem with config script, --enable-static did NOT put -static on the compile line, I had to force it by modifying CXX_FLAGS


log file for lapack++ build enclosed (I hope)
highlights:

*** Warning: Linking the shared library liblapackpp.la against the
*** static library /home/dsmith/lapack-3.2.1/liblapack.a is not portable!

*** Warning: Linking the shared library liblapackpp.la against the
*** static library /home/dsmith/lapack-3.2.1/libblas.a is not portable!

Archives lapack & blas:
ar cru .libs/liblapackpp.a /home/dsmith/lapack-3.2.1/liblapack.a /home/dsmith/lapack-3.2.1/libblas.a dopla.o dtimmg.o eigslv.o genmd.o laprefs.o lasvd.o lautil.o linslv.o systime.o .libs/liblapackpp.lax/liblamatrixpp.a/uutgmd.o .libs/liblapackpp.lax/liblamatrixpp.a/sybfd.o .libs/liblapackpp.lax/liblamatrixpp.a/gfqrd.o .libs/liblapackpp.lax/liblamatrixpp.a/vf.o .libs/liblapackpp.lax/liblamatrixpp.a/laexcp.o .libs/liblapackpp.lax/liblamatrixpp.a/utgmd.o .libs/liblapackpp.lax/liblamatrixpp.a/symd.o .libs/liblapackpp.lax/liblamatrixpp.a/lavc.o .libs/liblapackpp.lax/liblamatrixpp.a/sytrmd.o .libs/liblapackpp.lax/liblamatrixpp.a/vd.o .libs/liblapackpp.lax/liblamatrixpp.a/trmd.o .libs/liblapackpp.lax/liblamatrixpp.a/gmi.o .libs/liblapackpp.lax/liblamatrixpp.a/lavli.o .libs/liblapackpp.lax/liblamatrixpp.a/spdtrmd.o .libs/liblapackpp.lax/liblamatrixpp.a/gmli.o .libs/liblapackpp.lax/liblamatrixpp.a/lavd.o .libs/liblapackpp.lax/liblamatrixpp.a/vc.o .libs/liblapackpp.lax/liblamatrixpp.a/sybmd.o .libs/liblapackpp.lax/liblamatrixpp.a/gmtmpl.o .libs/liblapackpp.lax/liblamatrixpp.a/vli.o .libs/liblapackpp.lax/liblamatrixpp.a/gmconv.o .libs/liblapackpp.lax/liblamatrixpp.a/ltgmd.o .libs/liblapackpp.lax/liblamatrixpp.a/lavi.o .libs/liblapackpp.lax/liblamatrixpp.a/vi.o .libs/liblapackpp.lax/liblamatrixpp.a/spdbmd.o .libs/liblapackpp.lax/liblamatrixpp.a/laindex.o .libs/liblapackpp.lax/liblamatrixpp.a/gfqrc.o .libs/liblapackpp.lax/liblamatrixpp.a/bmd.o .libs/liblapackpp.lax/liblamatrixpp.a/spdmd.o .libs/liblapackpp.lax/liblamatrixpp.a/gmc.o .libs/liblapackpp.lax/liblamatrixpp.a/gmf.o .libs/liblapackpp.lax/liblamatrixpp.a/gmd.o .libs/liblapackpp.lax/liblamatrixpp.a/ultgmd.o .libs/liblapackpp.lax/libblaspp.a/blas2pp.o .libs/liblapackpp.lax/libblaspp.a/blas3pp.o .libs/liblapackpp.lax/libblaspp.a/blaspp.o .libs/liblapackpp.lax/libblaspp.a/blas1pp.o /home/dsmith/lapack-3.2.1/liblapack.a /home/dsmith/lapack-3.2.1/libblas.a
ranlib .libs/liblapackpp.a


Resulting lapackpp builds fine with my application but when I run the application I get:

symbol lookup error: ore-3.1.0-PIL-SNAPSHOT.so: undefined symbol: dscal_

symbol is defined in blas, why is it undefined in my app?

Attached Files

make-lapackpp.txt (31.2 KB, 14 views)

Not that I know much about lapackpp, just my considerations ..

cd lapackpp-2.5.3/ ( Example )

./configure --enable-static
.. is what it takes.

( If you want a debug version, better make it later / seperately
Can't imagine "debug" is required by your application.)

'make' will then create lapackpp.a in lapackpp-2.5.3/src/.libs/
And I get no errors with that.
Fortran 77, ATLAS, f77blas, cblas, gfortran, lapack are all checked
in automatically by " ./configure ".

But why use it ? liblapackpp.so.14.2.0 etc. is just as portable.
You can place it anywhere and start your application with a script :

#!/bin/sh
export LD_LIBRARY_PATH=./lib
exec ./<executable>

.. when you e.g. have the "lib/" folder in the same directory.

.....
.....
The best known example is Firefox with some 15 shared libraries
in the folder firefox/ . All included with the script "firefox" etc.
.....