On Thu, 2012-10-18 at 10:47 -0400, Bruce Ashfield wrote: > 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. > > Note: it isn't clear why the explicit build of version.h was originally > required, but the prep phases of the kernel have changed significantly, > so it should no longer be required.
I had a look through the archives. I think this is a throwback to 2.4, we had to build the version.h file to figure out if we had a 2.6 or a 2.4 kernel, then we could do the right thing to build it. Since we don't support 2.4 anymore, this can die! Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
