* Checking dynamic linking consistency [ 3% ] * broken /sbin/crda (requires libnl-3.so.200 libnl-genl-3.so.200) [ 100% ] Please change dep to libnl:3 or add USE.
Confirmed here to : when libnl:3 is present on the system, crda links against libnl:3, not libnl:1. Looking at the makefile, it seems that it automatically links against the highest libnl version. # ldd /sbin/crda linux-vdso.so.1 (0x0000034bfd36b000) libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x0000034bfcd7f000) libnl-genl-3.so.200 => /usr/lib64/libnl-genl-3.so.200 (0x0000034bfcb7a000) libnl-3.so.200 => /usr/lib64/libnl-3.so.200 (0x0000034bfc960000) libc.so.6 => /lib64/libc.so.6 (0x0000034bfc5be000) libdl.so.2 => /lib64/libdl.so.2 (0x0000034bfc3ba000) libz.so.1 => /lib64/libz.so.1 (0x0000034bfc1a4000) libpthread.so.0 => /lib64/libpthread.so.0 (0x0000034bfbf88000) libm.so.6 => /lib64/libm.so.6 (0x0000034bfbc97000) /lib64/ld-linux-x86-64.so.2 (0x0000034bfd14c000) So the libnl depend should probably be adjusted (to no version, like net-wireless/iw ?). Otherwise, it should be patched to depend explicitly on a specific libnl version. This should be easy, commenting libnl version on lines 48,49,50 of the Makefile to block version detection : https://github.com/mcgrof/crda/blob/master/Makefile
Fixed, now it depends on dev-libs/libnl, not dev-libs/libnl:1.1
That doesn't really fix the bug - crda is still linking against the latest installed SLOT. It just makes portage pull libnl:3 into the dependency graph even if crda was already built against libnl:1. You might as well just depend on dev-libs/libnl:3 if you're going to force everyone to install it anyway.
(In reply to comment #3) > You might as well just depend on dev-libs/libnl:3 if you're going to force > everyone to install it anyway. This would be particularly useful since dev-libs/libnl:3 is actively maintained upstream, whereas dev-libs/libnl:1 hasn't been for a long time.
Fixed, 1.1.2-r4 now depends on libnl:3 instead of just libnl.
