- Next message: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Previous message: Jeff Squyres: "Re: LAM: File locking failed in ADIOI_Set_lock"
- In reply to: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Next in thread: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Reply: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
On Jan 18, 2006, at 10:35 AM, Soumya,Teena, Ranjana,Liss,Navya wrote:
> We have installed the LAM package that comes with Debian Sarge. The
> program compiles even without -lmpi.
> The systems already had mpich2 installed in them. How can we make
> sure that we are using the mpicc from LAM implementation? Do we
> have to uninstall mpich2?
No, both should be able to co-exist on a cluster just fine (assuming
that they are installed into different locations). The main thing
you need to do is to set your $PATH to point to the MPI
implementation of your choice. You will likely even need to do this
in your shell startup files (e.g., .bashrc). Check the LAM FAQ --
there's a bunch of specific information in there about this.
A quick way to check is to run "which mpicc" and "which mpirun" to
see where they are located. Compare this to the output of, for
example, "which lamboot" -- they should probably be in the same
directory.
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
- Next message: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Previous message: Jeff Squyres: "Re: LAM: File locking failed in ADIOI_Set_lock"
- In reply to: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Next in thread: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
- Reply: Soumya,Teena, Ranjana,Liss,Navya: "Re: LAM: lam test suite failed"
|
