Dear Ladies and Gentlemen, as konradc already pointed out, "make prepare" introduces all the problems. I had a quick look on previous Kernel header versions and it seems like they are all faulty, sorry.
Also, konradc is right and make prepare generates the kernel.release file from the shipped basedir Makefile. Changing it might result in problems, as already observed, so we ought not touch it. I have been asking myself how to get rid of this problem and fired up my Debian virtual machine and had a look at their Kernel headers package. Obviously, make prepare does not work there and thus they do not have those problems. This is due to a removed file, which I feel we should do so as well. This sounds weird, breaking "make prepare", I guess, but let me explain why it is no big problem. At least when having the Kernel headers only, "make prepare" will always fail. The only thing it actually does is changing the utsrelease.h file and in spite of that, also the kernel.release file. We do not want this and, as "make prepare" has no real further effect on the headers, i.e. it does not anything needed for any build process to success, we should simply let it fail before causing any more problems. The crucial question is "How to do that?" In fact, it is not much a problem. The only thing we have to do is moving "scripts/basic/Makefile" to the linux-source package, removing it from linux-headers. Due to this, "make prepare" will reasonably fail before building any asm things and *this* bug being fixed. Now, to fix the utsrelease.h/kernel.release bug, it is necessary to set the prepare target in the basedir Makefile to do nothing, in fact ":". make will issue an error and after this terminate without anything being touched. To tie it all together, please have a look at my provided patch against linux-headers-2.6.24-19. Best regards, Mihai Moldovan ** Attachment added: "linux-headers.patch" http://launchpadlibrarian.net/16452995/linux-headers.patch -- Makefile contains incorrect EXTRAVERSION value https://bugs.launchpad.net/bugs/247055 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
