Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [hwloc-devel] hwloc embedding vs libltdl
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2013-05-08 16:16:06


Le 08/05/2013 13:09, Jeff Squyres (jsquyres) a écrit :
> 2. My thoughts were preventing hwloc from going thru some of the pain that OMPI went thru w embedding. Libibverbs has the same problem. If you have middleware that uses plugins that, in turn, uses plugins, it's a bit complicated to support fully static builds properly (OMPI and hwloc do, but libibverbs doesn't easily, but still, it may require a rebuild of hwloc with enable-static). Also, the problem with opening DSOs in private namespaces still exists; there's no good solution for that (when both the middleware and hwloc use plugins).

But this issue is only in the embedders (OMPI), not in the embeddee
(hwloc), right?

I can get plugins to work in tests/embedded by adding 2 lines to its
configure.ac (see the attached patch, which also removes your error
message and creates a shared lib containing libhwloc_embedded).

In short, I don't really see what risk we would be taking on the hwloc
side if we keep embedding+plugins possible (and still don't enable
plugins by default).

> 3. Open MPI also get flack for embedding lib ltdl and libevent. Although libltdl now has the built in options for using an external libltdl (which is what the distros use), why go down this road if we don't need to embed libltdl?

OK

Brice