Yeah, there’s no good answer here from an “automatically do the right thing”
point of view. The reachable:netlink component (which is used for the TCP BTL)
only works with libnl-3 because libnl-1 is a real pain to deal with if you’re
trying to parse route behaviors. It will do the right thing
Alan --
Sorry for the delay.
I agree with Gilles: Brian's commit had to do with "reachable" plugins in Open
MPI -- they do not appear to be the problem here.
>From the config.log you sent, it looks like configure aborted because you
>requested UCX support (via --with-ucx) but configure wasn't
As request I've attached the config.log. I also included the output from
configure itself.
-Alan
On Fri, Sep 14, 2018, 10:20 AM Alan Wild 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
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
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
