From: Sam Ravnborg <sam@ravnborg.org>
To: John Levon <levon@movementarian.org>
Cc: "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 06:50:07 +0100 [thread overview]
Message-ID: <20031118055007.GC1008@mars.ravnborg.org> (raw)
In-Reply-To: <20031117235927.GA31611@compsoc.man.ac.uk>
On Mon, Nov 17, 2003 at 11:59:27PM +0000, John Levon wrote:
> On Mon, Nov 17, 2003 at 09:33:36PM +0100, Sam Ravnborg wrote:
>
> > Use the following:
> > make -C /usr/src/linux SUBDIRS=`pwd` O=/users/cieciwa/rpm/BUILD/eagle-1.0.4/linux modules
> >
>
> 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.
The problem was generated files. If a generated file were present in
the kernel source tree, it would not be built again.
This resulted in a few suprises during development, and I therefore
added the check for a kernel source tree with no built-files.
It can be avoided, but that required too much surgery in various
makefiles and include statements. So that part is 2.7 material.
Sam
next prev parent reply other threads:[~2003-11-18 5:50 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 [this message]
2003-11-18 7:11 ` Ian Kent
2003-11-18 13:39 ` John Levon
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=20031118055007.GC1008@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=cieciwa@alpha.zarz.agh.edu.pl \
--cc=levon@movementarian.org \
--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