Greg,
>>
I'm not sure why you need to use --prefix at all? Did you specify
a prefix when you ran configure on OpenMPI? That should set up everything
correctly so you should just need to use mpirun.
I think that’s a
different prefix.
From http://www.open-mpi.org/faq/?category=running#mpirun-prefix:
-----------------------------------------------------------------------------------
3. What if I can't
modify my PATH and/or LD_LIBRARY_PATH?
|
There are some
situations where you cannot modify the PATH or LD_LIBRARY_PATH -- e.g., some ISV application prefer to hide all parallelism
from the user, and therefore do not want to make the
user modify their shell startup files.
In such cases, you
have two options:
Use mpirun's --prefix command line option (described below).
Modify the wrapper
compilers to include directives to include run-time search locations for the
Open MPI libraries (see this FAQ
entry)
mpirun's --prefix command line option takes as an argument the top-level
directory where Open MPI was installed. While relative directory names are
possible, they can become ambiguous depending on the job launcher used; using
absolute directory names are strongly recommended.
For example, say that
Open MPI was installed into /opt/openmpi-1.2.4. You would use the --prefix option like this:
shell$ mpirun
--prefix /opt/openmpi-1.2.4 -np 4 a.out
|
This will prefix the PATH and LD_LIBRARY_PATH on both the local and remote hosts with /opt/openmpi-1.2.4/bin and /opt/openmpi-1.2.4/lib, respectively.
-----------------------------------------------------------------------------------
I apparently need it
to prefix the PATH and LD_LIBRARY_PATH on the remote host.
>> What other
arguments do you need?
(--prefix is one ;-)
In the link above, there are other command-line arguments to mpiexec, as there
are with most other implementations. In the Eclipse Java launcher, for
example, you have the option to enter JVM arguments _and_ program arguments.
>> Please try running the
ptp_orte_proxy program manually and let me know what output you see. I suspect
you have a LD_LIBRARY_PATH problem.