v86d was building directly against the staged kernel in the target
sysroot. This has been fine in the past, but with recent (3.7) changes
to user headers into the "uapi" include structure, there are no longer
Without the preprocesor protection, v86d fails to build against any
kernel with uapi header files.
v86d doesn't actually need the whole kernel tree, the exported headers
are enough to build a working binary. This change sets the v86d variable
to ${STAGING_DIR_HOST}/usr, and once the v86d build adds "include" to the
end of KDIR, we have a valid include path to the target sysroot headers.
This also works for pre-uapi kernel headers, so the change is safe for
most (if not all) kernel's with properly exported headers.
Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com>
---
meta/recipes-bsp/v86d/v86d_0.1.10.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/v86d/v86d_0.1.10.bb
b/meta/recipes-bsp/v86d/v86d_0.1.10.bb
index 51829a3..2dbfbb5 100644
--- a/meta/recipes-bsp/v86d/v86d_0.1.10.bb
+++ b/meta/recipes-bsp/v86d/v86d_0.1.10.bb
@@ -27,7 +27,7 @@ do_configure () {
}
do_compile () {
- KDIR="${STAGING_KERNEL_DIR}" make
+ KDIR="${STAGING_DIR_HOST}/usr" make
}
do_install () {
--
1.7.10.4
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
