From: Marc Singer <elf@buici.com>
To: Pekka Pietikainen <pp@ee.oulu.fi>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: Support for building individual .ko's would be nice :-)
Date: Tue, 20 Apr 2004 12:16:03 -0700 [thread overview]
Message-ID: <20040420191603.GA25198@buici.com> (raw)
In-Reply-To: <20040420185904.GA27037@ee.oulu.fi>
On Tue, Apr 20, 2004 at 09:59:04PM +0300, Pekka Pietikainen wrote:
> I was told you're the man to bug about this :-)
>
> Having a slow box, a vendor kernel (+ kernel-source package with config
> for it) and a need to modify one line of a module, recompile it,
> replace existing module with it and continue business as usual
> made me notice kbuild doesn't seem to have a facility for this.
>
> What would be nice is (say)
>
> cp configs/xxx-i686.config .config
> emacs drivers/media/dvb/frontends/ves1820.c
> make drivers/media/dvb/frontends/ves1820.ko
> cp ves1820.ko /lib/modules/...
> rmmod ves1820; modprobe ves1820
>
> Or am I missing something obvious that let me get just that one .ko
> without recompiling just about everything? (.o is easy, but that's
> not very useful :-) )
If you leave the compiled tree intact, all you need to do is modify
the one source file and then "make modules". You'll wait a while the
first time, but successive builds will be minimal.
next prev parent reply other threads:[~2004-04-20 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 18:59 Support for building individual .ko's would be nice :-) Pekka Pietikainen
2004-04-20 19:16 ` Marc Singer [this message]
2004-04-20 19:42 ` Sam Ravnborg
2004-04-20 19:57 ` Axel Weiss
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=20040420191603.GA25198@buici.com \
--to=elf@buici.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pp@ee.oulu.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.