diff options
| -rw-r--r-- | meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 7 |
1 files changed, 4 insertions, 3 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 2ba6ed51df..92acf8aa0b 100644 --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | |||
| @@ -18,9 +18,10 @@ LICENSE = "GPLv2" | |||
| 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_DIR 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 DEPENDS += "virtual/kernel" but again, that is fine and | 22 | # recipe needs a |
| 23 | # makes total sense. | 23 | # do_configure[depends] += "virtual/kernel:do_shared_workdir" |
| 24 | # but again, that is fine and makes total sense. | ||
| 24 | # | 25 | # |
| 25 | # There can also be a case where your kernel extremely old and you want | 26 | # There can also be a case where your kernel extremely old and you want |
| 26 | # an older libc ABI for that old kernel. The headers installed by this | 27 | # an older libc ABI for that old kernel. The headers installed by this |