the package can be built with either slots of dev-libs/libnl and it magically selects the newer one, while the ebuild requests SLOT=1.1 dev-libs/libnl:1.1 checking for LIBNL... no checking for LIBNL... yes configure: nl: -lnl dev-libs/libnl:3 checking for LIBNL... yes checking for LIBNL_ROUTE3... yes configure: nl: -I/usr/include/libnl3 -I/usr/include/libnl3 -lnl-3 -lnl-route-3 -lnl-3
Yeah up to 0.9.12 it preferred the older one and I flipped the check for 0.9.13 but when I bumped 0.9.13 in the tree I forgot to fix the ebuild. Thanks for catching that. Fixed in CVS.
I'm not sure if this should come to new bug or this to reopen, but app-emulation/libvirt-0.9.13 cannot be build against dev-libs/libnl:3 only. On my system no other package depends on libnl:1.1 so it has been removed with packages cleanup. After that, libvirt no longer builds. Ïf I manually install back libnl:1.1, libvirt builds just ok. Build error is: In file included from libvirtd.c:50:0: ../src/util/virnetlink.h:30:27: fatal error: netlink/msg.h: No such file or directory compilation terminated I found mayby related bug: https://bugs.gentoo.org/show_bug.cgi?id=388659 where is the same problem mentioned.
