On May 18, 2006, at 11:38 AM, Valter Dal Bo wrote:
> Back on the topic...
> I can see a problem here with the liblam version/lam runtime having to
> match.
> The problem is that I have a few different applications all beeing
> linked to different lam versions.
> The fact of having to match liblam version/lam runtime makes it
> impossible to run those applications on the same machine.
> That is a great obstacle.
> Of course I can change the lam version on the fly, accordingly to
> whatever application I have to run in that precise moment, but that
> would be quite uncomfortable.... :-(
>
> I remember reading in the FAQ that normally different lam versions
> cannot co-exist on the same machine and different machines have to run
> the same lam version.
> Is there a workaround on that issue ?
There is not a workaround for the requirement that an entire job run
the same version of LAM/MPI and that the runtime / application use
the same version of LAM.
If you have requirements that make multiple versions of LAM
necessary, I'd recommend looking into the modules package (http://
modules.sourceforge.net/). It was meant to deal with pretty much
exactly this situation.
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
