Hello Jeff,
Fristly, don't worry about jumping in late, I'll send you a skid rope
;) Secondly, thanks for your nice little artilces on clustermonkey.net (good
refresher on MPI). And finally, down to my issues, thanks for clearing out the
--prefix LD_LIBRARY_PATH and all. The ebuild I ma
.@sun.com; Open MPI Users
> Subject: Re: [OMPI users] pls:rsh: execv failed with errno=2
>
> Thanks for pointing out the LD_LIBRARY_PATH64 ...that
> explains much. As for the original error, I am still "a duck
> out of watter". I will try the 1.1rxxx trunck though
Thanks for pointing out the LD_LIBRARY_PATH64 ...that explains much. As for the
original error, I am still "a duck out of watter". I will try the 1.1rxxx
trunck though (creating an ebuild for it as we speak)
Eric
Le vendredi 16 juin 2006 11:44, Pak Lui a écrit :
> Hi Eric,
>
> I started to see
Hi Eric,
I started to see what you are saying. You tried to point out that you
are using the libdir to lib64 instead of just lib and somehow it doesn't
get picked up.
I personally have not tried this option though, so I don't think I can
help you much here. But I saw that there are changes i
Hello,
I don't want to get too much off topic in this reply but you're
brigning out a point here. I am unable to run mpi apps on the AMD64 platform
with the regular exporting of $LD_LIBRARY_PATH and $PATH, this is why I have no
choice but to revert to using the --prefix approach. Here ar
Hi, I noticed your prefix set to the lib dir, can you try without the
lib64 part and rerun?
Eric Thibodeau wrote:
Hello everyone,
Well, first off, I hope this problem I am reporting is of some validity,
I tried finding simmilar situations off Google and the mailing list but
came up with only
Hello everyone,
Well, first off, I hope this problem I am reporting is of some
validity, I tried finding simmilar situations off Google and the mailing list
but came up with only one reference [1] which seems invalid in my case since
all executions are local (naïve assumptions that it m
