HP MLIB User's Guide Vol. 2 7th Ed.

638 HP MLIB User’s Guide
Accessing LAPACK
For example, the command lines in Method 2 for XC6000 could be written:
efc [options] file...−Wl,–Bstatic,−L/opt/mlib/lib/intel_7.1/hpmpi_2.1/
lib/64 −llapack −openmp
icc
[options] file ...−Wl,–Bstatic,−L/opt/mlib/lib/intel_7.1/hpmpi_2.1/
lib/64 −llapack −openmp
4. Set the LDOPTS environment variable to include:
–Bstatic,−L/opt/mlib/lib/intel_7.1/hpmpi_2.1/lib/64
For example:
setenv LDOPTS “–Bstatic,–L/opt/mlib/lib/intel_7.1/hpmpi_2.1/
lib/64”
Then use the −llapack option on the compiler command line that links your
program:
efc [options] file ... −llapack −openmp
icc
[options] file ... −llapack −openmp
NOTE An LDOPTS specification takes precedence over using -Wl on the
compiler command line. That is, if you use the LDOPTS environment
variable to specify a library path, you cannot override that specification
with a -Wl option on your compiler command line.
For XC4000 Systems with the PGI V5.1 Compiler
1. Use one of the following compile line commands to link LAPACK:
pgf90 [options] file ... –L/opt/mlib/pgi_5.1/hpmpi_2.1/lib/64 −llapack −mp
pgcc
[options] file ... –L/opt/mlib/pgi_5.1/hpmpi_2.1/lib/64 −llapack −mp
−lpgf90 −lpgf90_rpml −lpgf902 −lpgf90rtl −lpgftnrtl
2. Specify the entire path of the library file on the compiler command line that
links your program. For example, to link your program with LAPACK for
use with 64-bit addressing on an XC4000 system with the PGI V5.1
compiler, use one of the following:
pgf90 [options] file ... /opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64/liblapack.a −mp
pgcc
[options] file ... /opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64/liblapack.a −mp
−lpgf90 −lpgf90_rpml −lpgf902 −lpgf90rtl −lpgftnrtl
Replace liblapack.a with liblapack.so on your compiler command line if you
want to link the shared library on an XC4000 system.
3. Use the −llapack option on the compiler command line that links your
program, preceded by: