[BUG][2.5.60/61] - Making modules problem

[BUG][2.5.60/61] - Making modules problem

[Shawn Starr]

when doing make modules it does not build modules? It builds the kernel 

Has this behaviour changed or is this broken right now?

Shawn.

Re: [BUG][2.5.60/61] - Making modules problem

[Shawn Starr]

Ignore this, I didn't realize that you have to make the kernel image first 
THEN compile modules, before it would allow building modules before an actual 
kernel was compiled :-)

Shawn.

>List:     linux-kernel
>Subject:  [BUG][2.5.60/61] - Making modules problem
From:     Shawn Starr <spstarr () sh0n ! net>
>Date:     2003-02-16 5:11:05

>when doing make modules it does not build modules? It builds the kernel 

>Has this behaviour changed or is this broken right now?

>Shawn.

-- 
Shawn Starr
UNIX Systems Administrator, Operations
Datawire Communication Networks Inc.
10 Carlson Court, Suite 300
Toronto, ON, M9W 6L2
T: 416-213-2001 ext 179  F: 416-213-2008
shawn.starr@datawire.net
"The power to Transact" - http://www.datawire.net

Re: [BUG][2.5.60/61] - Making modules problem

[Kai Germaschewski]

On Mon, 17 Feb 2003, Shawn Starr wrote:

> Well, if I take a vanilla kernel, extract it, copy my old .config over, make 
> oldconfig, select anything new, make modules, it used to skim though sources 
> and compile the modules selected. Now, it builds bzImage (or whatever 
> vmlinux) and THEN builds the modules last.

It really builds the modules at the same time (as module.o),
then vmlinux, then the final modules (module.ko)

> If I have a built vmlinux, before I do make modules, it will just compile the 
> modules as it would normally do.

Okay, that's expected, with

> CONFIG_MODVERSIONS=y

So not a bug. Thanks for the details.

--Kai

Re: [BUG][2.5.60/61] - Making modules problem

[Kai Germaschewski]

On Mon, 17 Feb 2003, Shawn Starr wrote:

> Not a bug but I think an annoyance because sometimes I just want to recompile 
> just the modules using the same kernel version and not have to build the 
> whole thing just to get modules.

You have CONFIG_MODVERSIONS=y. Say your module is using printk(). So your 
module needs to know the checksum for printk(). This checksum is generated 
during the build of kernel/printk.c and then propagated into vmlinux, 
which is where the module build gets it from.

That's why you need printk.o / vmlinux to build the module. If you 
don't want these checks, turn of CONFIG_MODVERSIONS and it's back to what 
it used to be.

--Kai