Could you explain what is the actually gain of using the
modversions file your patch creates. (modpost changes)
distributions don't like to install the vmlinux since it's big(ish) and
means customers need to download a new vmlinux at each kernel erratum.
The same information is btw also
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
On Sun, 2004-03-07 at 14:46, Andreas Gruenbacher wrote:
Hello Arjan,
On Sun, 2004-03-07 at 14:03, Arjan van de Ven wrote:
Could you explain what is the actually gain of using the
modversions file your patch creates. (modpost changes)
distributions don't like to install the
On Sun, Mar 07, 2004 at 05:45:22PM +0100, Andreas Gruenbacher wrote:
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.
We have tried that
On Sun, Mar 07, 2004 at 01:44:58AM +0100, Andreas Gruenbacher wrote:
Hello,
here is the patch I posted previously that adds support for modversions
in external kernel modules that are built outside the main kernel tree
(first posting archived here: http://lwn.net/Articles/69148/). Relative
Hello Arjan,
On Sun, 2004-03-07 at 14:03, Arjan van de Ven wrote:
Could you explain what is the actually gain of using the
modversions file your patch creates. (modpost changes)
distributions don't like to install the vmlinux since it's big(ish) and
means customers need to download a
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
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.
Which means that my
On Sun, Mar 07, 2004 at 02:32:14PM +0100, Andreas Gruenbacher wrote:
What I have in mind is something like this:
- Get rid of current use of SUBDIRS. It is no longer used in any
arch Makefiles.
- Introduce a KBUILD_EXTMOD variable that is only set when building
external modules
-
On Sun, Mar 07, 2004 at 05:45:22PM +0100, Andreas Gruenbacher wrote:
All in all, in the end I changed my mind. I now think that it's better
to build modules against a clean kernel source tree that additionally
has the modversions file copied in. This already works when using O=.
With the
10 matches
Mail list logo
