From 7666bf96cd5853d8d8b3ff402300e2e5879605ce Mon Sep 17 00:00:00 2001 From: Nicolas Dechesne Date: Wed, 2 Sep 2020 12:47:44 +0200 Subject: linux-libc-headers: kernel headers are installed in STAGING_KERNEL_BUILDDIR Since 'fido', kernel headers are installed in STAGING_KERNEL_BUILDDIR, not STAGING_KERNEL_DIR. So this message in the linux-libc-headers recipe is slightly misleading. (From OE-Core rev: 83b74458783aac5d1d5a3ea8a31ccb79de3719bc) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie (cherry picked from commit bdd06f8ed58ed1c4983f8188e98f1a132da91e3d) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie --- meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 +- 1 file changed, 1 insertion(+), 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 4481aa430c..4ad74a27e9 100644 --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc @@ -16,7 +16,7 @@ LICENSE = "GPLv2" # and have a machine specific libc. # # But you have some kernel headers you need for some driver? That is fine -# but get them from STAGING_KERNEL_DIR where the kernel installs itself. +# but get them from STAGING_KERNEL_BUILDDIR where the kernel installs itself. # This will make the package using them machine specific but this is much # better than having a machine specific C library. This does mean your # recipe needs a -- cgit v1.2.3-54-g00ecf