LAM RPM notes:
Please note the following:
- The LAM tree is installed with a prefix of
/usr.
- All RPMs were build with the default GNU compilers (C, C++, and
Fortran). See below for which version of the GNU compilers were
used. If you wish to use a different set of compilers for your
MPI applications (such as a commercial compiler or a different
version of the GNU compilers), you will likely need to
build/install LAM/MPI from source using the same compilers.
Otherwise, your MPI applications may fail to link or run
correctly.
- Fortran support is included in all RPMs.
- ROMIO support is included in all RPMs.
LAM/MPI 7.1.4 RPMs:
- There are a choice of two sets of RPMs available: the
"all-in-one" RPM (which essentially contains the results of
"make install") or the "split-into-multiple" RPMs (which
contains the same output, but split into multiple RPMs for
those who want finer-gained control of exactly what is
installed on a given machine). The breakdown of the multiple
RPMs are as follows:
- lam-devel: Wrapper compilers (
mpicc and
friends), header files, and MPI function man pages. You
need this RPM if you want to compile LAM/MPI
applications.
- lam-docs: Example MPI programs, additional copyright
information, man pages on the rest of the LAM commands.
- lam-extras: Extra LAM/MPI commands that most
installations don't need.
- lam-runtime: The only RPM you need if you only want to
run LAM/MPI applications.
More than one RPM can be installed on a given node -- for
example, on "compile" nodes, it is common to install
lam-devel, lam-docs, and
lam-runtime. For compute nodes, some
administrations prefer to only install
lam-runtime.
- Both sets of RPMs contain the same RPI modules: crtcp lamd,
sysv, tcp, usysv. NOTE: Due to the wide
variety of Myrinet and Infiniband installations, the gm and
ib RPI modules are not included in the RPM. You
must build/install LAM/MPI from the source
code.
- C++ bindings are provided for all MPI functions.
- This RPM was built on a Red Hat EL 4 machine with the default
GNU compilers (3.4.5), meaning that
g77 was used
for the Fortran bindings, not gfortran. If you
wish to use the non-default GNU v4 compilers with
gfortran, you must build from source or rebuild
the SRPM with different options to configure.
LAM/MPI 7.0.6 RPMs:
- There is only one binary RPM provided (and its associated
source RPM). It includes the following RPI modules: crtcp,
lamd, sysv, tcp, usysv. NOTE: Due to the
wide variety of Myrinet installations, the gm RPI module is
not included in the RPM. You must
build/install LAM/MPI from the source code.
- C++ bindings are provided for all MPI functions.
- This RPM was built on a Red Hat 9 machine with the default
GNU compilers (3.2).
LAM/MPI 6.5.9 RPMs:
- Six RPMs are provided: TCP transport, SYSV transport, and
USYSV transport, and source RPMs for each transport.
- C++ bindings are provided for all MPI-1 functions.
- This RPM was built on a Red Hat 7.1 machine with the default
GNU compilers (2.96).
Source RPMs: If you are rebuilding the LAM SRPM,
please note that you must have recent versions of the GNU Autotools and
Libtool. If you do not, you may experience problems with thread
library symbols. This
thread on the LAM user's mailing list describes why you need
recent versions.
Older RPMs: Prior to version LAM/MPI 6.3.2,
non-standard spec files were used to create the LAM/MPI RPM files.
With the gracious donation of a standardized spec file from RedHat,
LAM 6.3.2 (and higher) RPMs can use the normal mechanisms of install
and update. Hence, if you are upgrading from an RPM version of LAM
prior to 6.3.2, you will need to remove the previous
RPM first (with rpm -e ...). Unfortunately, the
previous RPMs are indexed differently than the official RPMs, and the
"update" option of RPM will not detect that it is an upgrade.
Upgrading between versions of the official RPM's will work as
expected; there is no need to remove the previous RPM first.
