Messages in this thread | | | Date | Thu, 4 Nov 2010 17:07:21 +0800 | From | Américo Wang <> | Subject | Re: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after compilation |
| |
On Wed, Nov 03, 2010 at 06:35:46PM +0000, trapDoor wrote: >Obviously I do that only on freshly cloned git tree or on a kernel >unpacked from tarball. If I just update my git tree, the firmware >files will be already in place after previous configuration. And here >is interesting thing: neither of these commands .. > make mrproper > make distclean >.. will remove the firmware files I had put in place manually. After >doing 'make mrproper && make distclean' my tree should be clean. But >those firmwares still remain there (I always check as I need to built >them in and hence my .config refers to them).
They even don't know your firmwares files exist, how can you suppose them to remove those files for you?
> And if I run 'make >oldonfig && make kernelrelease' afterwards, it will come up with a >'non-dirty' version string. And this seems consistent: 'make mrproper >&& make distclean' tell me that my tree is clean despite the FW files >so 'make kernelrelease' gives me a clean version string as well - and >exactly the same version should be propagated after compilation (in >vmlinuz, initrd-img, grub entry, etc.). And that how it always worked >for me before >
Check the output of 'git status', if it says your tree is clean, then you should not have '-dirty'.
>It's not that I think that a kernel with (only) firmware file(s) added >manually should be considered as clean because 'make kernelrelease' >tells me so - actually I always thought it wasis wrong. I just want to >have 'make kernelrelease' coming up with the same version name as I'll >get after compilation. >
If so, you need to disable CONFIG_LOCALVERSION_AUTO *and* append "LOCALVERSION=" to your 'make' command.
| |