On Aug 24, 2015, at 9:31 AM, Gilles Gouaillardet 
<gilles.gouaillar...@gmail.com> wrote:
> 
> iirc, librdmacm uses libnl
> 
> I am not sure if handling this at run time is even possible
> 
> why not handle this at configure time ?
> e.g. if a component known to use libnl is built, then make sure no component 
> uses libnl3

How can we know which version of libnl a downstream package chooses to use?

E.g., libfabric can be built with either libnl or libnl3: it depends on either 
the default or the packager's choice.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Reply via email to