There's no point in configuring Linux kernel before headers installation. Moreover in come cases it might lead to problems on kernels starting from 4.17 with architecture or platfrom sets CROSS_COMPILE variable automatically, see [1].
Also note Buildroot doesn't do that kind of confiuration as well, see [2]. [1] https://lkml.org/lkml/2018/9/12/486 [2] https://git.buildroot.org/buildroot/tree/package/linux-headers/linux-headers.mk#n106 Signed-off-by: Alexey Brodkin <abrod...@synopsys.com> --- meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc index 05c82558e653..1a365ddeb6a9 100644 --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc @@ -54,7 +54,6 @@ S = "${WORKDIR}/linux-${PV}" EXTRA_OEMAKE = " HOSTCC="${BUILD_CC}" HOSTCPP="${BUILD_CPP}"" do_configure() { - oe_runmake allnoconfig } do_compile () { -- 2.17.1 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
