----- Original Message -----
From: "Jeff Squyres" <jsquyres_at_[hidden]>
To: "General LAM/MPI mailing list" <lam_at_[hidden]>
Sent: Tuesday, August 01, 2006 1:13 PM
Subject: Re: LAM: 6.5.6 installation
>I would also assume that this is due to a bad install somehow. It sounds
> like you installed LAM locally on both machines. Did you install via
> source
> (ie., "make all install")? If so, was there anything obvious in the "make
> install" output that indicated that something failed? There should be a
> fairly obvious indication of when the lam-conf.lamd file is copied to the
> installation location.
>
> Another issue to be sure of is that you aren't inadvertantly mixing
> versions
> of LAM -- many Linux distros ship with LAM/MPI these days. You might want
> to ensure that a distro-installed version is not getting in your way, etc.
>
Ah - yes - staring me in the face in the end - 7.1.2 on the master and 6.5.6
on the slaves.
However this does bring me to another point. 6.5.6 refuses to compile on
the newest box (Ubuntu 6.06) - not sure why - never have been too hot on
errors from makes. Is this something to do with gcc under Ubuntu 6.06
being different to the gcc that was in Slackware 7.1 (on which the 6.5.6
compiles ok)?
So now I have two possible options:
1) Try and make 6.5.6 compile on the new box
or
2) Throw out all the old boxes because they won't compile 7.1.2 (they
refused to compile 6.6.x as I recall because they were too low on resources
and a quick cross compile failed).
1) seems easiest - or is it too much trouble trying to compile 6.5.6 on a
very new distro
2) is a hell of a lot of work reghosting 8 machines.
Any advice?
Cheers
Rob
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.5/404 - Release Date: 31/07/2006
|
