From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>
Cc: Mark Brown <broonie@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com, linux-kbuild@vger.kernel.org,
kernel@collabora.com,
Guillaume Tucker <guillaume.tucker@collabora.com>
Subject: [PATCH RFC 0/1] kbuild: enable overriding the compiler using the environment
Date: Thu, 8 Aug 2019 23:06:51 +0200 [thread overview]
Message-ID: <cover.1565297255.git.guillaume.tucker@collabora.com> (raw)
When building with clang and there is no gcc available, running
merge_config.sh fails without this fix because it can't build
scripts/basic/fixdep with HOSTCC hard-coded to be gcc in the top-level
Makefile. This was discovered while trying to build big-endian arm64
kernels with clang for kernelci.org in a Docker container with only clang
as a host compiler.
While this fix seems like a very obvious thing to do, it's equally
surprising that it hasn't been done before. This is why I'm sending this
as an RFC; there may be a very good reason why the compiler variables
still need to be hard-coded with gcc in the top-level Makefile.
Guillaume Tucker (1):
kbuild: enable overriding the compiler using the environment
Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2019-08-08 21:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 21:06 Guillaume Tucker [this message]
2019-08-08 21:06 ` [PATCH RFC 1/1] kbuild: enable overriding the compiler using the environment 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
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=cover.1565297255.git.guillaume.tucker@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kernel@collabora.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michal.lkml@markovi.net \
--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