On Jan 25, 2005, at 7:01 PM, James Frye wrote:
> These questions have probably been answered before, but I can't seem to
> find anything relevant in the FAQ or archives, so..
>
> 1) How does one remove a pre-installed version of LAM? I bought a new
> laptop recently, and being in a hurry to get it running, just
> installed a
> Fedora distribution on in. It installed LAM (V 7.0, I think) in
> default
> places like /usr/bin. I need to have several versions of MPI on the
> machine (LAM w/ gcc, LAM w/ Intel compiler, MPICH, etc), so each
> package
> normally lives in a separate tree off of /opt. But I can't find a
> list of
> all the LAM files that Fedora installed, so I get conflicts.
You can probably just uninstall the LAM RPM that was installed by
Fedora ("rpm -e lam").
> 2) A related question: has anyone figured out a good way of handling
> this
> problem of using multiple MPIs? I have several machines on my home
> network that I use to test, and at present I have to set the path on
> each
> one by hand before running something. Is there a better way?
There have been a variety of solutions suggested about this:
1. Perhaps the most simplistic is to have a line in your shell startup
file that examines an external file to find out which LAM installation
to use. Consider this trivial csh-flavored example:
(in $HOME/.cshrc)
set path = ( `cat $HOME/.lampath` $path)
Then, just by changing the file $HOME/.lampath, you have effectively
changed which LAM installation you are using. There's endless
variations on this theme that are possible.
2. In OSCAR clusters, we use environment modules to distinguish between
different MPI installations. Hence, you can do stuff like:
module unload mpi
module load mpi/lam-blah
(modules are really handy, IMHO)
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
