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: Mon, 20 Jan 2003 21:14:17 +0100 [thread overview]
Message-ID: <E18aiJF-000344-00@bigred.inka.de> (raw)
In-Reply-To: <20030119182250.GA1495@mars.ravnborg.org>
> > It is a bug that the current Makefile can't compile modules in an
> > object directory different from the source directory. This means the
> > module source tree can't be mounted read-only (again, without
> > resorting to symlinks).
>
> make -C path/to/kernel/src SUBDIRS=$PWD modules
> So simple when you know the trick. That what I have documented
no, this doesn't work when you have the source and object files _of
the module_ in separate directories. You'd have to run make in the
object directory, but there seems no way to tell it where the source
is. (At least I have not found any.)
The reason to do this is compiling one module for different kernel
configurations as well as compiling one kernel for different
configurations. I.e. I want to have a tree like this:
first the kernel:
/usr/src/linux/2.5.99/ this is directory X
/var/obj/linux/2.5.99/boxa here is X compiled for boxa
/var/obj/linux/2.5.99/boxb here is X compiled for boxb
(this doesn't work either at the moment, another bug/missing feature...)
then the external module:
/usr/src/cipe this is directory Y
/var/obj/cipe/2.5.99/boxa here is Y compiled against X for boxa
/var/obj/cipe/2.5.99/boxb here is Y compiled against X for boxb
and /usr/src might be mounted read-only.
Olaf
next prev parent reply other threads:[~2003-01-20 20:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 12:31 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
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 [this message]
2003-01-20 20:46 ` Sam Ravnborg
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=E18aiJF-000344-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
all inboxes | Powered by JetHome®