<br><br>On Friday, September 13, 2013, Richard Purdie wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm getting concerned with the number of people forking this recipe<br>
and not understanding what they're doing. I'm therefore proposing<br>
adding in a suitable warning to people thinking of copying it.<br>
<br>
Signed-off-by: Richard Purdie <<a href="javascript:;" onclick="_e(event, 'cvml', 'richard.purdie@linuxfoundation.org')">richard.purdie@linuxfoundation.org</a>><br>
---<br>
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc<br>
index 96fe2ff..79b7dc4 100644<br>
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc<br>
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc<br>
@@ -2,6 +2,28 @@ DESCRIPTION = "Sanitized set of kernel headers for the C library's use."<br>
SECTION = "devel"<br>
LICENSE = "GPLv2"<br>
<br>
+#########################################################################<br>
+#### PLEASE READ<br>
+#########################################################################<br>
+#<br>
+# You're probably looking here thinking you need to create some new copy<br>
+# of linux-libc-headers since you have your own custom kernel. To put<br>
+# this simply, you DO NOT.<br>
+#<br>
+# Why? These headers are used to build the libc. If you customise the<br>
+# headers you are customising the libc and the libc becomes machine<br>
+# specific. Most people do not add custom libc extensions to the kernel<br>
+# and have a machine specific libc.<br>
+#<br>
+# But you have some kernel headers you need for some driver? That is fine<br>
+# but get them from STAGING_KERNEL_DIR where the kernel installs itself.<br>
+# This will make the package using them machine specific but this is much<br>
+# better than having a maching specific C library. This does mean your<br>
+# recipe needs a DEPENDS += "virtual/kernel" but again, that is fine and<br>
+# makes total sense.<br>
+#<br>
+# -- RP</blockquote><div><br></div><div>There are cases where we have bsps with 2.6.3x kernels and libc compiled against 3.10 assumes syscalls<br></div><div>Which the kernel will not provide. These kinds are genuine cases for creating equivalent recipes</div>
<div>You should mention the valid case too in this notice and basically asses the user is knowing what. He is doing</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+<br>
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"<br>
<br>
python __anonymous () {<br>
<br>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'Openembedded-core@lists.openembedded.org')">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote>