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
Tobias / all --
I swear there were further mails about this topic, but perhaps they were
off-list.
The end result is that this has finally been confirmed as an Intel 9.1 C++
compiler bug. I don't know exactly what platforms it occurred on, but I was
eventually able to replicate Tobias' problem
On Fri, 2006-10-06 at 10:18 -0400, Brian W. Barrett wrote:
> Is there a platform on which this breaks? It seems to have worked well
> for years... I'll take a closer look early next week.
Have you had a chance to look at this yet?
I could use a new "release" to build from since something curren
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/-
If I configure and build OpenMPI 1.1.1 with only --enable-shared, the
files listed below are created. If I build with both --enable-shared
and --enable-static, these same files do not appear in the final
install. Is this the correct behavior?
Thanks,
david
> /opt/OpenMPI/openmpi-pgi-1.1
Hello Jeff,
thank you very much for your help. I'm currently downloading the new
release and I hope I'll be able to test it next week.
Best Regards, Tobias
Jeff Squyres wrote:
> Tobias / all --
>
> I swear there were further mails about this topic, but perhaps they were
> off-list.
>
> The e
