>
> When using libnl-3.0 we need to link with libnl-genl also, if not, we
> get a lot of undefined symbols.
> ---
> has_libnl_ver=0
> PKG_CHECK_MODULES([LIBNL], [libnl-1], [has_libnl_ver=1], [
> - AC_SEARCH_LIBS([nl_socket_alloc], [nl], [has_libnl_ver=2], [
> + AC_SEARCH_LIBS([nl_socket_alloc], [libnl-2.0],
> [has_libnl_ver=2], [
>
> are you sure you want the linker to check for -llibnl-2.0? that means
> it's going to try to find a "liblibnl-2.0.so
<
http://liblibnl-2.0.so>"
> (note the double "lib" here).
this autoconf stuff is giving me a headache
maybe we should ask the libnl guys if they have some snippet that they
recommend.... after all I doubt we're the only ones dealing with their
library.
libnl2 always has nl_socket_alloc, does it not? Why check for it?
(Why even bother with libnl1 and libnl2 anyway? They are obsolete.)