From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hunt/
Date: Sun, 20 Mar 2022 18:43:55 +0000 (UTC) [thread overview]
Message-ID: <1647801815.faabae38e4abd60e28073844bbd1e7885270dbdc.sam@gentoo> (raw)
commit: faabae38e4abd60e28073844bbd1e7885270dbdc
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 20 18:41:00 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 20 18:43:35 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=faabae38
net-analyzer/hunt: [QA] fix tc-get* quoting
This can cause build problems for e.g. 32-bit (gcc -m32 ...)
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-analyzer/hunt/hunt-1.5_p6_p1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net-analyzer/hunt/hunt-1.5_p6_p1.ebuild b/net-analyzer/hunt/hunt-1.5_p6_p1.ebuild
index 3790bdef6529..b31b315b3758 100644
--- a/net-analyzer/hunt/hunt-1.5_p6_p1.ebuild
+++ b/net-analyzer/hunt/hunt-1.5_p6_p1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -31,7 +31,7 @@ src_configure() {
src_compile() {
local target
for target in . tpserv; do
- emake CC=$(tc-getCC) LDFLAGS="${CFLAGS} ${LDFLAGS}" -C "${target}"
+ emake CC="$(tc-getCC)" LDFLAGS="${CFLAGS} ${LDFLAGS}" -C "${target}"
done
}
next reply other threads:[~2022-03-20 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 18:43 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-28 20:27 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hunt/ Arthur Zamarin
2025-06-23 1:44 Sam James
2020-11-27 0:59 Aaron Bauman
2020-11-27 0:07 Thomas Deutschmann
2016-01-14 7:32 Jeroen Roovers
2016-01-14 7:32 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=1647801815.faabae38e4abd60e28073844bbd1e7885270dbdc.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