On Feb 16, 2014, at 10:58 AM, François-Xavier Le Bail <fx.leb...@yahoo.com> 
wrote:

>> From: Guy Harris <g...@alum.mit.edu>
> 
>> On Feb 15, 2014, at 1:21 PM, Michael Richardson <m...@sandelman.ca> wrote:
>> 
>>> The ESP tests are failing because you haven't got libssl-dev.
>> 
>> Yes - some tests fail if the full set of support libraries weren't available 
>> when tcpdump was built.
>> 
>> Perhaps we want to suppress some tests if we don't have the appropriate 
>> libraries - or have the tests compare against the results of a tcpdump built 
>> without the library or libraries in question rather than the results of one 
>> built with them.
> 
> 
> We could maybe add a text in INSTALL file, like:
> 
> diff --git a/INSTALL.txt b/INSTALL.txt
> index 132e118..4dc61d3 100644
> --- a/INSTALL.txt
> +++ b/INSTALL.txt
> @@ -9,6 +9,9 @@ You will need an ANSI C compiler to build tcpdump. The 
> configure
>  will abort if your compiler is not ANSI compliant. If this happens, use
>  the generally available GNU C compiler (GCC).
>  
> +To build with crypto support, you need SSL library (libssl-dev).
> +If you don't have this library, you will have some "make check" errors.

Denis appears to have fixed that with

        commit 9e2042ebe86c41d373930dbd89b56a6a2f06fcf0
        Author: Denis Ovsienko <infrastat...@yandex.ru>
        Date:   Mon Feb 17 00:22:37 2014 +0400

            make OpenSSL-specific tests conditional

That still leaves the NFLOG tests; that requires looking for DLT_NFLOG in the 
version of libpcap being used to build tcpdump, which would be a bit more work.

An alternative might be to have the configure script run a test for DLT_NFLOG 
and somehow do something to make "make check" skip the NFLOG test.  A 
generalization might be to have some support for "if ... end" in the 
tests/TESTLIST file, with the tests checking some name specified in a file, and 
have the configure script add entries to that file as necessary.
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Reply via email to