[OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

The KConfig infrastructure hardwires the compiler name to gcc, which breaks the BUILD_CC feature. This is needed even when cross compiling because make *config rely on the kconfig infrastructure --- meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc

Re: [OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

On Tue, Aug 23, 2016 at 3:25 AM, Jérémy Rosen wrote: > The KConfig infrastructure hardwires the compiler name to gcc, which breaks > the BUILD_CC feature. This is needed even when cross compiling because > make *config rely on the kconfig infrastructure > --- > meta/recipes-kernel/linux-libc-hea

Re: [OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

> On Aug 23, 2016, at 6:39 AM, Bruce Ashfield wrote: > > > > On Tue, Aug 23, 2016 at 3:25 AM, Jérémy Rosen > wrote: > The KConfig infrastructure hardwires the compiler name to gcc, which breaks > the BUILD_CC feature. This is needed even when cross compiling beca

Re: [OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

[...] If this is broken, it needs to be fixed upstream. I agree. now a days we have more than gcc available as system C compiler perhaps your patch might be upstream worthy. As stated elsewhere, I now have a proper way to override the variables without patching the build system. V2 of this