Re: [PATCH] CONFIG_RELOCATABLE modpost fix
From: Eric W. Biederman
Date: Tue Aug 08 2006 - 15:57:07 EST
Sam Ravnborg <sam@xxxxxxxxxxxx> writes:
> On Tue, Aug 08, 2006 at 05:32:11PM +0900, Magnus Damm wrote:
>> CONFIG_RELOCATABLE modpost fix
>> Run modpost on vmlinux regardless of CONFIG_MODULES.
> Below is my take on this one.
> - Dropped -rR since this is default now
> - Dropped subdir- assignment in scripts/Makefile since it is redundant
> - Always pass vmlinux ti modpost so we have full updated info
> - Print out number of modules being mod posted to distingush from
> vmlinux one
> - use vmlinux as target name to enable nicer quiet command print
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/