LKML Archive on
help / color / mirror / Atom feed
From: Arnd Bergmann <>
To: Masahiro Yamada <>
Cc: Alexei Starovoitov <>,
	"David S. Miller" <>,
	Alexei Starovoitov <>,
	Linux Kbuild mailing list <>,
	Networking <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH] [net-next, wrong] make BPFILTER_UMH depend on X86
Date: Fri, 1 Jun 2018 17:20:12 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 31, 2018 at 3:42 AM, Masahiro Yamada
<> wrote:
> 2018-05-31 0:17 GMT+09:00 Alexei Starovoitov <>:
>> On Mon, May 28, 2018 at 05:31:01PM +0200, Arnd Bergmann wrote:

> Hmm.
> For cross-compiling, we set 'ARCH' via the environment variable or the
> command line.
> ARCH is not explicitly set, the top-level Makefile sets it to $(SUBARCH)
> Maybe, we can assume the native build if $(ARCH) and $(SUBARCH) are the same?

SUBARCH is also used with a special meaning for arch/um where we build
with ARCH=um SUBARCH=x86, either on native (x86) or cross builds.

So doing that would still work in most but not all cases.

What is the reason for using HOSTCC rather than CC anyway? I think
the correct way to do this would be to check if CC is able to link binaries
and disallow the option if it's not.

Don't we already do something like that for tools/testing/selftest which
also needs to generate binaries with CC?


  reply	other threads:[~2018-06-01 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 15:31 Arnd Bergmann
2018-05-30 15:17 ` Alexei Starovoitov
2018-05-31  1:42   ` Masahiro Yamada
2018-06-01 15:20     ` Arnd Bergmann [this message]
2018-06-04 23:51       ` Alexei Starovoitov
2018-06-08  8:57 ` Geert Uytterhoeven
2018-06-08  9:33   ` Daniel Borkmann
2018-06-08  9:40     ` Geert Uytterhoeven

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] [net-next, wrong] make BPFILTER_UMH depend on X86' \

* 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).