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 1.9 is available
Date: Fri, 23 Nov 2001 19:04:03 +1100 [thread overview]
Message-ID: <19293.1006502643@kao2.melbourne.sgi.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Release 1.9 of kernel build for kernel 2.5 (kbuild 2.5) has been
released. http://sourceforge.net/projects/kbuild/, Package kbuild-2.5,
download release 1.9.
kbuild 2.5 currently supports i386 (2.4.15), ia64 and sparc32 (2.4.14)
with sparc64 in progress. ia64, sparc32 and sparc64 patches against
kernel 2.4.15 to follow.
http://marc.theaimsgroup.com/?l=linux-kernel&m=99725412902968&w=2
contains information about the base release.
Changelog:
Upgrade to kernel 2.4.15, this release will also work on kernel 2.5.0.
Rewrite pipelined commands that might fail so make can detect any
failure.
Add $(tmpfile), mainly used in commands that used to be pipelined.
Correct shipped() to handle same source and object directory.
Add missing .tmp cleanups.
Check UTS_ fields for length, KERNELRELEASE must not exceed 64
characters, other UTS_ fields are silenly truncated.
After a failure, tell the user to read the FAQ before sending a bug
report (hi, Richard :).
Some i386 Assembler needs -traditional because of unbalanced ' in
comments.
Correct the link order code. Earlier versions of kbuild 2.5 were
linking vmlinux in the wrong order. Nobody noticed, which shows how
horribly over specified the link order is.
This release does not support CML2, only use it with CML1. CML2
support in progress.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE7/gLxi4UHNye0ZOoRAl/kAJ0UVQLgIY61xcvGYK/1wiVxcQBUywCdEtsl
VQdVd7xdPnbA3IJnCD8+UKY=
=ZtT+
-----END PGP SIGNATURE-----
reply other threads:[~2001-11-23 8:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19293.1006502643@kao2.melbourne.sgi.com \
--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