Accessing VECLIB
4.Set the LDOPTS environment variable to include:
For example:
setenv LDOPTS
Then use the −lveclib option on the compiler command line that links your program:
pgf90 [options] file ... −lveclib −mp
pgcc [options] file ... −lveclib −mp −lpgf90 −lpgf90_rpml −lpgf902 −lpgf90rtl −lpgftnrtl
NOTE | An LDOPTS specification takes precedence over using |
| compiler command line. That is, if you use the LDOPTS environment |
| variable to specify a library path, you cannot override that specification |
| with a |
|
|
Problem with +ppu compatibility and duplicated symbols
All MLIB subprograms documented in the HP MLIB User’s Guide have two entry points: one is compatible with the Fortran compiler option +noppu (no postpend underbar) and the second is compatible with the Fortran compiler option +ppu (postpend underbar). For example, the MLIB BLAS error handler XERBLA has entry points xerbla and xerbla_. Table
Table | Compiler Defaults |
|
| |
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
| +noppu | +ppu | |
|
|
|
|
|
| Itanium |
| +ppu | +ppu |
|
|
|
|
|
Different compiler defaults can cause duplicate symbol definitions at link time as the following examples illustrate.
Suppose you write your own Fortran version of the XERBLA subroutine. You compile on
14HP MLIB User’s Guide