From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org
Subject: Re: external modules documentation
Date: Thu, 23 Sep 2004 22:24:50 +0200 [thread overview]
Message-ID: <200409232224.50234.arekm@pld-linux.org> (raw)
In-Reply-To: <20040918112900.GA22428@lst.de>
On Saturday 18 of September 2004 13:29, Christoph Hellwig wrote:
> Sam,
>
> is there any reason your patch from June still isn't merged?
>
[...]
> +Prepare the kernel for building external modules
> +------------------------------------------------
> +When building external modules the kernel is expected to be prepared.
> +This includes the precense of certain binaries, the kernel configuration
> +and the symlink to include/asm.
> +To do this a convinient target is made:
> +
> + make modules_prepare
> +
> +For a typical distribution this would look like the follwoing:
> +
> + make modules_prepare O=/lib/modules/linux-<kernel version>/build
Tthis means that one, unmodified source tree is _not_ usable for multiple
architectures. You can't use the same, prepared sources and for example
create noarch.rpm or burn on cd and then use for external modules building on
different architectures.
We are using this:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/linux-kbuild-extmod.patch?rev=1.2
to get external modules working for multiple archs with the same sources:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SPECS/template-kernel-module.spec?rev=1.14
--
Arkadiusz Miśkiewicz PLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/ http://ftp.pld-linux.org/
next prev parent reply other threads:[~2004-09-23 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 11:29 external modules documentation Christoph Hellwig
2004-09-23 20:24 ` Arkadiusz Miskiewicz [this message]
2004-09-27 7:25 ` Sam Ravnborg
2004-09-27 8:25 ` Arkadiusz Miskiewicz
2004-09-27 7:23 ` Sam Ravnborg
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=200409232224.50234.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--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