From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: James Beddek <telans@posteo.de>,
Andrew Savchenko <bircoph@gentoo.org>,
Manoj Gupta <manojgupta@chromium.org>
Subject: Re: [gentoo-dev] [PATCH v3] kernel-2.eclass: Respect portage toolchain variables
Date: Tue, 4 Jan 2022 23:25:34 +0000 [thread overview]
Message-ID: <4CC4B716-65A7-44C0-B7F0-D3C4E5E42C2F@gentoo.org> (raw)
In-Reply-To: <CAJ0EP42NtVKzr0DHC96gfm7bK5DFrcdMoT-rh_o4YUoZwbw4xQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]
> On 3 Jan 2022, at 18:23, Mike Gilbert <floppym@gentoo.org> wrote:
> On Mon, Jan 3, 2022 at 12:49 PM Adrian Ratiu <adrian.ratiu@collabora.com <mailto:adrian.ratiu@collabora.com>> wrote:
>>
>> Starting with kernel>=v5.7 the build system can override the
>> tools vars by setting LLVM=1 [1], but older kernels still use
>> the default GNU tools, so to be able to use a full LLVM/Clang
>> build, CC & co should be set to their respective portage values.
>>
>> [1] a0d1c951ef08 kbuild: support LLVM=1 to switch the default tools to Clang/LLVM
>>
>> Co-authored-by: Manoj Gupta <manojgupta@chromium.org>
>> Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
>> [snip]
>
> This seems ok to me, at least given the way the eclass currently works.
>
> At some point, we should really convert xmakeopts into an array. Any
> of these variables might contain spaces, and that would break the
> current implementation.
agreed, but lgtm
[-- Attachment #1.2: Type: text/html, Size: 6676 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2022-01-04 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 17:49 [gentoo-dev] [PATCH v3] kernel-2.eclass: Respect portage toolchain variables Adrian Ratiu
2022-01-03 18:23 ` Mike Gilbert
2022-01-04 23:25 ` Sam James [this message]
2022-01-04 23:31 ` Mike
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=4CC4B716-65A7-44C0-B7F0-D3C4E5E42C2F@gentoo.org \
--to=sam@gentoo.org \
--cc=bircoph@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=manojgupta@chromium.org \
--cc=telans@posteo.de \
/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