On Sep 17, 2008, at 9:49 AM, Paul Kapinos wrote:
If we add an " -x OPAL_PREFIX " flag, and through forces explicitly
forwarding of this environment variable, the error was not occured.
So we mean that this variable is needed to be exported across *all*
systhems in cluster.
It seems, the
Hi Rolf,
Rolf vandeVaart wrote:
I don't know -- this sounds like an issue with the Sun CT 8 build
process. It could also be a by-product of using the combined 32/64
feature...? I haven't used that in forever and I don't remember the
restrictions. Terry/Rolf -- can you comment?
I will
Paul Kapinos wrote:
Hi Jeff again!
(update) it works with "truly" OpenMPI, but it works *not* with SUN
Cluster Tools 8.0 (which is also an OpenMPI). So, it seems be an SUN
problem and not general problem of openMPI. Sorry for false relating
the problem.
Ah, gotcha. I guess my Sun
On Sep 17, 2008, at 5:49 AM, Paul Kapinos wrote:
But the setting of the environtemt variable OPAL_PREFIX to an
appropriate value (assuming PATH and LD_LIBRARY_PATH are setted
too) is not enough to let the OpenMPI rock from the new
lokation.
Hmm. It should be.
(update) it works with
Hi Jeff again!
But the setting of the environtemt variable OPAL_PREFIX to an
appropriate value (assuming PATH and LD_LIBRARY_PATH are setted too)
is not enough to let the OpenMPI rock from the new lokation.
Hmm. It should be.
(update) it works with "truly" OpenMPI, but it works *not* with
Short answer: yes, we do compile in the prefix path into OMPI. Check
out this FAQ entry; I think it'll solve your problem:
http://www.open-mpi.org/faq/?category=building#installdirs
On Sep 8, 2008, at 5:33 AM, Paul Kapinos wrote:
Hi all!
We are using OpenMPI on an variety of machines
Hi all!
We are using OpenMPI on an variety of machines (running Linux,
Solaris/Sparc and /Opteron) using couple of compilers (GCC, Sun Studio,
Intel, PGI, 32 and 64 bit...) so we have at least 15 versions of each
release of OpenMPI (SUN Cluster Tools not included).
This shows, that we have
