As noted in the previous section, the mpe library can be installed as part of the mpich configure and make process or as an extension of an existing MPI implementation. This section describes the instructions and examples for each type of installation.
In this mpe installation, no switches or flags are required. The
configure in the top-level mpich directory will gather the necessary
information and pass it to the configures in the mpe and
jumpshot directories. If no switches and flags are given, then the
mpe library and the graphical tool jumpshot will be automatically
configured. However, the user can choose to override this by configuring
mpich with the following options:
-mpe_opts=MPE_OPTS
-jumpshot_opts=JUMP_OPTS
where MPE_OPTS is one or more of the choices in
Section Configure Options
, and JUMP_OPTS is one of the options in
Section Configure Options
. Multiple uses of -mpe_opts is allowed
to specify several options for the MPE configure.
In the top-level mpich directory,
./configure <mpich options>
make
In the top-level mpich directory,
./configure <mpich options> \
-mpe_opts=--with-tcldir=<path of tcldir> \
-mpe_opts=--with-tkdir=<path of tkdir>
make
In the top-level mpich directory,
./configure <mpich options> -prefix=<install directory>
make
This is useful if you wish to install mpich, the mpe library,
and jumpshot in a public place so that others may use it. To install
all 3 packages into the install directory, type
make installin the top-level mpich directory.
In the top-level mpich directory,
./configure <mpich options> -mpe_opts=--enable-jumpshot=no
make
The jumpshot configure is invoked through the mpe configure.
Thus, the way in which to disable the configuration of jumpshot is
through a configure option to the mpe configure. Refer to
section Installation Instructions
for instructions on how to install
jumpshot separately.
In the top-level mpich directory,
./configure <mpich options> -nompe
make
It should be noted here that after mpich is configured, it is possible
to configure the mpe library and jumpshot without reconfiguring
mpich. Or, if mpich needs to be reconfigured, there is often no
need to reconfigure the mpe library or jumpshot.
In this mpe installation, a specific MPI implementation switch is necessary. Also, if the MPI implementation is not mpich, then the generic flag -libdir is mandatory.
In the top-level mpe directory,
./configure --with-sgi -libdir=<directory path of libdir>
or
./configure --with-sgi64 -libdir=<directory path of libdir>
make
By not specifying --with-jumpshot_home (and not using mpich),
jumpshot does not get configured.
In the top-level mpe directory,
./configure --with-sp -libdir=<directory path of libdir> \
--with-jumpshot_home=<directory path of jumpshot>
make
By not specifying -bindir=DIR, the jumpshot executable will be
located in libdir/../bin. If specification of a particular bin
directory is desired, then configure as follows:
In the top-level mpe directory,
./configure --with-sp -libdir=<directory path of libdir> \
--with-jumpshot_home=<directory path of jumpshot> \
-bindir=<directory path of bindir>
make
In the top-level mpe directory,
./configure --with-mpich=<directory path of MPICH> \
--with-mpichdev=<library subdirectory for MPICH>
make
If your mpich implementation has a mpich/jumpshot subdirectory, there
is no need to configure with the option --with-jumpshot_home.
If not, then this is a necessary configure option.
In the top-level mpe directory,
./configure --with-sgi -libdir=<directory path of libdir> \
--with-jumpshot_home=<directory path of jumpshot> \
--with-jumpshot_opts=<jumpshot option>
make