summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel/linux-libc-headers
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-13 12:18:14 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-14 08:21:00 +0100
commitbabbf7a46acaefd9b36031483cafce053f607e66 (patch)
tree6dd67c19b0406259d860d8c56f89a270a9d6ad05 /meta/recipes-kernel/linux-libc-headers
parent214bb6828ef909f4a6ea61e792c7c715b9c3276f (diff)
downloadpoky-babbf7a46acaefd9b36031483cafce053f607e66.tar.gz
linux-libc-headers: Add big warning about antisocial behaviour
I'm getting concerned with the number of people forking this recipe and not understanding what they're doing. I'm therefore proposing adding in a suitable warning to people thinking of copying it. (From OE-Core rev: c27ac156bcaf3193d52f456480947b0cfaef3c72) 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.inc27
1 files changed, 27 insertions, 0 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 96fe2ffd62..f4a02331ff 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
@@ -2,6 +2,33 @@ DESCRIPTION = "Sanitized set of kernel headers for the C library's use."
2SECTION = "devel" 2SECTION = "devel"
3LICENSE = "GPLv2" 3LICENSE = "GPLv2"
4 4
5#########################################################################
6#### PLEASE READ
7#########################################################################
8#
9# You're probably looking here thinking you need to create some new copy
10# of linux-libc-headers since you have your own custom kernel. To put
11# this simply, you DO NOT.
12#
13# Why? These headers are used to build the libc. If you customise the
14# headers you are customising the libc and the libc becomes machine
15# specific. Most people do not add custom libc extensions to the kernel
16# and have a machine specific libc.
17#
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.
20# This will make the package using them machine specific but this is much
21# better than having a maching specific C library. This does mean your
22# recipe needs a DEPENDS += "virtual/kernel" but again, that is fine and
23# makes total sense.
24#
25# 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# recipe should still be a standard mainline kernel, not your own custom
28# one.
29#
30# -- RP
31
5LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7" 32LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
6 33
7python __anonymous () { 34python __anonymous () {