linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Alistair J Strachan <alistair@devzero.co.uk>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [RFC] KBUILD 2.5 issues/regressions
Date: Sun, 9 Nov 2003 13:12:56 +0300	[thread overview]
Message-ID: <200311091312.56115.arvidjaar@mail.ru> (raw)
In-Reply-To: <20031106172333.GA1097@mars.ravnborg.org>

On Thursday 06 November 2003 20:23, Sam Ravnborg wrote:
> > So it is still an issue. I am thinking about some way to direct modpost
> > to extract versions out of /boot/vmlinuz and /lib/modules if it detects
> > pristine distribution sources
> >
> > To recap - currently under Mandrake and RH it is possible to do
> >
> > rpm -i kernel-source
> > cd /external/module/src
> > make
> >
> > and it will automatically create module for currently running kernel as
> > long as kernel is distribution kernel without any extra configuration.
>
> I am in the process of addressing this issue.
> What I plan to do is to provide a script solely for the purpose of building
> modules. This script will be simple but allow us to change the build
> process, without changing the way modules are build.
> In order to use module versioning the distributor needs to ship all
> modules. Otherwise the build process cannot look up a symbol exported
> in module A, used by module B.
>

sure. But distributor already has shipped all the modules as part of kernel 
package. Given the number of different kernels in Mandrake currently shipping 
yet another copy of binary modules for kernel sources would easily fill up 
the whole CD alone.

besides it is not the only problem. Even without MODVERSIONS build process 
attempts to write in temporary directory in kernel build tree making it 
impossible for non-root to build module.

> I have the basics implemented. Building a module with src located
> away from the kernel src, and output files located a third place.
> I simply need some spare time to do the rest....
>
> The idea comes from Kai Germaschewski - but I like it and will try to
> implement it.
>

Could you point to posts that describe this idea? Also we could join efforts 
:)

Thank you

-andrey


  parent reply	other threads:[~2003-11-09 10:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  7:10 [RFC] KBUILD 2.5 issues/regressions "Andrey Borzenkov" 
2003-11-05  9:23 ` Arjan van de Ven
2003-11-05 13:39   ` David Woodhouse
2003-11-06 17:23 ` Sam Ravnborg
2003-11-06 23:21   ` Ian Kent
2003-11-09 10:12   ` Andrey Borzenkov [this message]
2003-11-09 10:22     ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2003-07-11 17:57 Alistair J Strachan
2003-07-11 17:40 Alistair J Strachan
2003-07-11 17:47 ` Arjan van de Ven
     [not found] ` <200307111856.53635.alistair@devzero.co.uk>
     [not found]   ` <20030711180134.H19709@devserv.devel.redhat.com>
2003-07-11 18:06     ` Alistair J Strachan

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=200311091312.56115.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=alistair@devzero.co.uk \
    --cc=arjanv@redhat.com \
    --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).