not much difference from a performance point of view.
the difference is more from a space (both memory and disk) point of view
also, if you --disable-dlopen, Open MPI is rebuilt when a single
component is updated.
(without it, you can simply make install from the updated component
directory)
so if you are developing a new component, *not* using --disable-dlopen
can save you some build time
Cheers,
Gilles
On 11/4/2016 5:12 PM, Mahmood Naderan wrote:
I will try that. Meanwhile, I want to know what is the performance
effect of disabling/enabling dlopen?
Regards,
Mahmood
On Fri, Nov 4, 2016 at 11:02 AM, Gilles Gouaillardet
<gil...@rist.or.jp <mailto:gil...@rist.or.jp>> wrote:
Yes, that is a problem :-(
you might want to reconfigure with
--enable-static --disable-shared --disable-dlopen
and see if it helps
or you can simply manuall edit
/opt/openmpi-2.0.1/share/openmpi/mpifort-wrapper-data.txt,
and append -ldl to the libs_static definition
Cheers,
Gilles
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
