Hm, My version was to keep current strict dependency on libnl by default, so if there is no libnl then netsniff-ng & trafgen will be removed from build list, but make possible to skip this rule by --disable-libnl option. Now I am not sure there is a reason for --disable-libnl as if there is no libnl then netsniff-ng & trafgen will be added to build list, and will be compiled w/o libnl dependency..
So does --disable-libnl makes sense ? Regards, Vadim Kochan On Fri, Aug 5, 2016 at 12:31 PM, Vadim Kochan <vadi...@gmail.com> wrote: > Sorry for that copy'n'paste ... > > On Fri, Aug 5, 2016 at 12:29 PM, Tobias Klauser <tklau...@distanz.ch> wrote: >> On 2016-08-04 at 18:30:20 +0200, Vadim Kochan <vadi...@gmail.com> wrote: >>> Add command line parsing function which allows to compile tools >>> (trafgen, netsniff-ng) without libnl-xxx libraries. >> >> But it does in its current state not allow to compile >> netsniff-ng/trafgen without libnl if libnl is not installed (i.e. not >> found by check_libnl). >> >> I rewrote this patch to support this case and make it more in line with >> the existing library checking/disabling. >> >> Thanks! -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to netsniff-ng+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
