On 4/2/24 13:40, Craig Small wrote:
On Wed, 3 Apr 2024 at 02:19, Bart Van Assche <bvanass...@acm.org> wrote:
Can you please check the configure script logs to see why libnl-3 was
not detected?
libnl-3 was detected:
configure:27875: $PKG_CONFIG --exists --print-errors "libnl-3.0"
configure:27878: $? = 0
configure:27936: result: yes
But libnl-route-3.0 was not:
configure:27942: $PKG_CONFIG --exists --print-errors "libnl-route-3.0"
Package libnl-route-3.0 was not found in the pkg-config search path.
I added libnl-route-3-dev and it compiled ok.
There's something not quite right with the configure script, because
it evaluates
libnl-3 + !libnl-route-3 = libnl1
instead of failing.
Something else must be going on. This is the code from configure.ac that
checks for libnl-3:
if test "x$ac_cv_header_netlink_netlink_h" = xyes; then
AC_EGREP_HEADER([nl_socket_free], [netlink/socket.h],
[AC_DEFINE([HAVE_LIBNL3], [1],
[Define to 1 if <netlink/netlink.h>
provides the
libnl3 API])])
fi
Thanks,
Bart.
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
