summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/python
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2012-10-18 10:47:05 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-12-13 15:21:44 +0000
commitdbaa3f075d4f62d0b5427cd565a4543dc2c709d4 (patch)
tree8dfd42935202ccb91a905a2d9a20bad1bce7eb57 /meta/recipes-devtools/python
parentdacedaa31edcbbdcbb69cb1305f9b13bda5847df (diff)
downloadpoky-dbaa3f075d4f62d0b5427cd565a4543dc2c709d4.tar.gz
kernel.bbclass: remove explicit version.h target
The compilation routine for the kernel has an explicit call to build version.h, which works fine for most kernels, but the location of it has recently changes. commit d183e6f5 [UAPI: Move linux/version.h] commit 10b63956 [UAPI: Plumb the UAPI Kbuilds into the user header installation and checking] moves the file to include/generated/linux/version.h and then to include/generated/uapi/linux/version.h. As a result kernel builds of 3.7 or bisection builds of intermediate kernel commits will fail with: make[2]: *** No rule to make target `include/linux/version.h'. Stop. Making the explicit version.h build conditional on the version, or via a file test would fix the problem, but it introduces some complexity to the build. Even without an explicit call to build version.h, it is always produced by the kernel build, so it can simply be removed. This extra make line was originally so that the kernel version could be determined, so that then different instructions could be executed depending on whether it was a 2.4 or 2.6 kernel. Since we no longer support 2.4, this code is no longer needed. [YOCTO: #3293] (From OE-Core rev: 1ccc1560114d14f7492c034620ad8d7a8d2ef175) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python')
0 files changed, 0 insertions, 0 deletions