Check the output of "make install" to see where LAM installed itself.
It probably installed itself to an alternate location. Unless an
explicit --prefix is mentioned on the configure line, LAM will look for
where the executable "lamboot" lives and use that as an implicit
--prefix.
So you should probably use an explicit --prefix=/usr/local argument to
configure.
You should also check to ensure that you don't have other copies of LAM
installed that would be used instead of the one you're currently
installed (e.g., I don't know of RH WS comes with a LAM RPM already
installed, etc.).
On Jan 18, 2005, at 7:56 AM, Andrew.Bridgeman_at_[hidden] wrote:
> Hello,
> I currently have 16 Redhat 7.1/7.3 machines running lam
> 6.5.6 which are used by my users for lamboot. The current way we
> install 6.5.6 is to:
>
> Extract the tar file to /usr/local
> cd lam6.5.6 directory
> type - ./configure -with-no-fflags=-fno-second-underscore -with-shared
> -without-fc
> type - make install
> Done
>
> I am installing 22 Redhat WS Version 3 servers and i have built one
> already and have tried our normal install procedure above but it does
> not seem to install properly as normally we have allot of files and
> links in the /usr/local/bin directory which allows the users to run
> lamboot but there is nothing appearing in this directory so obviously
> something is wrong. I am not sure if it because i am using a new
> version of redhat or i have just missed something.
>
> Unfortunately we need to run this version of the lam because the
> software we run requires this particular version.
>
> If anyone has ideas on what i can do / try or change, any help would
> be much appreciated as i need to built all the other machines with lam
> working ASAP
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
