This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Jeff Squyres wrote:
> We use lt_dlopen() to open the plugins (Libtool's wrapper for a
> portable dlopen). It opens all plugins (DSOs) in a private scope.
> That private scope is kept deep in the OPAL MCA base and not exposed
> elsewhere in the code base. So if you manually dlopen a plugin
> again, I'll bet that the linker realizes that that DSO has already
> been loaded into the process space and doesn't actually load it again
> (but doesn't fail). So the dlsyms fail because you don't have access
> to the private scope from where Libtool originally opened the DSO.
> Make sense?
Yes, I'm nodding my head vigorously (with a vacuous stare on my face).
Mostly, I think you're very smart and I'm not! I get the general
principles, but am unfamiliar with the details.
Never mind: --enable-static is exactly the flavor of suggestion I was
looking for. Thanks. I'm back in the saddle. Onward.