From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/crossdev:master commit in: wrappers/etc/portage/
Date: Wed, 27 Oct 2021 08:55:20 +0000 (UTC) [thread overview]
Message-ID: <1635324742.9ecff85d0909d3e576b1388b48da03cfc824516b.vapier@gentoo> (raw)
commit: 9ecff85d0909d3e576b1388b48da03cfc824516b
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 27 08:52:22 2021 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Wed Oct 27 08:52:22 2021 +0000
URL: https://gitweb.gentoo.org/proj/crossdev.git/commit/?id=9ecff85d
wrappers: drop HOSTCC setting
This is a bit obsolete. Few packages every used this setting, and
toolchain-funcs.eclass provides a suite of BUILD_xxx helpers that
ebuilds can leverage directly.
Closes: https://bugs.gentoo.org/727900
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
wrappers/etc/portage/make.conf | 2 --
1 file changed, 2 deletions(-)
diff --git a/wrappers/etc/portage/make.conf b/wrappers/etc/portage/make.conf
index eac5138..2ab65b3 100644
--- a/wrappers/etc/portage/make.conf
+++ b/wrappers/etc/portage/make.conf
@@ -5,8 +5,6 @@
CHOST=__CHOST__
CBUILD=__CBUILD__
-HOSTCC=${CBUILD}-gcc
-
ROOT=@GENTOO_PORTAGE_EPREFIX@/usr/${CHOST}/
ACCEPT_KEYWORDS="${ARCH} ~${ARCH}"
next reply other threads:[~2021-10-27 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:55 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-21 21:06 [gentoo-commits] proj/crossdev:master commit in: wrappers/etc/portage/ James Le Cuirot
2024-09-21 21:06 James Le Cuirot
2023-12-12 22:02 James Le Cuirot
2022-09-09 4:32 Sam James
2022-06-17 2:44 Sam James
2022-06-17 2:44 Sam James
2014-01-18 19:37 Mike Frysinger
2012-08-21 16:24 Mike Frysinger
2012-03-07 18:31 Mike Frysinger
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=1635324742.9ecff85d0909d3e576b1388b48da03cfc824516b.vapier@gentoo \
--to=vapier@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