summaryrefslogtreecommitdiffstats
path: root/meta/recipes-connectivity/iproute2
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2013-02-15 23:17:51 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-03-01 13:03:28 +0000
commitec3d3fa9c20d466f24a0d26518ddd8dd8282fdb0 (patch)
treee16567c2f6509067c19492672ba7c7a789b502f7 /meta/recipes-connectivity/iproute2
parentcc1c217ff36c0a994fcc56bd20d2c43cb37fab03 (diff)
downloadpoky-ec3d3fa9c20d466f24a0d26518ddd8dd8282fdb0.tar.gz
v86d: compile against userspace safe kernel headers
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. (From OE-Core rev: 8d4256b2c9f782368a16c1458e04ed61fa82691a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity/iproute2')
0 files changed, 0 insertions, 0 deletions