Q-Logic IB6054601-00 D manual Run Time Errors With Different MPI Implementations, # /etc/ldconfig

Q

C – Troubleshooting InfiniPath MPI Troubleshooting

The above compiler command insures that the program will run using this path on any machine.

For the second option, we change the file /etc/ld.so.conf on the compute nodes rather than using the -Wl,-rpath,option when compiling on the development node. We assume that the mpi-lib-*rpm is installed on the compute nodes with the same --prefix /path/to/libsoption as on the development nodes. Then, on the computer nodes we then add the following lines to the file /etc/ld.so.conf.

/path/to/libs/lib

/path/to/libs/lib64

Then, to make sure that the changes are picked up, run (as root):

#/etc/ldconfig

The libraries can now be found by the runtime linker on the compute nodes. This method has the advantage that it will work for all InfiniPath programs, without having to remember to change the compile/link lines.

2.Instead of either of the two above mechanisms, you can also put this line in the

~/.mpirunrc file:

export LD_LIBRARY_PATH=/path/to/libs/{lib,lib64}

See Section 3.5.8 in the chapter “Using InfiniPath MPI” for more information on using the -rcfileoption to mpirun.

Choices between these options are left up to the cluster administrator and the MPI developer. See the documentation for your compiler for more information on the compiler options.

C.8.7

Run Time Errors With Different MPI Implementations

It is now possible to run different implementations of MPI, such as HP-MPI, over InfiniPath. Many of these implementations share command (such as mpirun) and library names, so it is important to distinguish which MPI version is in use. This is done primarily through careful programming practices.

IB6054601-00 D C-17