From: Nicolas Dechesne Date: Wed, 2 Sep 2020 10:47:44 +0000 (+0200) Subject: linux-libc-headers: kernel headers are installed in STAGING_KERNEL_BUILDDIR X-Git-Tag: lucaceresoli/bug-15201-perf-libtraceevent-missing~10171 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bdd06f8ed58ed1c4983f8188e98f1a132da91e3d;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git 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. Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- 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 b1cb553c752..3bceac40cc2 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