From: sam@ravnborg.org
To: "Axel Weiß" <aweiss@informatik.hu-berlin.de>
Cc: linux-kernel@vger.kernel.org, Arkadiusz Miskiewicz <arekm@pld-linux.org>
Subject: Re: build system broken in 2.6.6rc1 for external modules?
Date: Wed, 21 Apr 2004 12:43:33 +0200 (CEST) [thread overview]
Message-ID: <20040421104333.B646015C30@post1.dk> (raw)
>> 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.
With the patch that went into -rc2-mm1 there is no longer a need
to build the full kernel.
Previously kbuild required the Module.symvers file to be present,
but with the latest patch this requirement is relaxed.
Sam
next reply other threads:[~2004-04-21 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 10:43 sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-19 17:56 build system broken in 2.6.6rc1 for external modules? Arkadiusz Miskiewicz
2004-04-19 20:58 ` Sam Ravnborg
2004-04-19 21:07 ` Arkadiusz Miskiewicz
2004-04-21 8:45 ` Axel Weiß
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=20040421104333.B646015C30@post1.dk \
--to=sam@ravnborg.org \
--cc=arekm@pld-linux.org \
--cc=aweiss@informatik.hu-berlin.de \
--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