From b36dfafb69d24a3e7d32401c19b950a4ad391787 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: bdd06f8ed58ed1c4983f8188e98f1a132da91e3d) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/recipes-kernel') 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 b1cb553c75..3bceac40cc 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