LKML Archive on
help / color / mirror / Atom feed
From: Masahiro Yamada <>
To: Nathan Chancellor <>
Cc: Nick Desaulniers <>,
	clang-built-linux <>,
	Michal Marek <>,
	Linux Kbuild mailing list <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH] kbuild: add script check for cross compilation utilities
Date: Sun, 12 May 2019 12:04:48 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20190511022458.GA7376@archlinux-i9>

On Sat, May 11, 2019 at 11:25 AM Nathan Chancellor
<> wrote:
> Few comments below but nothing major, this seems to work fine as is.
> On Thu, May 09, 2019 at 01:19:21PM -0700, 'Nick Desaulniers' via Clang Built Linux wrote:
> > When cross compiling via setting CROSS_COMPILE, if the prefixed tools
> > are not found, then the host utilities are often instead invoked, and
> > produce often difficult to understand errors.  This is most commonly the
> > case for developers new to cross compiling the kernel that have yet to
> > install the proper cross compilation toolchain. Rather than charge
> > headlong into a build that will fail obscurely, check that the tools
> > exist before starting to compile, and fail with a friendly error
> > message.
> This part of the commit message makes it sound like this is a generic
> problem when it is actually specific to clang. make will fail on its
> own when building with gcc if CROSS_COMPILE is not properly set (since
> gcc won't be found).
> On a side note, seems kind of odd that clang falls back to the host
> tools when a non-host --target argument is used... (how in the world is
> that expected to work?)

I agree.
Failure is much better than falling back to host tools.

Best Regards
Masahiro Yamada

  reply	other threads:[~2019-05-12  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 20:19 Nick Desaulniers
2019-05-11  2:24 ` Nathan Chancellor
2019-05-12  3:04   ` Masahiro Yamada [this message]
2019-05-13 18:04     ` Nick Desaulniers
2019-05-12  2:21 ` Masahiro Yamada

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] kbuild: add script check for cross compilation utilities' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).