From: Christian Zander <zander@minion.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Christian Zander <zander@minion.de>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Mark Fasheh <mark.fasheh@oracle.com>,
Thomas Schlichter <schlicht@uni-mannheim.de>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: no version magic, tainting kernel.
Date: Mon, 27 Jan 2003 01:24:17 +0100 [thread overview]
Message-ID: <20030127002417.GK394@kugai> (raw)
In-Reply-To: <31172.1043622971@passion.cambridge.redhat.com>
On Sun, Jan 26, 2003 at 11:16:11PM +0000, David Woodhouse wrote:
>
> There are some differences, but nothing insurmountable.
>
> For <=2.4 you have to include Rules.make at the end of your own
> Makefile, and for 2.5 that file doesn't exist any more.
>
> For older kernels you must set O_TARGET, for 2.5 I think the mere
> act of setting it causes the build to break -- that one is
> gratuitously making it harder to make external modules which compile
> in both and I've complained about it before.
>
> Per-file CFLAGS must have a full path specified now in 2.5, whereas
> in 2.4 and earlier it was just 'CFLAGS_filename.o'.
>
Thanks for pointing that out, I'll look into this more closely. If it
is as simple as you say, I'll be inclined to share your sentiment
towards custom build systems interfacing with the Linux kernel.
--
christian zander
zander@minion.de
next prev parent reply other threads:[~2003-01-26 23:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 13:59 no version magic, tainting kernel Thomas Schlichter
2003-01-23 16:29 ` Randy.Dunlap
2003-01-23 16:52 ` Sam Ravnborg
2003-01-23 17:32 ` Thomas Schlichter
2003-01-23 18:22 ` Sam Ravnborg
2003-01-23 19:35 ` Mark Fasheh
2003-01-26 13:29 ` Christian Zander
2003-01-26 13:33 ` Keith Owens
2003-01-26 18:02 ` Kai Germaschewski
2003-01-26 17:51 ` Kai Germaschewski
2003-01-26 21:57 ` Christian Zander
2003-01-26 21:46 ` Kai Germaschewski
2003-01-26 23:12 ` Christian Zander
2003-01-26 22:55 ` David Woodhouse
2003-01-27 0:07 ` Christian Zander
2003-01-26 23:16 ` David Woodhouse
2003-01-27 0:24 ` Christian Zander [this message]
2003-01-27 16:25 ` Kai Germaschewski
2003-01-27 16:29 ` David Woodhouse
2003-01-27 16:39 ` Kai Germaschewski
2003-01-27 6:17 ` Petr Vandrovec
2003-01-27 9:02 ` David Woodhouse
2003-01-27 9:24 ` Petr Vandrovec
2003-01-27 17:59 ` Joel Becker
2003-01-27 18:31 ` Kai Germaschewski
2003-01-27 22:15 ` Joel Becker
2003-01-27 23:08 ` Kai Germaschewski
2003-01-27 23:37 ` Joel Becker
2003-01-28 15:43 ` David Woodhouse
2003-01-28 17:03 ` Joel Becker
2003-01-26 22:23 ` Christian Zander
2003-01-26 17:43 ` Kai Germaschewski
2003-01-26 22:08 ` Christian Zander
2003-01-26 21:29 ` Sam Ravnborg
2003-01-26 23:03 ` Christian Zander
2003-01-26 21:40 ` David Woodhouse
2003-01-26 23:28 ` Christian Zander
2003-01-26 22:46 ` David Woodhouse
2003-01-26 23:56 ` Christian Zander
2003-01-26 23:04 ` David Woodhouse
2003-01-28 1:58 ` Rusty Russell
2003-01-28 19:10 ` Mark Fasheh
2003-01-28 19:17 ` Kai Germaschewski
2003-01-27 18:52 ` Jerry Cooperstein
2003-01-27 19:12 ` Sam Ravnborg
2003-01-27 19:35 ` Jerry Cooperstein
2003-01-27 19:54 ` Gerd Knorr
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=20030127002417.GK394@kugai \
--to=zander@minion.de \
--cc=dwmw2@infradead.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=rddunlap@osdl.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=schlicht@uni-mannheim.de \
/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