From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Replacement for "make SUBDIRS=...." in 2.5.63?
Date: 28 Feb 2003 13:48:52 +0100 [thread overview]
Message-ID: <87d6lcbmff.fsf@bytesex.org> (raw)
In-Reply-To: Pine.LNX.4.44.0302251039080.13501-100000@chaos.physics.uiowa.edu
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> writes:
> I hope that clarifies things a bit. As I wrote earlier, I'll come up with
> a proper and simple way to build external modules once I find the time.
Any idea what to do until this is available? The "make
SUBDIRS=/dir/outside/kernel/tree modules" approach worked quite well
for a long time, but stopped working now. Which isn't very nice for
driver hacking.
Gerd
--
Weil die späten Diskussionen nicht mal mehr den Rotwein lohnen.
-- Wacholder in “Melanie”
next prev parent reply other threads:[~2003-02-28 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 6:33 Replacement for "make SUBDIRS=...." in 2.5.63? Adam J. Richter
2003-02-25 17:04 ` Kai Germaschewski
2003-02-28 12:48 ` Gerd Knorr [this message]
2003-02-28 16:05 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 19:26 Adam J. Richter
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=87d6lcbmff.fsf@bytesex.org \
--to=kraxel@bytesex.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