On Fri, Jun 01, 2018 at 05:20:12PM +0200, Arnd Bergmann wrote: > On Thu, May 31, 2018 at 3:42 AM, Masahiro Yamada > <yamada.masahiro@xxxxxxxxxxxxx> wrote: > > 2018-05-31 0:17 GMT+09:00 Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx>: > >> 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) > > > > > > ARCH ?= $(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. that's a great idea. Let's do that. > Don't we already do something like that for tools/testing/selftest which > also needs to generate binaries with CC? I couldn't find such makefile magic. Can you please help me with this? -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
