Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Federico Pellegrin <fede@evolware.org>
Cc: buildroot@buildroot.org,  joris.lijssens@gmail.com
Subject: Re: [Buildroot] [PATCH 1/1] package/netsniff-ng: bump to 0.6.9
Date: Fri, 18 Jul 2025 11:49:21 +0300	[thread overview]
Message-ID: <87fretlw8e.fsf@tarshish> (raw)
In-Reply-To: <20250718050954.18325-1-fede@evolware.org> (Federico Pellegrin's message of "Fri, 18 Jul 2025 07:09:54 +0200")

Hi Federico,

On Fri, Jul 18 2025, Federico Pellegrin wrote:
> Changes: https://github.com/netsniff-ng/netsniff-ng/releases/tag/v0.6.9
>
> Remove now upstreamed patch 0001-Detect-libpcap-dependencies-using-pkg-config.patch.
> Fixes also: https://patchwork-proxy.ozlabs.org/project/buildroot/patch/20240829075015.39164-1-fede@evolware.org/

With this patch removed, .checkpackageignore should also be updated.

baruch

> Signed-off-by: Federico Pellegrin <fede@evolware.org>
> ---
>  ...ibpcap-dependencies-using-pkg-config.patch | 51 -------------------
>  package/netsniff-ng/netsniff-ng.hash          |  2 +-
>  package/netsniff-ng/netsniff-ng.mk            |  2 +-
>  3 files changed, 2 insertions(+), 53 deletions(-)
>  delete mode 100644 package/netsniff-ng/0001-Detect-libpcap-dependencies-using-pkg-config.patch
>
> diff --git
> a/package/netsniff-ng/0001-Detect-libpcap-dependencies-using-pkg-config.patch
> b/package/netsniff-ng/0001-Detect-libpcap-dependencies-using-pkg-config.patch
> deleted file mode 100644
> index bbcbd2bfc3..0000000000
> --- a/package/netsniff-ng/0001-Detect-libpcap-dependencies-using-pkg-config.patch
> +++ /dev/null
> @@ -1,51 +0,0 @@
> -From 194ec61843b9598ce90873c812b817c4b96e2e0d Mon Sep 17 00:00:00 2001
> -From: Baruch Siach <baruch@tkos.co.il>
> -Date: Thu, 2 Sep 2021 12:56:00 +0300
> -Subject: [PATCH] Detect libpcap dependencies using pkg-config
> -
> -When building statically the link command line must include all
> -dependencies of all libraries. libpcap can optionally depend on libnl.
> -mausezahn can't build statically in this case.
> -
> -Use pkg-config in configure and in the link command to construct the
> -library flags we need to link with libpcap.
> -
> -Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> -Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> ----
> -Upstream status: commit 194ec61843b9598ce90873c812b817c4b96e2e0d
> -
> - configure          | 4 +++-
> - mausezahn/Makefile | 2 +-
> - 2 files changed, 4 insertions(+), 2 deletions(-)
> -
> -diff --git a/configure b/configure
> -index 510826a798f5..598ae2433a7a 100755
> ---- a/configure
> -+++ b/configure
> -@@ -588,7 +588,9 @@ int main(void)
> - }
> - EOF
> - 
> --	$CC -o $TMPDIR/pcaptest $TMPDIR/pcaptest.c -lpcap >> config.log 2>&1
> -+	$CC -o $TMPDIR/pcaptest $TMPDIR/pcaptest.c \
> -+		$($PKG_CONFIG --libs libpcap 2>> config.log) \
> -+		>> config.log 2>&1
> - 	if [ ! -x $TMPDIR/pcaptest ] ; then
> - 		echo "[NO]"
> - 		echo "CONFIG_LIBPCAP=0" >> Config
> -diff --git a/mausezahn/Makefile b/mausezahn/Makefile
> -index ca16b6579583..9544565355cc 100644
> ---- a/mausezahn/Makefile
> -+++ b/mausezahn/Makefile
> -@@ -1,6 +1,6 @@
> - mausezahn-libs =	-lcli \
> - 			-lnet \
> --			-lpcap \
> -+			$(shell PKG_CONFIG_PATH=$(PKG_CONFIG_PATH) $(PKG_CONFIG) --libs libpcap 2> /dev/null ) \
> - 			-lrt \
> - 			-lpthread \
> - 			-lm
> --- 
> -2.33.0
> -
> diff --git a/package/netsniff-ng/netsniff-ng.hash b/package/netsniff-ng/netsniff-ng.hash
> index 40b015cb0d..e63963c6d7 100644
> --- a/package/netsniff-ng/netsniff-ng.hash
> +++ b/package/netsniff-ng/netsniff-ng.hash
> @@ -1,5 +1,5 @@
>  # Locally calculated after checking signature
> -sha256  77d17d4158faf1d93c7d922a1bd7f093a8b437bd658292c830708540e10894ba  netsniff-ng-0.6.8.tar.xz
> +sha256  027840fa3c4e11abfe4fd0fffe9909c5c4ed1428d4b9397fb6d2f5ea69325918  netsniff-ng-0.6.9.tar.xz
>  # Locally computed
>  sha256  b353349ba51e0d4b59cf2f188f0c285296e154ce8c58954bc5e0dc0282a4db2d  README
>  sha256  8f6d85366f3763557d6ddd0637988b9ba11edef354e3c9302fff4262a235c387  COPYING
> diff --git a/package/netsniff-ng/netsniff-ng.mk b/package/netsniff-ng/netsniff-ng.mk
> index 2b5b19b27f..5e779f1cfb 100644
> --- a/package/netsniff-ng/netsniff-ng.mk
> +++ b/package/netsniff-ng/netsniff-ng.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -NETSNIFF_NG_VERSION = 0.6.8
> +NETSNIFF_NG_VERSION = 0.6.9
>  NETSNIFF_NG_SITE = http://pub.netsniff-ng.org/netsniff-ng
>  NETSNIFF_NG_SOURCE = netsniff-ng-$(NETSNIFF_NG_VERSION).tar.xz
>  NETSNIFF_NG_LICENSE = GPL-2.0

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-18  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  5:09 [Buildroot] [PATCH 1/1] package/netsniff-ng: bump to 0.6.9 Federico Pellegrin
2025-07-18  8:49 ` Baruch Siach via buildroot [this message]
2025-07-18  8:56   ` Federico Pellegrin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fretlw8e.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=fede@evolware.org \
    --cc=joris.lijssens@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox