compiling only one module in kernel version 2.6?
What's the easiest way to compile just one module in the Linux 2.6 kernel tree?
This no longer seem to work:
$ cd /usr/src/linux
$ make SUBDIRS=fs/reiserfs modules
Building modules, stage 2.
MODPOSTI don't see any .ko generated.
Quoted 10 lines · Fong Vang
What's the easiest way to compile just one module in the Linux 2.6 kernel tree?
This no longer seem to work:
$ cd /usr/src/linux $ make SUBDIRS=fs/reiserfs modules Building modules, stage 2. MODPOSTI don't see any .ko generated.
It worked for me. Is your reiserfs turned on as a module, and not compiled into the kernel. (<M> not <*> nor < >)
-- Steve
Quoted 10 lines · On Tue, 16 Aug 2005 23:18:49 -0400 Steven Rostedt wrote:
Quoted 9 lines · Fong Vang
What's the easiest way to compile just one module in the Linux 2.6 kernel tree?
This no longer seem to work:
$ cd /usr/src/linux $ make SUBDIRS=fs/reiserfs modules Building modules, stage 2. MODPOST
Quoted 4 lines
Quoted 1 line
I don't see any .ko generated.
It worked for me. Is your reiserfs turned on as a module, and not compiled into the kernel. (<M> not <*> nor < >)
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
---
~Randy
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
-- Steve
Quoted 9 lines · Steven Rostedt
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
I just did this on a 2.6.9 vanilla kernel, and it still worked. How "recent" did Sam do this?
-- Steve
Quoted 6 lines · On Wed, 17 Aug 2005 01:54:50 -0400 Steven Rostedt wrote:
Quoted 5 lines · Steven Rostedt
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
Quoted 7 lines
Quoted 4 lines
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
I just did this on a 2.6.9 vanilla kernel, and it still worked. How "recent" did Sam do this?
2.6.9 did not handle "make one_module.ko" (for me on x86).
---
~Randy
Quoted 6 lines · Steven Rostedt
Quoted 5 lines · Steven Rostedt
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
Quoted 6 lines
Quoted 4 lines
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
I just did this on a 2.6.9 vanilla kernel, and it still worked.
Hi Steve.
make fs/reiserfs/
and
make fs/reiserfs/resiserfs.ko
does not do the same thing. Only the latter result in a .ko file.
Sam
Quoted 14 lines · Sam Ravnborg
Quoted 6 lines · Steven Rostedt
Quoted 5 lines · Steven Rostedt
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
Quoted 6 lines
Quoted 4 lines
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
I just did this on a 2.6.9 vanilla kernel, and it still worked.
Quoted 7 lines
Hi Steve.
make
fs/reiserfs/
and
makefs/reiserfs/resiserfs.kodoes not do the same thing. Only the latter result in a .ko file.
I never said I did a "make fs/reiserfs". I did a "make SUBDIRS=fs/reiserfs" which does produce a .ko file.
But even shorter is to do a "make M=fs/reiserfs", which also works.
But, I guess what was added was the ability to just type the module itself. That's cool, but I haven't had the need to do that (yet).
-- Steve
Quoted 17 lines · Steven Rostedt
Quoted 16 lines · Sam Ravnborg
Quoted 6 lines · Steven Rostedt
Quoted 5 lines · Steven Rostedt
Quoted 3 lines · Randy.Dunlap
Sam only added make .ko build support very recently, so it could easily depend on what kernel verison Fong is using.
Quoted 6 lines
Quoted 4 lines
That could very well explain it. I'm doing this on 2.6.13-rc6-rt6 (2.6.13-rc6 with Ingo's rt6 patch applied). So I really do have a recent kernel.
I just did this on a 2.6.9 vanilla kernel, and it still worked.
Hi Steve.
Quoted 8 lines
Quoted 5 lines
make
fs/reiserfs/
and
makefs/reiserfs/resiserfs.kodoes not do the same thing. Only the latter result in a .ko file.
I never said I did a "make fs/reiserfs". I did a "make SUBDIRS=fs/reiserfs" which does produce a .ko file.
That command uses an implicit target of all (which is bzImage + modules), and then SUBDIRS (or M) limits it to the specified subdir., so it builds all modules in the specified subdir.
As opposed to what I thought(?) the OP was asking about:
how to build one module only.
I think that we have nailed it enough now, yes? :)
Quoted 4 lines
But even shorter is to do a "make M=fs/reiserfs", which also works.
But, I guess what was added was the ability to just type the module itself. That's cool, but I haven't had the need to do that (yet).
Signature · 1 line
~Randy