Messages in this thread | | | Date | Wed, 9 Aug 2006 00:05:09 +0200 | From | Sam Ravnborg <> | Subject | Re: [PATCH] CONFIG_RELOCATABLE modpost fix |
| |
On Tue, Aug 08, 2006 at 01:59:03PM -0600, Eric W. Biederman wrote:
> Sam, Magnus: > > I'm dense. Why do we want to run modpost if we are building a kernel > that doesn't support modules? > > I haven't mucked with modpost at all so I don't have a good feel for > what it does, or why we want to run it. > > My quick skimming says modpost is all about generating the module > version symbol scrambling. Which if that is all it does means it is > senseless to run this without modules.
Recently modpost has been enhanced to do section reference checks. So modpost is used to check that there is no references from .text to .init.text - the latter will be freed by the kernel so we better avoid it.
The consistency checks does a bit more than just that simple check but this was enough reason to run it twice in the build process.
Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |