In answer to your suggestions:
1). I have sent the make log and configure log on a previous mail (
waiting on replies).
2). I have tried using the prefix like suggested but i got exactly the
same result.
3). There are no other versions of lam on the machine, i tried a
find/which and rpm search.
The main problem at the moment is that it does not put the install anywhere
on my system after running make or make install. Any idea please let me
know.
Regards
(Embedded image moved to file: pic08942.jpg)
|---------+---------------------------->
| | Jeff Squyres |
| | <jsquyres_at_lam-mpi|
| | .org> |
| | Sent by: |
| | lam-bounces_at_lam-m|
| | pi.org |
| | |
| | |
| | 19/01/2005 13:27 |
| | Please respond to|
| | General LAM/MPI |
| | mailing list |
| | |
|---------+---------------------------->
>-----------------------------------------------------------------------------------------------------------------------|
| |
| To: General LAM/MPI mailing list <lam_at_[hidden]> |
| cc: |
| Subject: Re: LAM: Cannot install Lam |
>-----------------------------------------------------------------------------------------------------------------------|
On Jan 19, 2005, at 8:01 AM, Terry Frankcombe wrote:
> What does the output of "make install" say? Are there errors
> reported? Where does install say it is putting stuff?
Yes -- that would be most helpful. You only performed part of 1 of my
3 recommendations (1. check the output of "make install", 2. use the
--prefix argument to configure, and 3. check to see if a conflicting
LAM version is installed).
Please do 1 and 2 and let us know the results (I am fairly confident
that proper use of 2 will solve your problems).
Also, note that RPM is not the only way to install software -- it's
quite possible that LAM is installed via another mechanism on your
nodes (e.g., if someone else LAM compiled from source, like you are
doing). Try "which lamboot" and so on. I only mention this because
the main reason that LAM's configure script will automatically choose
to install itself somewhere other than /usr/local is because it finds
"lamboot" in your path and assumes that you want to upgrade that
installation of LAM (disclaimer: we've been doing this for quite a
while in LAM's configure script, but I don't remember if it's in your
specific version of LAM or not).
Indeed, it's been a *long* time since I've used the 6.x series of LAM,
but I *think* that the installation directory should be in the first
few lines of configure's output.
>> --0__=0FBBE51DDFD72EA68f9e8a93df938690918c0FBBE51DDFD72EA6
>> Content-type: text/plain; charset=US-ASCII
>>
>> I have done a bit more investigating into my lam install issue. I have
>> found that i do not have any rpm packages relating to lam installed
>> on my
>> server as Engineering and scientific was not ticked on the initial
>> Redhat
>> install. So i should not have any conflict between different versions
>> on
>> lam. Can someone advise me on what i can do next with this issue, any
>> help
>> is much appreciated.
>>
>> Regards
>>
>
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
