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.3 is available.
Date: Wed, 26 Sep 2001 20:58:48 +1000 [thread overview]
Message-ID: <1470.1001501928@ocs3.intra.ocs.com.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Release 1.3 of kernel build for kernel 2.5 (kbuild 2.5) is available.
http://sourceforge.net/projects/kbuild/, Package kbuild-2.5, download
release 1.3.
http://marc.theaimsgroup.com/?l=linux-kernel&m=99725412902968&w=2
contains information about the base release.
Changes from Release 1.2
Upgrade to kernel 2.4.10.
Split arch/$(ARCH)/Makefile.defs into Makefile.defs.noconfig and
Makefile.defs.config, the latter can only be processed after .config
has been read. i386 and ia64 done, more to come.
arch_core_subdirs is gone, it uses link_subdirs like everything else.
Yet more aic7xxx fixes, I wish that Makefile followed the rules :(.
Changing the number of source trees no longer forces a complete
rebuild. Changing the names of the source tree never forced a
rebuild but adding or deleting a complete tree used to.
Add $(obj_includelist) for generated include files.
Offsets for Assembler code standardized to arch/$(ARCH)/asm-offsets.h.
i386 and ia64 done, more to come.
scripts/shadow.pl to report on which files are shadowed and at which
levels.
Ensure that make install uses the same KERNELRELEASE as the build,
even if root forgets to specify any overrides.
Assorted bug fixes.
Expect a kbuild 2.5 patch for 2.4.9-ia64-010820 in the next few days,
and a patch for 2.4.10-ac after 2.4.10-ac1 is released.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE7sbTmi4UHNye0ZOoRAnM0AJ9xp0JtrolFU8ioWBKmj1HGZ0u79ACfeTLG
MLMOkn824x8+DNnNATZadxU=
=N3b6
-----END PGP SIGNATURE-----
reply other threads:[~2001-09-26 10:59 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=1470.1001501928@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®