From: Keith Owens <kaos@ocs.com.au>
To: kbuild-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Date: Tue, 09 Apr 2002 23:08:35 +1000 [thread overview]
Message-ID: <29447.1018357715@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 08 Apr 2002 22:04:54 +1000." <3127.1018267494@ocs3.intra.ocs.com.au>
New core, common and ia64 code for kbuild 2.5 is available in
http://sourceforge.net/project/showfiles.php?group_id=18813&release_id=83065
Changes from core-2 to core-3.
Ensure that database records are aligned. Do not assume that keys
are aligned (all the world is not a 386).
Changes from common-2.4.18-1 to common-2.4.18-2.
Minor changes to common code to suit ia64.
New, ia64-020226-2.4.18-1.
core-3 works on ia64, it should work on other architectures that have
alignment requirements such as sparc.
Other architecture maintainers can use core-3 and common-2.4.18-2 as a
starting point for porting this release of kbuild 2.5 to their
architecture. The existing arch patches from Release 1.12 are a good
starting point, ia64 was almost unchanged from Release 1.12 to 2.0.
I have not tested any of the kbuild 2.5 code on big endian machines.
It should work as is but it would be nice to have it confirmed.
next prev parent reply other threads:[~2002-04-09 13:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 11:26 Keith Owens
2002-04-06 2:03 ` Keith Owens
2002-04-06 16:35 ` Russell King
2002-04-06 23:12 ` Keith Owens
2002-04-06 18:17 ` Larry McVoy
2002-04-07 14:18 ` Roman Zippel
2002-04-07 14:28 ` Keith Owens
2002-04-07 14:51 ` Roman Zippel
2002-04-07 14:53 ` Keith Owens
2002-04-07 15:38 ` Roman Zippel
2002-04-07 23:35 ` [kbuild-devel] " Brendan J Simon
2002-04-08 8:50 ` Keith Owens
2002-04-08 9:06 ` Roman Zippel
2002-04-08 12:04 ` Keith Owens
2002-04-09 13:08 ` Keith Owens [this message]
2002-04-09 19:00 ` [kbuild-devel] " Thomas Duffy
2002-04-10 1:11 ` Keith Owens
2002-04-10 11:48 ` Keith Owens
2002-04-14 13:23 ` Keith Owens
2002-04-16 1:58 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-04-06 7:20 Keith Owens
2002-04-07 0:51 ` Keith Owens
[not found] <p73k7rms6ba.fsf@oldwotan.suse.de.suse.lists.linux.kernel>
[not found] ` <7853.1018011163@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 14:37 ` Andi Kleen
2002-04-05 14:52 ` Keith Owens
[not found] <7022.1018005968@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 12:01 ` Andi Kleen
2002-04-05 12:52 ` Keith Owens
2002-04-05 13:29 ` Russell King
2002-04-05 14:33 ` Keith Owens
2002-04-05 10:59 Keith Owens
2002-04-05 11:09 ` Pavel Machek
2002-04-05 11:23 ` Sebastian Heidl
2002-04-05 18:25 ` Mike Fedyk
2002-04-06 18:31 ` Peter Samuelson
2002-04-08 16:16 ` Matthias Andree
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=29447.1018357715@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®