From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 1.1 is available.
Date: Sun, 12 Aug 2001 11:21:22 +1000 [thread overview]
Message-ID: <4736.997579282@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 11 Aug 2001 15:02:55 MST." <20010811150255.G4657@cpe-24-221-152-185.az.sprintbbd.net>
On Sat, 11 Aug 2001 15:02:55 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>On Sun, Aug 12, 2001 at 01:03:00AM +1000, Keith Owens wrote:
>
>> Changes from Release 1.
>[snip]
>> Document kbuild targets and C to assembler conversions. As always,
>> Documentation/kbuild/kbuild-2.5.txt is your friend.
>
>Okay, I've played with this a bit on PPC, and got it working to boot :)
>Now here's what I see as the slight problems with it. At least on PPC
>what we do is generate the offset bits, and then have another file,
>arch/ppc/kernel/ppc_asm.h include that file and have some other useful
>macros for .S files. So any of the .S files which include ppc_asm.h
>would need an additional
>extra_aflags(foo.o $(src_includelist /arch/$(ARCH)))
That will be required for all asm code that includes offsets.h, on all
architectures, I doubt there will be more than 10 on any arch.
The alternative of having code in some arch directory updating
include/asm-$(ARCH)/offsets.h is worse. It is a terrible design to
have code in one makefile updating files in another directory. It is a
layer violation which is always a bad idea.
next prev parent reply other threads:[~2001-08-12 1:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 15:03 Announce: Kernel Build for 2.5, Release 1.1 is available Keith Owens
2001-08-11 15:20 ` Russell King
2001-08-11 16:03 ` Keith Owens
2001-08-11 16:08 ` Philip Blundell
2001-08-11 16:14 ` Russell King
2001-08-11 21:35 ` [kbuild-devel] " Tom Rini
2001-08-11 21:55 ` Roman Zippel
2001-08-12 1:17 ` Keith Owens
2001-08-11 22:02 ` [kbuild-devel] " Tom Rini
2001-08-12 1:21 ` Keith Owens [this message]
2001-08-12 1:44 ` Tom Rini
2001-08-12 14:36 ` David Woodhouse
2001-08-12 14:48 ` Keith Owens
2001-08-12 14:56 ` David Woodhouse
2001-08-12 14:56 ` Russell King
2001-08-13 2:23 ` Keith Owens
2001-08-12 2:24 ` Keith Owens
2001-08-12 4:30 ` Keith Owens
2001-08-19 7:13 ` Richard Henderson
[not found] <20010811212051.A819@jaquet.dk>
2001-08-12 2:11 ` Keith Owens
2001-08-12 2:27 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-08-12 7:31 [kbuild-devel] " Rasmus Andersen
2001-08-12 7:44 ` Keith Owens
2001-08-12 7:57 ` Daniel T. Chen
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=4736.997579282@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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