Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Jeff Squyres (jsquyres)
This is a losing battle. We can't keep an up-to-date table in our configury of what downstream packages were compiled with what versions of libnl, not only because it would quickly become out of date, but also because the downstream package may be variable (e.g., libfabric, as I cited in http:

Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Jeff Squyres (jsquyres)
On Aug 24, 2015, at 9:31 AM, Gilles Gouaillardet 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

Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Gilles Gouaillardet
a first step could be adding a --disable-libnl3 option to configure, which means components should not even try to use libnl3 makes sense ? On Monday, August 24, 2015, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > iirc, librdmacm uses libnl > > I am not sure if handling this at r

Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Gilles Gouaillardet
fwiw, in my environment, libnl is loaded before libnl3 the crash occurs in libnl3 initializer, which is invoked when dlopen'ing mca_reachable_netlink.so it is very strange since some initialized static structs (same name, different type and value in both libraries) are incorrectly initialized (or a

Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Gilles Gouaillardet
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 On Monday, August 24, 2015, Jeff Squyres (jsquyres) wrote: > It is definitely

Re: [OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Jeff Squyres (jsquyres)
It is definitely true that if both libnl v1 and libnl v3 (also known as "libnl3", even though libnl v1 is known as "libnl") are present in the same process, Random Bad Things will happen. This is due to unfortunate choices that the netlink library authors and/or packagers made. >From what I ha

[OMPI devel] reachable_netlink mca, libnl and libnl3

2015-08-24 Thread Gilles Gouaillardet
Folks, I recently installed libnl3-devel rpm on my centos 7 box, reconfigured and recompiled ompi, and ompi_info now crashes. it seems the root cause is an obscure conflict between libnl and libnl3. libnl is indirectly required by the common_verbs mac (OFED libraries do need it) and libnl3 is req