There were long, religious debates about exactly this issue in the
OMPI developer group. The end result is pretty much a generalization
of what Michael said: our wrappers should do the absolute minimum to
compile and link MPI executables. That is, we provide the -I's, -
L's, and -l's neces
On Oct 11, 2006, at 10:38 AM, Lisandro Dalcin wrote:
On 10/11/06, Jeff Squyres wrote:
Open MPI v1.1.1 requires that you set your LD_LIBRARY_PATH to
include the
directory where its libraries were installed (typically, $prefix/
lib). Or,
you can use mpirun's --prefix functionality to avoid
On 10/11/06, Jeff Squyres wrote:
Open MPI v1.1.1 requires that you set your LD_LIBRARY_PATH to include the
directory where its libraries were installed (typically, $prefix/lib). Or,
you can use mpirun's --prefix functionality to avoid this
BTW, Why mpicc/mpicxx does not symply pass a -rpath/-
Hum; that's quite odd. In Open MPI, mpirun and mpiexec are both sym links
to the same back-end executable (orterun). So if you can run one, you must
be able to run both.
I suspect that your mpirun and mpiexec are being found in different places
-- try "which mpirun" and "which mpiexec" (or "wher
Ok, I apologize in advance. I am still trying to get openmpi to compile
and run with PGI, Myrinet and PBSPro.
I am configuring it with:
--with-gm=/opt/gm --disable-shared --enable-static
--enable-mca-static=pml,btl:gm,btl:self --with-tm=/usr/pbs CC=pgcc
CXX=pgCC F77=pgf77 FC=pgf90 FFLAGS=-fastsse
