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-02 16:00:47 +0100 |
| commit | b36dfafb69d24a3e7d32401c19b950a4ad391787 (patch) | |
| tree | a14492e04b564e4393ace1da293fad28a9e08120 /meta/recipes-kernel/linux-libc-headers | |
| parent | daa8aeed535b3584894426e7e76cd6ce77bb2e57 (diff) | |
| download | poky-b36dfafb69d24a3e7d32401c19b950a4ad391787.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: bdd06f8ed58ed1c4983f8188e98f1a132da91e3d)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/linux-libc-headers')
| -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 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" | |||
| 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 |