HP-MPI User's Guide (11th Edition)

Debugging and troubleshooting
Troubleshooting HP-MPI applications
Chapter 6 205
Building on HP-UX and Linux
You can solve most build-time problems by referring to the
documentation for the compiler you are using.
If you use your own build script, specify all necessary input libraries. To
determine what libraries are needed, check the contents of the
compilation utilities stored in the HP-MPI $MPI_ROOT/bin
subdirectory.
HP-MPI supports a 64-bit version of the MPI library on 64-bit platforms.
Both 32- and 64-bit versions of the library are shipped on 64-bit
platforms. You cannot mix 32-bit and 64-bit executables in the same
application.
HP-MPI does not support Fortran applications that are compiled with
the following option:
•+autodblpad— Fortran 77 programs
Building on Windows
Make sure you are running the build wrappers (i.e. mpicc, mpif90) in a
compiler command window. This window is usually an option on the
Start->All Programs menu. Each compiler vendor provides their own
command window option which includes all the necessary paths for
compiler and libraries.
On Windows, the HP-MPI libraries include the 'bitness' in the library
name. HP-MPI provides support for both 32- and 64-bit libraries. The .lib
files are located in "%MPI_ROOT%\lib".
Starting on HP-UX and Linux
When starting multihost applications using an appfile, make sure that:
• All remote hosts are listed in your .rhosts file on each machine and
you can remsh to the remote machines. The mpirun command has the
-ck option you can use to determine whether the hosts and programs
specified in your MPI application are available, and whether there
are access or permission problems. Refer to “mpirun” on page 74.
MPI remsh can be used to specify other commands to be used, such
as ssh, instead of remsh.