mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Axel Weiß" <aweiss@informatik.hu-berlin.de>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: build system broken in 2.6.6rc1 for external modules?
Date: Wed, 21 Apr 2004 10:45:03 +0200	[thread overview]
Message-ID: <200404211045.03547.aweiss@informatik.hu-berlin.de> (raw)
In-Reply-To: <200404192307.31059.arekm@pld-linux.org>

Am Montag, 19. April 2004 23:07 schrieb Arkadiusz Miskiewicz:
> Dnia Monday 19 of April 2004 22:58, Sam Ravnborg napisał:
> > 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.
>
> Great but with 2.6.5 kernel (2.6.4, too. previous probably too) I was able
> to build modules without need to build the full kernel.
>
> > 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
>
> This will start building kernel for me! I don't want that. I want only few
> external modules to be built.

If you are interested, I will send you a brief Makefile for compiling external 
modules. It works on a clean kernel source tree without compiling the whole 
kernel.

Regards,
Axel
-- 
Humboldt-Universität zu Berlin
Institut für Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Weiß
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050


  reply	other threads:[~2004-04-21  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 17:56 Arkadiusz Miskiewicz
2004-04-19 20:58 ` Sam Ravnborg
2004-04-19 21:07   ` Arkadiusz Miskiewicz
2004-04-21  8:45     ` Axel Weiß [this message]
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=200404211045.03547.aweiss@informatik.hu-berlin.de \
    --to=aweiss@informatik.hu-berlin.de \
    --cc=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®