public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: HOWTO build modules in 2.6.0 ...
Date: Tue, 18 Nov 2003 13:39:01 +0000	[thread overview]
Message-ID: <20031118133901.GA64922@compsoc.man.ac.uk> (raw)
In-Reply-To: <20031118055007.GC1008@mars.ravnborg.org>

On Tue, Nov 18, 2003 at 06:50:07AM +0100, Sam Ravnborg wrote:

> > This requires a kernel source tree empty of built files though, so it's
> > really not a great solution ...
> 
> Correct - but why keep kernel trees around full of build files, when
> there is a proper solution to keep them out of the src.

Because people *will* have build trees that are in the source directory.
You're effectively requiring everybody to rebuild their kernel using
some new syntax the first time they want to compile an external module.

External modules were compilable fine (if somewhat clumsily) in 2.4
without any special setup; it's a pity that 2.6 regresses in this given
how superior the build system is in every other way.

> It can be avoided, but that required too much surgery in various
> makefiles and include statements. So that part is 2.7 material.

Would allowing non-O= builds to work again be 2.7 too ? It worked up
until very recently.

regards
john

-- 
Khendon's Law:
If the same point is made twice by the same person, the thread is over.

      parent reply	other threads:[~2003-11-18 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 19:00 HOWTO build modules in 2.6.0 Wojciech 'Sas' Cieciwa
2003-11-17 18:05 ` Randy.Dunlap
2003-11-17 18:28 ` David T Hollis
2003-11-17 20:33 ` Sam Ravnborg
2003-11-17 23:59   ` John Levon
2003-11-18  5:50     ` Sam Ravnborg
2003-11-18  7:11       ` Ian Kent
2003-11-18 13:39       ` John Levon [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20031118133901.GA64922@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=cieciwa@alpha.zarz.agh.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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