public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: build system broken in 2.6.6rc1 for external modules?
Date: Mon, 19 Apr 2004 22:58:17 +0200	[thread overview]
Message-ID: <20040419205817.GA2090@mars.ravnborg.org> (raw)
In-Reply-To: <200404191956.53184.arekm@pld-linux.org>

On Mon, Apr 19, 2004 at 07:56:52PM +0200, Arkadiusz Miskiewicz wrote:

[Please send kbuild related stuff to me. Roman is not kbuild maintainer].

> On 2.6.5 this works fine (/usr/src/linux is read only and make mrproper'ed):
> 
> ln -sf %{_kernelsrcdir}/config-up .config
> install -d include/{linux,config}
> ln -sf %{_kernelsrcdir}/include/linux/autoconf-up.h include/linux/autoconf.h
> ln -sf %{_kernelsrcdir}/include/asm-%{_arch} include/asm
> touch include/config/MARKER
> %{__make} -C %{_kernelsrcdir} scripts modules \
>         SUBDIRS=$PWD \
>         O=$PWD \
>         V=1

The way to build modules are now:

cd $KERNELSRCDIR
make
make clean

cd $MODULEDIR
make -C KERNELSRCDIR M=$PWD

This will work even with MODVERSIONING turned on.

There is currently a glitch that requires you to have defined
at least one module in the kernel. net/dummy for example.
When next round of patched are in you will not need to build the full kernel either.

If you do not want (cannot) build the kernel in the $KERNELSRCDIR
then you can use:

cd $KERNELSRCDIR
copy config-up ~/build
make O=~/build
make O=~/build clean

cd $MODULEDIR
make -C KERNELSRCDIR O=~/build M=$PWD


Hope this clarifies it.

	Sam

  reply	other threads:[~2004-04-19 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 17:56 build system broken in 2.6.6rc1 for external modules? Arkadiusz Miskiewicz
2004-04-19 20:58 ` Sam Ravnborg [this message]
2004-04-19 21:07   ` Arkadiusz Miskiewicz
2004-04-21  8:45     ` Axel Weiß
  -- strict thread matches above, loose matches on Subject: below --
2004-04-21 10:43 sam

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=20040419205817.GA2090@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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