HP-MPI Version 2.2 for Linux Release Note

HP-MPI V2.2 for Linux Release Note
What’s in This Version
11
To use rsh instead, the following script needs to be run as root on each node in the cluster:
% /opt/hpmpi/etc/mpi.remsh.default
Or, to use rsh, use the alternative method of manually populating the files
/etc/profile.d/hpmpi.csh and /etc/profile.d/hpmpi.sh with the following settings
respectively:
setenv MPI_REMSH rsh
export MPI_REMSH=rsh
C++ bindings
HP-MPI 2.2 now supports C++ bindings as described in the MPI-2 Standard. If compiling and
linking with the mpiCC command, no additional work is needed to include and use the
bindings. You can include either mpi.h or mpiCC.h in your C++ source files.
The bindings provided by HP-MPI are an interface class, calling the equivalent C bindings. To
profile your application, users should profile the equivalent C bindings.
If the user builds without the mpiCC command, they will need to include -lmpiCC to resolve
C++ references.
If you want to use an alternate libmpiCC.a with mpiCC, use the -mpiCClib <LIBRARY>
option. A 'default' g++ ABI compatible library is provided for each architecture except Alpha.
Non-g++ ABI compatible C++ compilers The C++ library provided by HP-MPI,
libmpiCC.a, was built with g++.
If you are using a C++ compiler which is not g++ ABI compatible (e.g. Portland Group
Compiler), you must build your own libmpiCC.a and include this in your build command. The
sources and Makefiles to build an appropriate library are located in
/opt/hpmpi/lib/ARCH/mpiCCsrc.
To build your private version of libmpiCC.a and include it in the builds using mpiCC, do the
following:
1. Copy the files from /opt/hpmpi/lib/ARCH/mpiCCsrc to a working directory, where
ARCH is the architecture are using:
% cp /opt/hpmpi/lib/linux_amd64/mpiCCsrc/* /scratch/libmpicc
% cd /scratch/libmpicc
2. Edit the Makefile and define your CXX and MPI_ROOT to the correct locations.
3. Perform the make. This should build libmpiCC.a in your working directory: