Accessing VECLIB

–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 −lveclib option on the compiler command line that links your program:

 

efc [options] file ...

−lveclib −openmp

 

icc [options] file ...

−lveclib −openmp

 

 

 

NOTE

 

An LDOPTS specification takes precedence over using -Wlon 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 -Wloption 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 VECLIB: pgf90 [options] file ... –L/opt/mlib/pgi_5.1/hpmpi_2.1/lib/64−lveclib −mp

pgcc [options] file ... –L/opt/mlib/pgi_5.1/hpmpi_2.1/lib/64 −lveclib −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 VECLIB 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/libveclib.a −mp

pgcc [options] file ... /opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64/libveclib.a −mp −lpgf90 −lpgf90_rpml −lpgf902 −lpgf90rtl −lpgftnrtl

Replace libveclib.a with libveclib.so on your compiler command line if you want to link the shared library on an XC4000 system.

3.Use the −lveclib option on the compiler command line that links your program, preceded by:

−Wl,–Bstatic,−L/opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64

For example, the command lines in Method 2 for XC4000 could be written:

pgf90 [options] file...−Wl,–Bstatic,−L/opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64 −lveclib −mp

pgcc [options] file ...−Wl,–Bstatic,−L/opt/mlib/lib/pgi_5.1/hpmpi_2.1/lib/64 −lveclib −mp −lpgf90 −lpgf90_rpml −lpgf902 −lpgf90rtl −lpgftnrtl

Chapter 1 Introduction to VECLIB 13