archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <>
To: Bernd Porr <>
Cc: Sam Ravnborg <>,,
Subject: Re: compiling external kernel modules (
Date: Sat, 2 Aug 2003 14:07:56 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Aug 02, 2003 at 12:53:07PM +0100, Bernd Porr wrote:
> Ok. Thanks. Now the bug is that comedi cannot find the file "Rules.make" 
> which is apparently no longer there in 2.6. Is it right that the rules 
> are now integrated in the corresponding makefiles?

The way to find the Makefiles changed during the 2.5 development
cycle. Now the kbuild Makefile (the one for comedi for example) are
included from scripts/ hereby obsoleting Rules.make.

You will NOT succeed creating a single simple makefile supporting both
2.4 and 2.6. On the other hand the Makefile are so trivial that creating
two distinct version should be acceptable?

> Can you recommend me a Makefile which I can take as a template? Comedi 
> uses some sort of autoconfig and I have to append then the "rules" to 
> the automatically generated makefile.

The most simple Makefile looks like this:

obj-m := comedi.o

No more is actually needed.
You should get rid of export-objs as well - they are also obsoleted
in 2.5/2.6.

> Another thing: can a prevent the kernel of generating the "Stage 2"? It 
> would be nice if the kernel doen't need to write to it's own directories 
> if it compiles external modules.

The right fix is to allow you to build a kernel in a directory
separate from the kernel src. This is WIP - hopefully included in 
mainline within a few weeks.

PS. Please do not cc: subscription only mailing lists.


  reply	other threads:[~2003-08-02 12:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02  1:04 compiling external kernel modules ( Bernd Porr
2003-08-02  7:04 ` Sam Ravnborg
2003-08-02 11:53   ` Bernd Porr
2003-08-02 12:07     ` Sam Ravnborg [this message]
2003-08-02 13:10       ` Bernd Porr
2003-08-02 23:05         ` Sam Ravnborg
2003-08-11 13:53           ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).