From: Manoj Gupta <manojgupta@google.com>
To: gentoo-dev@lists.gentoo.org
Cc: Sergei Trofimovich <slyfox@gentoo.org>, kernel@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] kernel-2.eclass: use $(CC) as HOSTCC, bug #725878
Date: Sat, 30 May 2020 09:59:16 -0700 [thread overview]
Message-ID: <CAH=QcsjzkUPq9fNuqX6=xaU5-VbwWZ=tVegtiw7MLKVfHaEruQ@mail.gmail.com> (raw)
In-Reply-To: <20200530122336.3560258-1-slyfox@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Also see https://bugs.chromium.org/p/chromium/issues/detail?id=1088210 on
Chrome OS.
Verified that this fixes the linux-headers build issue when gcc links are
not installed.
Thanks,
Manoj
On Sat, May 30, 2020 at 5:24 AM Sergei Trofimovich <slyfox@gentoo.org>
wrote:
> Before the change HOSTCC always used gcc. This was
> detected by Agostino on linux-headers package.
>
> After the change HOSTCC uses user-specified CC
> (or BUILD_CC). Tested on native linux-headers
> and on cross-*/linux-headers.
>
> CC: kernel@gentoo.org
> Reported-by: Agostino Sarubbo
> https://bugs.gentoo.org/725878
> Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
> ---
> eclass/kernel-2.eclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/eclass/kernel-2.eclass b/eclass/kernel-2.eclass
> index 930bcf22e29..04edee33930 100644
> --- a/eclass/kernel-2.eclass
> +++ b/eclass/kernel-2.eclass
> @@ -712,6 +712,7 @@ env_setup_xmakeopts() {
> elif type -p ${CHOST}-ar > /dev/null ; then
> xmakeopts="${xmakeopts} CROSS_COMPILE=${CHOST}-"
> fi
> + xmakeopts="${xmakeopts} HOSTCC=$(tc-getBUILD_CC)"
> export xmakeopts
> }
>
> --
> 2.26.2
>
>
>
[-- Attachment #2: Type: text/html, Size: 1938 bytes --]
next prev parent reply other threads:[~2020-05-30 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 12:23 [gentoo-dev] [PATCH] kernel-2.eclass: use $(CC) as HOSTCC, bug #725878 Sergei Trofimovich
2020-05-30 16:59 ` Manoj Gupta [this message]
2020-06-03 7:57 ` Sergei Trofimovich
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='CAH=QcsjzkUPq9fNuqX6=xaU5-VbwWZ=tVegtiw7MLKVfHaEruQ@mail.gmail.com' \
--to=manojgupta@google.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kernel@gentoo.org \
--cc=slyfox@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