From: Arjan van de Ven <arjanv@redhat.com>
To: Andreas Gruenbacher <agruen@suse.de>,
Sam Ravnborg <sam@ravnborg.org>,
lkml <linux-kernel@vger.kernel.org>,
"kbuild-devel@lists.sourceforge.net"
<kbuild-devel@lists.sourceforge.net>
Subject: Re: External kernel modules, second try
Date: Sun, 7 Mar 2004 17:08:24 +0100 [thread overview]
Message-ID: <20040307160824.GA14967@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040307160527.GA2027@mars.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Sun, Mar 07, 2004 at 05:05:27PM +0100, Sam Ravnborg wrote:
> On Sun, Mar 07, 2004 at 03:01:31PM +0100, Arjan van de Ven wrote:
> > > and it's missing the symbols from
> > > module files.
> >
> > sure but the module files are generally installed...
> I'm aiming for a situation where I can build external modules,
> using an almost clean kernel src tree.
Personally I don't see the point. I'm perfectly happy with the current
situation with the exception of not using System.map and co.
From a distribution kernel pov; I already ship a subset of files for building
modules against (basically include/, the KConfig and makefiles), which only
not 100% works because I don't ship vmlinux.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-07 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 0:44 External kernel modules, second try Andreas Gruenbacher
2004-03-07 12:53 ` Sam Ravnborg
2004-03-07 13:03 ` Arjan van de Ven
2004-03-07 13:46 ` Andreas Gruenbacher
2004-03-07 14:01 ` Arjan van de Ven
2004-03-07 14:26 ` Andreas Gruenbacher
2004-03-07 15:09 ` GPL 3 mark kandianis
2004-03-07 15:14 ` Måns Rullgård
2004-03-07 16:43 ` John Bradford
2004-03-07 16:05 ` External kernel modules, second try Sam Ravnborg
2004-03-07 16:08 ` Arjan van de Ven [this message]
2004-03-07 16:45 ` Andreas Gruenbacher
2004-03-07 16:49 ` Arjan van de Ven
2004-03-07 18:33 ` Sam Ravnborg
2004-03-07 13:32 ` Andreas Gruenbacher
2004-03-07 15:09 ` Sergey Vlasov
2004-03-07 18:37 ` Sam Ravnborg
2004-03-07 16:18 ` 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=20040307160824.GA14967@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=agruen@suse.de \
--cc=kbuild-devel@lists.sourceforge.net \
--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