On multiple kernel versions of the same kernel programs which need System.map can use the wrong System.map since using 'uname -r' which is of course the same on same kernel version, even if kernel names and System.map names are different. Patch *should* be trivial... -KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION) +KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)-$(BUILDVERSION) So users who want to use multiple version (eg. 2.4.22-gentoo-r3 and 2.4.22-gentoo-r3-mon (monolithic version)) can "export BUILDVERSION=mon" and System.map-2.4.22-gentoo-r3-mon would be correctly recognized with it's kernel. Couldn't dig the regexp on Makefile deep enough until now to "see" if the added buildversion has any negative consequences but for me it works fine. (Most users would hardly need it, so just an idea ;) Reproducible: Always Steps to Reproduce:
I confirmed this bug in -r3 (the hard way... stuff got messed up...) This bug is fixed in -r4.
This is a duplicate of bug 37444. The existing -r3 ebuild was already fixed. Here's the CVS change list: http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-kernel/gentoo-sources/gentoo-sources-2.4.22-r3.ebuild
Oops I might have misread the bug. It doesn't seem to be a duplicate after all. Sorry.
The easiest way to do this would be to add it to EXTRAVERSION, as anything else wouldn't be standard according to Documentation/kbuild/makefiles.txt. You wouldn't need to patch anything except the ebuild itself. -EXTRAVERSION = -gentoo-r4 +EXTRAVERSION = -gentoo-r4-mon Kinda cheesy, but it should be guaranteed to work/not break anything.
Should have RTFmakefiles.txt before ;) OK, so back to the standard/manual way. :/
So is this resolved? Why not use make install with /boot mounted?
Interest seems to have died. Closing.
To Quote "Should have RTFmakefiles.txt before ;) OK, so back to the standard/manual way. :/" Closing.
