XMPI 2.2 will only work with LAM It will not work with any version of LAM prior to LAM . This file contains the installation instructions
for XMPI 2.2
Installing from RPMS
shell# rpm -ivh xmpi-2.2-.i386.rpm
or
shell# rpm -ivh xmpi-2.2-.src.rpm
Important Note:
XMPI depends on the Motif libraries, Lesstif or Motif must be installed.
Further, Lestif must either be installed using RPMS (available on
their web page) or RPM will not find the Lestif libraries and will not
allow XMPI to be installed.You can circumvent this problem by using
the command :
shell# rpm -ivh --neodepsxmpi-2.2-.i386.rpm
Installing from source
For the impatient
If you don't want to read the rest of the instructions, the following
should do the trick for most situations:
shell$ gunzip -c xmpi-2.2-.tar.gz | tar xf -
shell$ cd xmpi-2.2-.tar.gz
shell$ ./configure --prefix=/path/to/install/in
[...lots of output...]
shell$ make
[...lots of output...]
shell# make install
If you do not specify a prefix, XMPI install under
/usr/local/. Now go read the Release
notes; they contains all the information about the new features of
this release of XMPI.
Unpacking the distribution
The XMPI source directory is packaged as a compressed tape archive
xmpi-2.2-.tar.gz or xmpi-2.2-.tar.Z.
Uncompress the archive and extract the sources.
shell$ gzip -d -c xmpi-2.2-.tar.gz | tar xf -
or
s
shell$ uncompress -c xmpi-2.2-.tar.Z | tar xf -
Configuration
LAM uses a GNU configure script to perform site and architecture
specific configuration.
Change directory to the top level LAM directory (xmpi-2.2-) and run the
configure script.
shell$ ./configure {options}
or
shell$ sh ./configure {options}
NOTE: Unlike most configure scripts, XMPI's configure does
not follow the CC environmental variable. If you wish to
specify a compiler, you MUST use --with-cc.
By default the configure script sets the XMPI install directory to
/usr/local/. This can be overridden with the --prefix
option (see below).
The configure script will create several configuration files:
config.mk, XMPI, and Makefile. You may wish to inspect these files for a sanity
check, but ./configure usually guesses correctly.
The configure script recognizes the following options (shown here in
alphabetical order):
--enable-echo
Will echo all of the commands that configure executes. This is
usually for debugging purposes only, and is not recommended for end
users.
--prefix=PREFIX
Sets the installation location LAMHOME for the LAM binaries,
libs, etc., to directory PREFIX. PREFIX must be specified as an
absolute directory name.
--with-cc=CC
Use the C compiler CC. The C compiler can also be
selected by setting the "CC" environment variable before running
configure. This compiler will be used both to compile LAM, and as the
default compiler for the hcc(1) and mpicc(1)
wrapper compilers.
--with-cflags=CFLAGS Use the C compiler flags CFLAGS.
The flags passed to the C compiler can also be selected by setting the
"CFLAGS" environment variable before running configure. If CFLAGS are
not specified, ./configure will pick optimization flags
to use. These flags are *not* used as default flags in any of the
wrapper compilers.
--with-lam
Build XMPI with the LAM-libxmpi version of libxmpi. This will
allow you to use XMPI with the LAM implementation of MPI.
--with-ldflags=LDFLAGS Use the LD linker flags LDFLAGS.
If this flag is not set on the ./configure command line,
the value for CFLAGS is used. If LDFLAGS (and CFLAGS) are not
specified, ./configure will pick optimization flags to
use.
These flags are *not* used as default flags in any of the wrapper
compilers.
--with-sgi
Build XMPI to use the libxmpi provided by SGI for the SGI native
implimentation of MPI. In order to use this, you must have a SGI libxmpi
shared library available.
--with-shared
builds the LAM libxmpi library as a shared library
(libxmpi.so or libxmpi.sl), not the default
static library (libxmpi.a)
--with-vendor-libxmpi=DIR
Build with vendor supplied libxmpi in DIR
--help
Print a summary of the options to `configure', and exit.
--quiet
--silent
-q
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null'
(any error messages will still be shown).
--srcdir=DIR
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
--version
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
Example:
shell$ ./configure --with-sgi --with-cc=/bin/cc --with-cflags=-O4 -with-fc=no
Compile for the SGI MPI using the C compiler /bin/cc
with options -O4.
Building XMPI
Once the configuration step has completed, build XMPI by doing:
shell$ make
in the top level XMPI directory. This will build the XMPI binaries and
libraries. You should test the binary to make sure that the build
completed normally. To install the binaries, libraries, and man
pages, enter:
shell# make install
Note that you must have write permission in the install directory for
this command to work.
Running XMPI
The xmpi(1) man page describes the features and use of xmpi.
We suggest you run xmpi while reading the man page and try
things out as you read about them. To this end there is an example
trace file example.lamtr provided.
The Help item in the Help menu may provide additional
documentation on using xmpi. Selecting this item executes a
command specified by the XMPI.helpCmd resource. The default is
typically a command that fires up a Web browser to view a help page.
You can change this to invoke your favourite browser.
If while running xmpi it looks crooked, adjust the appropriate
XMPI or Motif resources in the previously installed application resource
file.
Clearing Space
After XMPI has been built, all of the objects can be removed by running the
make(1) utility with the "clean" target in the source directory.
shell$ make clean
If further space is required, the source directory can be taken off-line.
Only the installation directory need be maintained on-line.
Reporting problems
Problems building, installing or using XMPI should be addressed to the XMPI
mailing list. Please specify details such as machine architecture
and operating system on which the problem occurred. In the case of
compilation or installation errors, including a transcript of the run
would be most helpful.
If you have LAM 6.5.9 installed, please also
include the output produced by
shell$ lamboot -V
If you have LAM 7.0.6 installed, please also
include the output produced by
shell$ laminfo
|