public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christoph Junghans" <junghans@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/nawk/
Date: Fri,  2 Dec 2022 15:18:25 +0000 (UTC)	[thread overview]
Message-ID: <1669994298.d34150a8ad5a986519809b2e8e4c15ba04ef9464.junghans@gentoo> (raw)

commit:     d34150a8ad5a986519809b2e8e4c15ba04ef9464
Author:     Christoph Junghans <junghans <AT> gentoo <DOT> org>
AuthorDate: Fri Dec  2 15:17:38 2022 +0000
Commit:     Christoph Junghans <junghans <AT> gentoo <DOT> org>
CommitDate: Fri Dec  2 15:18:18 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d34150a8

sys-apps/nawk: fix CC usage

Closes: https://bugs.gentoo.org/243502
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Christoph Junghans <junghans <AT> gentoo.org>

 sys-apps/nawk/nawk-20220122-r1.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sys-apps/nawk/nawk-20220122-r1.ebuild b/sys-apps/nawk/nawk-20220122-r1.ebuild
index c133bc9a1ac9..34f6cf9af4a1 100644
--- a/sys-apps/nawk/nawk-20220122-r1.ebuild
+++ b/sys-apps/nawk/nawk-20220122-r1.ebuild
@@ -24,6 +24,7 @@ DOCS=( README.md FIXES )
 src_compile() {
 	emake \
 		CC="$(tc-getCC)" \
+		HOSTCC="$(tc-getBUILD_CC)" \
 		CFLAGS="${CFLAGS}" \
 		CPPFLAGS=-DHAS_ISBLANK \
 		ALLOC="${LDFLAGS}" \


             reply	other threads:[~2022-12-02 15:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 15:18 Christoph Junghans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-24  4:45 [gentoo-commits] repo/gentoo:master commit in: sys-apps/nawk/ Sam James
2025-03-13  3:15 Sam James
2025-03-13  3:15 Sam James
2025-03-13  1:28 Sam James
2025-03-13  1:24 Sam James
2025-03-13  1:21 Sam James
2025-03-13  1:21 Sam James
2025-03-13  1:09 Sam James
2025-02-09  5:18 Sam James
2025-02-09  5:18 Sam James
2023-12-28  4:15 Sam James
2023-10-27 12:17 Sam James
2023-10-23 14:05 Arthur Zamarin
2023-10-22 11:44 Sam James
2023-10-22 11:40 Sam James
2023-10-22 11:39 Sam James
2023-10-22 11:39 Sam James
2023-10-22 11:39 Sam James
2023-10-22 11:39 Sam James
2023-09-12  2:23 Sam James
2023-02-13  3:41 Matt Turner
2022-12-27 19:53 Sam James
2022-12-27 19:45 Sam James
2022-12-27 13:40 Sam James
2022-12-27 11:31 Sam James
2022-12-24  3:02 WANG Xuerui
2022-12-18 11:45 James Le Cuirot
2022-12-18  1:50 Yixun Lan
2022-12-16 21:19 Arthur Zamarin
2022-12-16 21:19 Arthur Zamarin
2022-12-16 21:19 Arthur Zamarin
2022-12-16 18:26 Arthur Zamarin
2022-12-16  7:53 Sam James
2022-12-01 19:41 Sam James
2022-12-01 19:38 Sam James
2022-12-01 18:11 Christoph Junghans
2022-12-01 17:58 Christoph Junghans
2021-05-22 17:20 David Seifert
2021-01-06 15:26 Fabian Groffen
2020-05-06 17:25 Michał Górny
2018-02-19 19:58 Christoph Junghans
2016-11-14  2:01 Christoph Junghans

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=1669994298.d34150a8ad5a986519809b2e8e4c15ba04ef9464.junghans@gentoo \
    --to=junghans@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