From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ANN: LKMB (Linux Kernel Module Builder) version 0.1.16
Date: Sat, 18 Jan 2003 23:37:19 +0100 [thread overview]
Message-ID: <E18a1aZ-0006mL-00@bigred.inka.de> (raw)
In-Reply-To: Pine.LNX.4.33L2.0301171857230.25073-100000@vipe.technion.ac.il
> > Use "/lib/modules/`uname -r`/build" as a default kernel directory, but
> > allow it to be overridden somehow from the command line. Then do something
> > like...
>...
> Do you mean I'll need a live Linux kernel to build the kernel module
> package?
Whoever invented this /lib/modules/... scheme should have known that
it provokes this sort of misunderstandings, not to mention is broken
in other ways too.
You need the _source_ of the kernel the module will run on to compile
modules. You don't need to _run_ this kernel while compiling. Putting
build infrastructure into a deployment directory at the least causes
confusion, not to mention that the deployment directory might not even
exist on the development machine. (I routinely compile kernels and
modules of different configurations for three boxes on one of them,
the other two don't even have a complete development toolset.)
Compiling modules is one of the things which always have been among
the most broken things in the kernel build systems, can this please be
fixed and properly documented?
Olaf
next prev parent reply other threads:[~2003-01-18 22:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 12:31 ANN: LKMB (Linux Kernel Module Builder) version 0.1.16 Shlomi Fish
2003-01-17 12:37 ` Shlomi Fish
2003-01-17 13:12 ` David Woodhouse
2003-01-17 17:00 ` Shlomi Fish
2003-01-17 18:00 ` Sam Ravnborg
2003-01-17 18:28 ` Shlomi Fish
2003-01-18 22:37 ` Olaf Titz [this message]
2003-01-18 22:55 ` Arjan van de Ven
2003-01-20 20:03 ` Olaf Titz
2003-01-20 21:39 ` Arjan van de Ven
2003-01-21 21:16 ` Olaf Titz
2003-01-21 21:30 ` David Lang
2003-01-21 21:46 ` Sam Ravnborg
2003-01-22 11:21 ` David Woodhouse
2003-01-22 11:18 ` David Woodhouse
2003-01-22 19:16 ` Bill Davidsen
2003-01-22 22:17 ` David Woodhouse
2003-01-19 0:12 ` John Levon
2003-01-19 12:55 ` Olaf Titz
2003-01-19 13:06 ` Arjan van de Ven
2003-01-20 20:16 ` Olaf Titz
2003-01-19 18:22 ` Sam Ravnborg
2003-01-20 20:14 ` Olaf Titz
2003-01-20 20:46 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 21:17 Paul Zimmerman
2003-01-19 21:24 Paul Zimmerman
2003-01-23 0:20 Hal Duston
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=E18a1aZ-0006mL-00@bigred.inka.de \
--to=olaf@bigred.inka.de \
--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