Alan, Can you please compress and post your config.log ?
My understanding of the mentioned commit is it does not build the reachable/netlink component if libnl version 1 is used (by third party libs such as mxm). I do not believe it should abort configure Cheers, Gilles On Saturday, September 15, 2018, Alan Wild <a...@madllama.net> wrote: > I apologize if this has been discussed before but I've been unable to find > discussion on the topic. > > I recently went to build 3.1.2 on our cluster only to have the build > completely fail during configure due to issues with libnl versions. > > Specifically I was had requested support for mellanox's libraries (mxm, > hcoll, sharp, etc) which was fine for me in 3.0.0 and 3.0.1. However it > appears all of those libraries are built with libnl version 1 but the > netlink component is now requiring netlink version 3 and aborts the build > if it finds anything else in LIBS that using version 1. > > I don't believe mellanox's is providing releases of these libraries linked > agsinst liblnl version 3 (love to find out I'm wrong on that) at least not > for CentOS 6.9. > > According to github, it appears bwbarret's commit a543e7f (from one year > ago today) which was merged into 3.1.0 is responsible. However I'm having > a hard time believing that openmpi would want to break support for these > libraries or there isn't some other kind of workaround. > > I'm on a short timeline to deliver this build of openmpi to my users but I > know they won't accept a build that doesn't support mellanox's libraries. > > Hoping there's an easy fix here (short of trying to reverse the commit in > my build) that I'm overlooking here. > > Thanks, > > -Alan >
_______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
