[libfabric-users] libnl error

[Jeff Squyres (jsquyres)]

Martin --

This feels like a bug on the libfabric side, but I'm not 100% sure.  I can't speak to the MXM integration in libfabric -- I filed a GitHub issue to track this:

    https://github.com/ofiwg/libfabric/issues/2583

> On Dec 7, 2016, at 2:53 PM, Martin Cuma <martin.cuma at utah.edu> wrote:
> 
> Hi Jeff,
> 
> the libnl trick worked as long as we removed the libnl-devel, and installed libnl3-devel instead. I wish RedHat would just install the libnl3-devel by default.
> 
> Now, I have another potential quirk with libfabric. I configured it to add Mellanox MXM, as:
> ../../../srcdir/libfabric/1.4.0/configure --prefix=/uufs/chpc.utah.edu/sys/installdir/libfabric/1.4.0 --enable-mxm=/uufs/chpc.utah.edu/sys/installdir/hpcx/v1.7.405-gcc-OFED-1.5.4.1-redhat7.2-x86_64/mxm
> 
> All built fine, the libfabric tests work, but, when building MPICH with the ch4:ofi device, the make was complaining about missing /libmxm.la. After some hunting, I have located the source of this in /uufs/chpc.utah.edu/sys/installdir/libfabric/1.4.0/lib/libfabric.la:
> 
> dependency_libs=' -L/uufs/chpc.utah.edu/sys/installdir/hpcx/v1.7.405-gcc-OFED-1.5.4.1-redhat7.2-x86_64/mxm/lib -lrdmacm -lnl-3 -lnl-route-3 -lpsm_infinipath  /libmxm.la -L/usr/lib64 -L/usr/lib -lm -lz -libverbs -lbfd -liberty -lrt -lpthread -ldl'
> 
> It looks like the libfabric build has not correctly expanded the full path to the libmxm.la.
> 
> Is this something I did incorrectly with the libfabric build, or something that needs to be fixed in the libfabric itself?
> 
> Thanks,
> MC
> 
> -- Martin Cuma
> Center for High Performance Computing
> Department of Geology and Geophysics
> University of Utah
> 


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