HP XC System 3.x Software - Manual (Page 32)

(perhaps with incompatible shared objects) installed, it is probably wise to set MPI_CC (and others) explicitly
to the commands made available by the compiler's modulefile.
The contents of the modulefiles in the modulefiles_hptc RPM use the vendor-intended location of the
installed software. In many cases, this is under the /opt directory, but in a few cases (for example, the
PGI compilers and the TotalView debugger) this is under the /usr directory.
If you install a software package other than in the intended place, you must create or edit an appropriate
modulefile under the /opt/modules/modulefiles directory.
For the packages that install by default into the /usr directory (currently the PGI compilers and TotalView),
their corresponding modulefiles will try their vendor-intended location under the /usr directory. If they
do not find that directory, the packages will also search under the /opt directory. Therefore, you do not
need to make any changes to the modulefiles if you want to install third-party software consistently as
the vendor intended or consistently under the /opt directory,
If the package is the stable product intended to be used by the site, editing an existing modulefile is
appropriate. While each modulefile has its unique characteristics, they all set some variables describing
the top-level directory, and editing to adjust the string should be sufficient. You may need to repeat the
adjustment if you update the modulefiles_hptc RPM or otherwise rebuild your system.
If the package is a variant, for example, a beta version of a compiler, first copy the default modulefile to
a well-named copy, then edit the copy. You need root access to modify the modulefiles, which is generally
needed to install packages in either the /opt or /usr directories.
If you download a package into a private directory, you can create a private modulefiles directory. You
can then copy the corresponding default modulefile from under the /opt/modules/modulefiles
directory into a private modulefiles directory, edit the file, and then register the directory with the module
use
command.
3.2 Supplied Modulefiles
The HP XC system provides the Modules Package (not to be confused with Linux kernel modules) to
configure and modify the user environment. The Modules Package enables dynamic modification of a
user's environment by means of modulefiles.
The HP XC system supplies the modulefiles listed in Table 3-1 .
Table 3-1 Supplied Modulefiles
Sets the HP XC User Environment to Use: Modulefile
GCC C compiler, Version 3.4. gcc/3.4/default
GCC compiler, Version 4.0. gcc/4.0/default
GCC compiler, Version 4.1. gcc/4.1/default
HP-CPI profiling tools. hpcpi
HPTC loader. hptc
Intel C/C++ Version 8.0 compilers. icc/8.0/default
Intel C/C++ Version 8.1 compilers. icc/8.1/default
Intel C/C++ Version 9.0 compilers. icc/9.0/default
Intel C/C++ Version 9.1 compilers. icc/9.1/default
Intel IDB debugger. idb/7.3/default
Intel IDB debugger. idb/9.0/default
Intel IDB debugger. idb/9.1/default
Intel Fortran Version 8.0 compilers. ifort/8.0/default
Intel Fortran Version 8.1 compilers. ifort/8.1/default
Intel Fortran Version 9.0 compilers. ifort/9.0/default
Intel Fortran Version 9.1 compilers. ifort/9.1/default
32 Configuring Your Environment with Modulefiles