From: Andreas Gruenbacher <agruen@suse.de>
To: arjanv@redhat.com
Cc: Sam Ravnborg <sam@ravnborg.org>,
lkml <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net
Subject: Re: External kernel modules, second try
Date: Sun, 07 Mar 2004 15:26:40 +0100 [thread overview]
Message-ID: <1078669600.4168.10.camel@nb.suse.de> (raw)
In-Reply-To: <1078668091.9106.1.camel@laptop.fenrus.com>
On Sun, 2004-03-07 at 15:01, Arjan van de Ven wrote:
> On Sun, 2004-03-07 at 14:46, Andreas Gruenbacher wrote:
> > and it's missing the symbols from
> > module files.
>
> sure but the module files are generally installed...
Not when building for five different configurations on one machine. (And
this is not a theoretical case.)
> > Now it would be possible to extract the modver symbols from the
> > installed vmlinux and .ko files when needed, but note that we may be
> > building modules for kernels that are not currently running, and for
> > which those binaries are not even installed. So this sounds like a bad
> > idea.
>
> I don't personally care about those; you need SOME stuff to build
> against obviously, and vmlinux is well over the top I agree that. But
> assuming the .ko's for the modules are there...you need those to use the
> kernel anyway.
The .ko's are really not there. And even if they were, I don't think we
want to teach modpost to poke around in /lib/modules when it can be
avoided easily.
Cheers,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX AG
next prev parent reply other threads:[~2004-03-07 14:26 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 [this message]
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
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=1078669600.4168.10.camel@nb.suse.de \
--to=agruen@suse.de \
--cc=arjanv@redhat.com \
--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