From: Muli Ben-Yehuda <mulix@mulix.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: building out of tree modules with 2.6.0-test8
Date: Fri, 24 Oct 2003 08:54:12 +0200 [thread overview]
Message-ID: <20031024065411.GE5017@actcom.co.il> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Hi,
Documentation/kbuild/modules.txt on 2.6.0-test8-bk says:
"Compiling modules outside the official kernel
---------------------------------------------
Often modules are developed outside the official kernel.
To keep up with changes in the build system the most portable way
to compile a module outside the kernel is to use the following
command-line:
make -C path/to/kernel/src SUBDIRS=$PWD modules"
However, trying this yields:
"make[1]: Entering directory `/home/muli/kernel/linux-2.5'
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
make[2]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/asm-i386/asm_offsets.h
Building modules, stage 2.
/home/muli/kernel/linux-2.5/scripts/Makefile.modpost:17:
*** Uh-oh, you have stale module entries. You messed with SUBDIRS,
/home/muli/kernel/linux-2.5/scripts/Makefile.modpost:18:
do not complain if something goes wrong.
MODPOST
make[1]: Leaving directory `/home/muli/kernel/linux-2.5'
What is the correct way to build out of tree modules? if there isn't a
correct way, any pointers on how to go about adding support for it?
Thanks,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://www.livejournal.com/~mulix
"the nucleus of linux oscillates my world" - gccbot@#offtopic
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-10-24 6:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031024065411.GE5017@actcom.co.il \
--to=mulix@mulix.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).