When building more than one version of mpich, for example, to
support two different devices or several different architectures, it
is important to build each one by configuring with a unique prefix and
installing the built mpich before building the next version. For
example, to build both a ch_p4 and a ch_shmem version
for a collection of Solaris workstations, the following commands
should be used:
./configure --with-device=ch_p4 -prefix=/usr/local/mpich-1.2.1/solaris/ch_p4 make >& make.log make install ./configure --with-device=ch_p4 -prefix=/usr/local/mpich-1.2.1/solaris/ch_shmem make >& make.log make installThis assumes that mpich is to be installed into /usr/local/mpich-1.2.1, and that the make.log files are checked to ensure that the creation of the libraries succeeeded.
Versions of mpich before 1.2.0 placed the device- and architecture-specific files into directories defined by mpich. With version 1.2.0, mpich follows (almost) the GNU approach to installation. In particular, you can override the choices of most of the directories with standard configure options. For example, to change the location of the libraries to /usr/local/lib, add the configure option -libdir=/usr/local/lib. If you override any of the directories, use bin/mpiinstall instead of make install as the command to install mpich.