Hi ompi developers, If you always configure ompi with --disable-dlopen you can delete this message now.
There has been some discussion of end case situations with use of dlopen in the ompi mca framework that can lead to unresolved symbols when subsequent shared libraries are dlopen'd that might needs symbols from a library that had been opened previously. Yes these libraries should be doing something like a second dlopen of the lib they are dependent on, but that's a different story involving other software projects outside of ompi. The default with the mca framework dlopen'ing of component libraries is not to use RTLD_GLOBAL, and there does not currently appear to be a way to change this behavior at runtime. Is there a reason for avoiding use of RTLD_GLOBAL in libltdl's use of dlopen? Would it be okay to add RTLD_GLOBAL to the default module_flags used in the vm_open - modulo detection of the definition of RTLD_GLOBAL at compile time. Perhaps adding a way with an env. or config option to not enable RTLD_GLOBAL by default? Thanks, Howard
