public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nfdump/
Date: Thu, 23 Jun 2022 04:47:27 +0000 (UTC)	[thread overview]
Message-ID: <1655959615.ce9cf468b74854dd0d12f3647c509b7e3700b179.sam@gentoo> (raw)

commit:     ce9cf468b74854dd0d12f3647c509b7e3700b179
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 23 04:45:27 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 23 04:46:55 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce9cf468

net-analyzer/nfdump: fix build on musl

Closes: https://bugs.gentoo.org/853763
Thanks-to: CFuga <cfuga <AT> cfuga.mx>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-analyzer/nfdump/nfdump-1.6.24.ebuild | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/net-analyzer/nfdump/nfdump-1.6.24.ebuild b/net-analyzer/nfdump/nfdump-1.6.24.ebuild
index abe553c93b29..db24ffe43a66 100644
--- a/net-analyzer/nfdump/nfdump-1.6.24.ebuild
+++ b/net-analyzer/nfdump/nfdump-1.6.24.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=8
 
-inherit autotools toolchain-funcs
+inherit autotools flag-o-matic toolchain-funcs
 
 DESCRIPTION="A set of tools to collect and process netflow data"
 HOMEPAGE="https://github.com/phaag/nfdump"
@@ -19,6 +19,7 @@ REQUIRED_USE="?? ( jnat nsel )"
 RDEPEND="
 	app-arch/bzip2
 	sys-libs/zlib
+	elibc_musl? ( sys-libs/fts-standalone )
 	ftconv? ( net-analyzer/flow-tools )
 	nfpcapd? ( net-libs/libpcap )
 	nfprofile? ( net-analyzer/rrdtool )
@@ -54,6 +55,9 @@ src_prepare() {
 src_configure() {
 	tc-export CC
 
+	# bug #853763
+	use elibc_musl && append-libs "-lfts"
+
 	# --without-ftconf is not handled well, bug #322201
 	econf \
 		$(use ftconv && echo "--enable-ftconv --with-ftpath=/usr") \


             reply	other threads:[~2022-06-23  4:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  4:47 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 18:54 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nfdump/ Arthur Zamarin
2024-12-25  1:48 Sam James
2024-11-25 21:56 Sam James
2024-11-25 21:56 Sam James
2024-11-14 18:41 Sam James
2024-11-14  3:17 Sam James
2024-02-27 22:06 Sam James
2023-06-01  5:23 Sam James
2023-05-01 13:19 Sam James
2023-04-23 17:57 Sam James
2022-10-31 16:41 Agostino Sarubbo
2022-10-01  0:34 Sam James
2022-06-23  6:45 Agostino Sarubbo
2022-06-23  5:58 Agostino Sarubbo
2022-04-13  1:48 Sam James
2022-03-24 23:58 Sam James
2021-08-11  0:02 Sam James
2021-05-28  2:27 Sam James
2021-05-28  1:22 Sam James
2021-04-18 21:27 Sam James
2021-04-18 21:20 Sam James
2021-03-27 16:11 Sam James
2021-03-27 16:07 Sam James
2021-03-27 16:06 Sam James
2021-03-27 16:02 Sam James
2021-03-27 15:35 Sam James
2021-03-15 21:12 Sam James
2021-03-15 21:12 Sam James
2021-03-15 21:09 Sam James
2021-03-15 21:01 Sam James
2020-08-02 10:43 Jeroen Roovers
2020-03-29 12:38 Jeroen Roovers
2020-03-12 16:26 Agostino Sarubbo
2020-03-12 16:21 Agostino Sarubbo
2017-05-29  8:30 Jeroen Roovers
2016-06-15  9:13 Jeroen Roovers
2016-05-14 22:23 Agostino Sarubbo
2016-05-14 22:22 Agostino Sarubbo
2016-05-12 16:39 Jeroen Roovers

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=1655959615.ce9cf468b74854dd0d12f3647c509b7e3700b179.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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