If we have this recipe, it means the whole armv6 (or whichever tune) is chosen
depends
on a machine specific recipe. This makes no sense as armX packages are meant to
be
machine independent.
We've had this problem in other layers and it causes needed rebuilds of packages
when you switch machines since the sstate checksums change. These headers are
just part
of the toolchain bootstrap process so "standard" kernel headers are fine. The
kernel
header version does need to be later of equal to the kernel version but we're
fine in
that regard since the core is on 3.8, the latest pi kernel is 3.6.
There is nothing special about these headers so lets remove them and use the
standard
system provided recipe, avoding any rebuilds. I tested the various other
recipes in
the layer and there doesn't seem to be any dependency on these headers.
Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
---
.../linux-libc-headers-raspberrypi_3.2.27.bb | 12 ------------
1 file changed, 12 deletions(-)
delete mode 100644
recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
diff --git
a/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
b/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
deleted file mode 100644
index a5964ab..0000000
--- a/recipes-kernel/linux-libc-headers/linux-libc-headers-raspberrypi_3.2.27.bb
+++ /dev/null
@@ -1,12 +0,0 @@
-require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
-
-PR = "r0"
-
-PROVIDES = "linux-libc-headers"
-RPROVIDES_${PN}-dev = "linux-libc-headers-dev"
-RPROVIDES_${PN}-dbg = "linux-libc-headers-dbg"
-
-SRCREV = "10182a3bc434b27740f81c2b836a1af943060241"
-SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.2.27 \
- "
-S = "${WORKDIR}/git"
--
1.7.10.4
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
