Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] hwloc embedding vs libltdl
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2013-05-09 09:02:10


On May 9, 2013, at 8:55 AM, Brice Goglin <Brice.Goglin_at_[hidden]> wrote:

> +Although hwloc plugins may be used in embedded mode, the embedder
> +project will have to manually setup libltdl in its build system so
> +that hwloc can load its plugins.
> +Also, embedders should avoid using their own plugins and hwloc plugins
> +simultaneously because of possible issues with public and private
> +namespaces when using libltdl.
> +The embedder project is strongly advised not to use libltdl.

Tweaked:

Although hwloc dynamic shared object plugins may be used in embedded mode, the embedder project will have to manually setup libltdl in its build system so
that hwloc can load its plugins at run time. Also, embedders should be aware of complications that can arise due to public and private linker namespaces (e.g., if the embedded project is loaded into a private namespace and then hwloc tries to dynamically load its plugins, such loading may fail since the hwloc plugins can't find the hwloc symbols they need). The embedder project is *strongly* advised not to use hwloc's dynamically loading plugins / libltdl capability.

-- 
Jeff Squyres
jsquyres_at_[hidden]
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/