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: Mon, 25 Nov 2024 21:56:42 +0000 (UTC)	[thread overview]
Message-ID: <1732571594.18d02c7487b2e450ec468a57a2657f5dc252760b.sam@gentoo> (raw)

commit:     18d02c7487b2e450ec468a57a2657f5dc252760b
Author:     Cristian Othón Martínez Vera <cfuga <AT> cfuga <DOT> mx>
AuthorDate: Mon Nov 25 18:30:34 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Nov 25 21:53:14 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18d02c74

net-analyzer/nfdump: eprexify paths for configure script

Signed-off-by: Cristian Othón Martínez Vera <cfuga <AT> cfuga.mx>
Closes: https://github.com/gentoo/gentoo/pull/39401
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-analyzer/nfdump/nfdump-1.7.4.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net-analyzer/nfdump/nfdump-1.7.4.ebuild b/net-analyzer/nfdump/nfdump-1.7.4.ebuild
index 9ba85b7fd6b2..ef05ba0e4b6a 100644
--- a/net-analyzer/nfdump/nfdump-1.7.4.ebuild
+++ b/net-analyzer/nfdump/nfdump-1.7.4.ebuild
@@ -67,7 +67,7 @@ src_configure() {
 
 	# --without-ftconf is not handled well, bug #322201
 	local myeconfargs=(
-		$(usex ftconv "--enable-ftconv --with-ftpath=/usr")
+		$(usex ftconv "--enable-ftconv --with-ftpath=${EPREFIX}/usr")
 		$(usex nfpcapd --enable-nfpcapd)
 		$(usex nfprofile --enable-nfprofile)
 		$(usex nftrack --enable-nftrack)
@@ -76,7 +76,7 @@ src_configure() {
 		$(use_enable nsel)
 		$(use_enable readpcap)
 		$(use_enable sflow)
-		$(use_with zstd "zstdpath=/usr")
+		$(use_with zstd "zstdpath=${EPREFIX}/usr")
 	)
 	econf "${myeconfargs[@]}"
 }


             reply	other threads:[~2024-11-25 21:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 21:56 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-19  2:17 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nfdump/ Sam James
2025-03-08 18:54 Arthur Zamarin
2024-12-25  1:48 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-06-23  4:47 Sam James
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=1732571594.18d02c7487b2e450ec468a57a2657f5dc252760b.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