Re: upcoming tcpslice release

[Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Guy Harris <gharris () sonic net>
>
> Date: Sat, 15 Oct 2022 15:21:42 -0700
>
> On Oct 15, 2022, at 8:03 AM, Denis Ovsienko via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:
>
> > As it turns out, on Linux tcpslice currently fails to build with the
> > current master branch of libpcap.  This reproduces in all Linux CI
> > builds and also on my Ubuntu 20.04 PC.  The root cause seems to be in
> > libpcap via pcap-config:
> >
> > /usr/bin/ld: cannot find -lsystemd
> > clang: error: linker command failed with exit code 1 (use -v to see invocation)
> >
> > LIBS='../libpcap/libpcap.a -lnl-genl-3 -lnl-3  -ldbus-1 -lpthread -lsystemd  '
>
> Fixed in
>
> commit 588f0bb996230a84a8cf10ddf30cc514e3ba5a68 (HEAD -> master, origin/master, origin/HEAD)
> Author: Guy Harris <gharris () sonic net>
> Date:   Sat Oct 15 15:18:13 2022 -0700
>
>     configure: use pcap-config --static-pcap-only if available.
>     
>     If we're linking with a libpcap in ../libpcap*, it's static, but we only
>     need to link with the libraries on wich it immediately depends, we don't
>     need to link with the libraries on which those libraries depend, etc..
>     
>     So, if ../libpcap*/pcap-config supports --static-pcap-only, use that.
>     
>     Regenerate configure script.
>
> This should only be an issue for programs that link statically with libpcap (libpcap.a) but don't link completely 
> statically.  I don't know if anything does that other than tcpdump (from which this change was taken) and tcpslice, if 
> they're building with a libpcap.a from a libpcap source and build tree in the same parent directory as the 
> tcpdump/tcpslice source and build tree.
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers