From: Arjan van de Ven <arjanv@redhat.com>
To: Alistair J Strachan <alistair@devzero.co.uk>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org,
kai@tp1.ruhr-uni-bochum.de
Subject: Re: [RFC] KBUILD 2.5 issues/regressions
Date: 11 Jul 2003 19:47:39 +0200 [thread overview]
Message-ID: <1057945659.5806.8.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200307111840.31225.alistair@devzero.co.uk>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Fri, 2003-07-11 at 19:40, Alistair J Strachan wrote:
> o The state of kbuild in shipped (distribution) kernels must be such that the
> construction of external modules can be done without having to modify the
> shipped kernel-source package.
that is actually not hard; I just did this in a RH rpm like way last
week.
> So far, this matches the behaviour in 2.4. However, in 2.4 you need only do a
> "make dep" (and, I believe, some distros also touch a couple of other files).
you never ever should need to do make dep in distro trees for building
external modules.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-11 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 17:40 Alistair J Strachan
2003-07-11 17:47 ` Arjan van de Ven [this message]
[not found] ` <200307111856.53635.alistair@devzero.co.uk>
[not found] ` <20030711180134.H19709@devserv.devel.redhat.com>
2003-07-11 18:06 ` Alistair J Strachan
2003-07-11 17:57 Alistair J Strachan
2003-11-05 7:10 "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
2003-11-09 10:22 ` Arjan van de Ven
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=1057945659.5806.8.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=alistair@devzero.co.uk \
--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
all inboxes | Powered by JetHome®