LAM/MPI logo

LAM FAQ: Platform Specific Questions

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just the FAQ
Table of contents:
  1. Does LAM/MPI work under Mac OS X?
  2. Does LAM/MPI work under Microsoft Windows?
  3. Does LAM/MPI work under PBS?
  4. Does LAM work under LSF?
  5. Does LAM/MPI work with Absoft's ProFortran compiler
  6. Does LAM/MPI work with the Portland Group compilers?

[ Return to FAQ ]


1. Does LAM/MPI work under Mac OS X?
Applies to LAM 7.0 and above

Yes, with a couple important notes.

The OS X Developer Tools are requied for using LAM. They are available free of charge from the Apple Developers site. The Developer Tools do not include a Fortran compiler, so you will either have to provide a Fortran compiler or build LAM with the --without-fc option to configure.

Mac OS X can use either HFS+ or UFS as its underlying filesystem. The most popular choice seems to be HFS+, which is not case sensitive - mpicc and mpiCC are the same file. As the LAM wrapper compilers are named mpicc and mpiCC for C and C++, respectively, this caused some problems. Therefore, we have renamed the C++ compiler to be mpic++.

[ Top of page | Return to FAQ ]


2. Does LAM/MPI work under Microsoft Windows?

LAM/MPI 7.1 will support Cygnus environment under Windows. The LAM team has finished porting LAM/MPI to Cygwin (kernel version 1.5.5). Currently, tcp, lamd, sysv and usysv RPIs are supported. romio is not supported. If you are interested in starting to use LAM/MPI under Cygwin right away, please download our nightly trillium tar-ball .

There are some special instructions to be followed in order to install the sysv and usysv modules. Please refer to the LAM/MPI User's guide and LAM/MPI Installation guide for more instructions.

Since there are some issues with the use of the native cygwin terminal for standard Io redirection, it is advised to run MPI applications on xterm. For more information on getting X services installed for Cygwin, please refer to the XFree86 project

Although we tried to port the complete functionality of LAM/MPI to Cygwin, because of some outstanding portability issues, execution of LAM/MPI applications on Cygwin may not always be reliable.

[ Top of page | Return to FAQ ]


3. Does LAM/MPI work under PBS?
Applies to LAM 7.0 and above

Yes!

LAM/MPI will work under the PBS environment without problem. Starting with LAM 7.0, LAM is able to use the TM interface to PBS, eliminating the need for rsh/ssh. For more information, please see the LAM/MPI User's Guide.

A minimal PBS script to run an application foobar might look like:

#!/bin/sh
 
### Job name
#PBS -N lam-foobar
 
### Run the application
lamboot $PBS_NODEFILE
mpirun C foobar
lamhalt

exit 0
The SciClone cluster project at the College of William and Mary has developed a useful set of scripts for running LAM/MPI jobs under PBS. They were kind enough to make the script and man page available for other users. More information can be found in this mail to the LAM/MPI users list. If you have a great script for using LAM/MPI under PBS (or any other batch scheduling system) and are willing to make it available for others, please send a message to the LAM/MPI general use's mailing list and we will add the solution to this list.

[ Top of page | Return to FAQ ]


4. Does LAM work under LSF?
Applies to LAM 6.5.7 and above

Yes!

LAM/MPI will work under the LSF environment without problem. LAM/MPI still must use rsh or ssh to start the LAM environment. A minimal LSF script to run an application foobar might look like:

#!/bin/sh
 
# Run the application
lamboot hostfile
mpirun C foobar
lamhalt

exit 0

See the question, "Does LAM/MPI work under PBS?" for additional resources and helpful scripts for batch queue administrators.

[ Top of page | Return to FAQ ]


5. Does LAM/MPI work with Absoft's ProFortran compiler

Yes - recent versions of LAM work without problem with the Absoft compilers. The only change required is to tell the LAM configure script to use the Absoft ProFortran compiler. This can be done in one of three ways:

  • Ensure that the Absoft f77 compiler appears before any other binary named f77 in your path.
  • set the FC environment variable to the full path to the Absoft copmiler (ie, /Applications/Absoft/bin/f77 on most Mac OS X installations)
  • Specify --with-fc=full_path_to_compiler when running configure.

Unlike traditional Fortran compilers, recent Absoft compilers are case sensitive by default. This can cause problems with many Fortran MPI applications, which often assume the compiler is case-insensitive.

The easiest solution to this problem is to tell the Absoft compiler to not be case-sensitive. This can be acheived by passing the -f flag to the compiler. This must be done both during the compiling of LAM and whenever any MPI applications are compiled with mpif77. In order to build LAM with the -f flag, either set the environment variable FFLAGS before running configure or use the --with-fflags= option when running configure.

LAM and the Absoft compiler can be used together without specifying the -f flag. However, all MPI function calls and constants will have to be specified in all UPPERCASE for the application to properly link with the MPI library.

[ Top of page | Return to FAQ ]


6. Does LAM/MPI work with the Portland Group compilers?

Yes. At configure time, either set the environment variables CC, CXX, and FC to specify the PGI C, C++, and Fortran compilers (respectively) or use the --with-cc=, --with- cxx, and --with-fc flags at configure time.

Due to a bug in Libtool, it may not be possible to build LAM with shared libraries with some Portland Group compilers. However, it is possible to build static libraries.

In the past, there have been small issues with LAM/MPI, Linux, and the PGI compilers. In all cases, the problem was traced to bugs in the Linux system header files. The latest such problem was with Red Hat 7.1. If you are using Red Hat 7.1, you will want to apply the Red Hat provided updates to glibc to fix some minor system header file issues.

[ Top of page | Return to FAQ ]