[lkml]   [2018]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: defconfig fails if CROSS_COMPILE is set while cross-gcc is not avaialble
Hi Masahiro,

On Wed, 2018-09-12 at 21:53 +0900, Masahiro Yamada wrote:
> Hi Alexey.
> 2018-09-12 21:08 GMT+09:00 Alexey Brodkin <>:
> > Hello Masahiro-san,
> >
> > Starting from kernel v4.17 it is no longer possible to install kernel headers
> > for ARC architecture if there's no cross-toolchain in PATH.
> Really?
> I can do 'make ARCH=arc headers_install'
> with the latest Linus' tree.

Indeed "headers_install" works that way but is it OK to install headers
without previous configuration. In my experiment I don't see any differences
though for example OpenEmbedded on configuration step of "linux-libc-headers"
do "ARCH=xxx make allnoconfig", see

That might be some legacy but I'm not really sure,
worth asking OE people.

For the record in Buildroot no configuration happens for Linux headers,

> I see the following warnings, but possible to install kernel headers.
> ./scripts/ line 26: arc-linux-gcc: command not found
> ./scripts/ line 27: arc-linux-gcc: command not found

Right... that happens because we're doing 2 hackish things:
1. Checking if current toolchain is configured for ARCompact (ARCv1) ISA
or ARCv2. That's because we use toolchain's libgcc and so we want to warn
a user if wrong toolchain is used early instead of leaving him to deal with
final linkage failure.

2. Asking CC for a path to libgcc


> I am trying to fix even those warnings
> by eliminating unneeded compiler invocation. It is WIP.

And if (1) is not super important (in fact we used to live without it for years)
(2) requires implementation of libgcc in kernel sources (which BTW will make (1)
obsolete immediately). We do have it on our todo list though...


> > That doesn't happen for ARM and other arches simply because for ARC
> > we define CROSS_COMPILE if it is not set by user, see:
> >
> I do not think it is a good practice
> to forcibly set CROSS_COMPILE that users may not have.

Maybe so. Still some arches or random platforms do that.

> arch/m68k/Makefile uses cc-cross-prefix helper
> to set the first found compiler.

Well I'm not really sure we need to mess with CROSS_COMPILE in kernel.
I.e. there might be tons of variations depending on who toolchain was built
etc. So I'd better get rid of CROSS_COMPILE setup in our Makefile.

> > Still if CROSS_COMPILE is set before execution of "make defconfig"
> > then the same problem happens for others.
> >
> > I was able to find a series of commits which cause this problem,
> > here they are:
> > ----------------------------->8--------------------------
> > 59f53855babf - gcc-plugins: test plugin support in Kconfig and clean up Makefile
> > 469cb7376c06 - kconfig: add CC_IS_CLANG and CLANG_VERSION
> > a4353898980c - kconfig: add CC_IS_GCC and GCC_VERSION
> > ----------------------------->8--------------------------
> >
> > What happen is "$(CC)" is passed as an argument and in its turn CC is
> > "$(CROSS_COMPILE)gcc", see:
> >
> >
> >
> > So if I substitute "CC" with "HOSTCC" in a couple of places (see below)
> > the problem goes away. But I'm not really sure if what I do is correct.
> > I.e. when we're interested in CC for target and when only host CC is of
> > our interest.
> I think the log of commit 316d55d55f49eca44
> is a good source to know the background of this change.
> Now Kconfig requires the target compiler.
> So, it does not make sense to
> do defconfig with non-existing compiler.

Agree, so I'll check with OpenEmbedded people if there's a reason to do "make allnoconfig"
if it's just a legacy code we'll fix it there.

Thanks a lot for all the input, much appreciated!

 \ /
  Last update: 2018-09-12 15:44    [W:0.196 / U:2.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site