The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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.4 is available.
Date: Mon, 08 Oct 2001 17:08:43 +1000	[thread overview]
Message-ID: <3169.1002524923@kao2.melbourne.sgi.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Release 1.4 of kernel build for kernel 2.5 (kbuild 2.5) is available.
http://sourceforge.net/projects/kbuild/, Package kbuild-2.5, download
release 1.34

http://marc.theaimsgroup.com/?l=linux-kernel&m=99725412902968&w=2
contains information about the base release.

Changes from Release 1.3

  Upgrade to kernel 2.4.11-pre5.

  As suggested by Christoph Hellwig, ensure that the kernel does not
  depend on user space include files.

  Yet more aic7xxx fixes, I wish that Makefile followed the rules :(.

  Expand $(ARCH) in pp_makefile, reduces special cases.

  Tweaks to arch/i386/asm-offsets.h.

  vmlinux.lds* (linkage editor scripts) are now called vmlinux.lds.S
  (input) and vmlinux.lds.i (post-processed output, input to linker).
  Using .S and .i let me plug it into the full dependency system
  instead of being a special case.

  Add expsyms() for several objects that are not in 2.4 export-objs.

  Add -DEXPORT_SYMTAB for expsyms(), to check for entries missing from
  expsyms().

  Add CONFIG_KBUILD_2_5, always defined for kbuild 2.5.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE7wVD5i4UHNye0ZOoRAo+nAKC9DqTKD/79PB38doGgG+d4nUTWBQCgvqgi
FYmuheRQX9iw2RCQg0/s0ZE=
=R5en
-----END PGP SIGNATURE-----


                 reply	other threads:[~2001-10-08  7:08 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=3169.1002524923@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