From: Mark Brown <broonie@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Michal Marek <michal.lkml@markovi.net>,
Guenter Roeck <linux@roeck-us.net>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
kernel@collabora.com
Subject: Re: [PATCH RFC 1/1] kbuild: enable overriding the compiler using the environment
Date: Mon, 12 Aug 2019 18:14:44 +0100 [thread overview]
Message-ID: <20190812171444.GL4592@sirena.co.uk> (raw)
In-Reply-To: <CAK7LNAT6Yp3oemUxSst+htnmM-St8WmSv+UZ2x2XF23cw-kU-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Tue, Aug 13, 2019 at 01:37:14AM +0900, Masahiro Yamada wrote:
> On Fri, Aug 9, 2019 at 2:15 PM Nathan Chancellor
> > This is problematic because there is no way for CC, HOSTCC, and HOSTCXX
> > to be passed to make within scripts/kconfig/merge_config.sh.
> Is it so problematic?
> If you start from make, CC=clang and HOSTCC=clang are propagated to sub-make
> even via shell scripts such as merge_config.sh
> Only the problem I see is the situation where
> a user directly runs scripts/kconfig/merge_config.sh
> without using make as a start-point.
This is really a very common thing for testing infrastructure to do,
it'll combine a base defconfig with a fragment enabling extra stuff
either to directly cover that extra stuff or to ensure that
configuration options needed for testsuites get turned on.
> A user can wrap merge_config.sh with a simple Makefile
> if they want to override CC, HOSTCC, etc.
If we want to do that it seems sensible to provide that Makefile
upstream so there's a standard thing, it might also help people notice
that they need to do this and avoid getting surprised.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-12 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 21:06 [PATCH RFC 0/1] kbuild: enable overriding the compiler using the environment Guillaume Tucker
2019-08-08 21:06 ` [PATCH RFC 1/1] " Guillaume Tucker
2019-08-08 22:35 ` Mark Brown
2019-08-12 13:13 ` Guillaume Tucker
2019-08-08 22:42 ` Nick Desaulniers
2019-08-08 22:54 ` Mark Brown
2019-08-09 5:15 ` Nathan Chancellor
2019-08-12 13:33 ` Guillaume Tucker
2019-08-12 16:37 ` Masahiro Yamada
2019-08-12 17:14 ` Mark Brown [this message]
2019-08-12 17:33 ` Nick Desaulniers
2019-08-08 22:17 ` [PATCH RFC 0/1] " Mark Brown
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=20190812171444.GL4592@sirena.co.uk \
--to=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michal.lkml@markovi.net \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=yamada.masahiro@socionext.com \
/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