Jeff,
thanks for your answer on this.
> Sorry for the delay.
No problem. Better delayed than never. ;-)
> Which version of Open MPI are you referring to? I'm offline at the
> moment, and I think you're referring to the OMPI 1.6 series -- I'm
> pretty sure we renamed these libraries in the 1.7/1
On Oct 14, 2014, at 12:33 AM, Marc-Andre Hermanns
wrote:
>> No. Also note that in OMPI 1.7/1.8, we have renamed the Fortran
>> wrapper to be mpifort -- mpif77 and mpif90 are sym links to mpifort
>> provided simply for backwards compatibility.
>
> Thanks for the heads up. Complicates our config
Jeff,
>>> No. Also note that in OMPI 1.7/1.8, we have renamed the Fortran
>>> wrapper to be mpifort -- mpif77 and mpif90 are sym links to mpifort
>>> provided simply for backwards compatibility.
>>
>> Thanks for the heads up. Complicates our configuration a little but good
>> to know. ;-)
>
> I'
Hi,
Perhaps I've missed something but is it possible to build openmpi (any version)
so that:
* tools (e.g., orted) are statically linked
* shared libs are built
This would help avoid lib dependencies on orted at start up.
Thanks,
John
This is not a common use case because the LD_LIBRARY_PATH requirements for the
orted and friends are the same as for the MPI executables. So reducing the
dependency requirements for the orted doesn't really buy you much.
However, you could probably do this manually:
-
# Build static execut
Dear Open MPI fans and experts
This is just a note in case other people run into the same problem.
I just built Open MPI 1.8.3.
As usual I put my old settings on openmpi-mca-params.conf,
with no further thinking.
Then I compiled the connectivity_c.c program and tried
to run it with mpiexec.
That
On Oct 14, 2014, at 5:32 PM, Gus Correa wrote:
> Dear Open MPI fans and experts
>
> This is just a note in case other people run into the same problem.
>
> I just built Open MPI 1.8.3.
> As usual I put my old settings on openmpi-mca-params.conf,
> with no further thinking.
> Then I compiled th
