diff options
| author | Nicolas Dechesne <nicolas.dechesne@linaro.org> | 2020-09-02 12:47:44 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-09-10 19:07:40 +0100 |
| commit | 7666bf96cd5853d8d8b3ff402300e2e5879605ce (patch) | |
| tree | 2f3d8b85741cf3b994060a36b28f166b1d87e30f | |
| parent | 5e210cc9c3670c754da89b3729c92a5fca0ae079 (diff) | |
| download | poky-7666bf96cd5853d8d8b3ff402300e2e5879605ce.tar.gz | |
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 <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit bdd06f8ed58ed1c4983f8188e98f1a132da91e3d)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 |
1 files changed, 1 insertions, 1 deletions
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" | |||
| 16 | # and have a machine specific libc. | 16 | # and have a machine specific libc. |
| 17 | # | 17 | # |
| 18 | # But you have some kernel headers you need for some driver? That is fine | 18 | # But you have some kernel headers you need for some driver? That is fine |
| 19 | # but get them from STAGING_KERNEL_DIR where the kernel installs itself. | 19 | # but get them from STAGING_KERNEL_BUILDDIR where the kernel installs itself. |
| 20 | # This will make the package using them machine specific but this is much | 20 | # This will make the package using them machine specific but this is much |
| 21 | # better than having a machine specific C library. This does mean your | 21 | # better than having a machine specific C library. This does mean your |
| 22 | # recipe needs a | 22 | # recipe needs a |