From: Keith Owens <kaos@ocs.com.au>
To: kbuild-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Announce: Kernel Build for 2.5, Release 2.3 is available
Date: Wed, 01 May 2002 23:53:12 +1000 [thread overview]
Message-ID: <20199.1020261192@ocs3.intra.ocs.com.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Release 2.3 of kernel build for kernel 2.5 (kbuild 2.5) is available.
http://sourceforge.net/projects/kbuild/, package kbuild-2.5, download
release 2.3.
kbuild-2.5-core-9.bz2.
Changes from core-8.
Handle Config.help as well as Configure.help.
Track config changes for generated .[is] files.
kbuild-2.5-common-2.5.12-1.bz2.
Changes from common-2.5.10-2.
Upgrade to kernel 2.5.12.
Add Config.help entries for kbuild 2.5.
Force uname date to LANG=C.
Clean up logic for finding the initial .config.
Add installable target tftpboot.img.
kbuild-2.5-i386-2.5.12-1.bz2.
Changes from i386-2.5.10-1.
Upgrade to kernel 2.5.12.
kbuild-2.5-sparc64-2.5.12-1.bz2
Originally a patch by Tom Duffy against 2.5.11. There were no arch
Makefile changes from 2.5.11 to 2.5.12 and a quick build on sparc64
found no problems so I used the 2.5.11 sparc64 patch for 2.5.12.
Because sparc64 does not compile in 2.5.1[12] (even using the old
kernel build), you need some extra sparc64 patches. Read the patch
for details.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE8z/NGi4UHNye0ZOoRAiutAJ9Qz7PY0/X2hy4Lv+bHEl2nyOpKhQCg2VN1
zrhRk2PHILEvpBFQT2raQp0=
=aSHw
-----END PGP SIGNATURE-----
next reply other threads:[~2002-05-01 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 13:53 Keith Owens [this message]
2002-05-02 16:45 ` Nick Sanders
2002-05-03 8:38 ` Keith Owens
2002-05-03 8:51 ` Keith Owens
2002-05-03 9:18 ` Nick Sanders
2002-05-03 10:08 ` Keith Owens
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=20199.1020261192@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®