linux-kernel.vger.kernel.org archive mirror
 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: Re: Announce: Kernel Build for 2.5, Release 2.4 is available
Date: Thu, 09 May 2002 21:45:39 +1000	[thread overview]
Message-ID: <19760.1020944739@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 04 May 2002 23:01:17 +1000." <24512.1020517277@ocs3.intra.ocs.com.au>

On Sat, 04 May 2002 23:01:17 +1000, 
Keith Owens <kaos@ocs.com.au> wrote:
>Release 2.4 of kernel build for kernel 2.5 (kbuild 2.5) is available.
>http://sourceforge.net/projects/kbuild/, package kbuild-2.5, download
>release 2.4.

Extra architecture support added to release 2.4:

  kbuild-2.5-ppc-2.5.14-1.bz2 from Paul Mackerras
  kbuild-2.5-sparc64-2.5.14-1.bz2 from Tom Duffy
  kbuild-2.5-sh-2.5.12-1.bz2 from Greg Banks

  Read the start of each patch for special instructions.

kbuild-2.5-core-12.bz2 added to release 2.4

  Changes from core-11.

    Verify that KBUILD_OBJTREE points to an objtree directory during
    make clean/mrproper.  Old object trees will get a warning,
      echo "must not be empty" > $KBUILD_OBJTREE/_objtree
    to mark old objtrees, only needed once.

    Change message when switching from normal mode to NO_MAKEFILE_GEN
    mode, document why the switch requires additional processing.

    Fix standardization of file names in commands.

    pp_ programs are compiled with -O2 -NDEBUG=1.

    Tune database layout to improve speed, especially for small builds.
    The new database format requires and will force a complete rebuild.


  parent reply	other threads:[~2002-05-09 11:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 14:19 Keith Owens
2002-05-03 14:37 ` your mail tomas szepe
2002-05-03 15:07   ` tomas szepe
2002-05-03 15:29   ` Keith Owens
2002-05-03 15:45     ` tomas szepe
2002-05-03 15:57       ` kbuild 2.5 release 2.4 Keith Owens
2002-05-03 16:41         ` tomas szepe
2002-05-04 10:58           ` tomas szepe
2002-05-04 11:24             ` Keith Owens
2002-05-04 11:26               ` Zwane Mwaikambo
2002-05-04 12:11                 ` Keith Owens
2002-05-04 11:58                   ` Zwane Mwaikambo
2002-05-04 16:21                     ` rddunlap
2002-05-04 11:39               ` tomas szepe
2002-05-04 12:00                 ` Keith Owens
2002-05-04 12:15                   ` tomas szepe
2002-05-04 16:19                     ` rddunlap
2002-05-04 16:29                       ` Tomas Szepe
2002-05-04 16:30                         ` rddunlap
2002-05-05  2:27                       ` Keith Owens
2002-05-04 13:01 ` Announce: Kernel Build for 2.5, Release 2.4 is available Keith Owens
2002-05-06  6:27   ` Keith Owens
2002-05-07 17:47     ` [kbuild-devel] " Thomas Duffy
2002-05-09 11:45   ` Keith Owens [this message]
2002-05-10  1:46     ` Thomas Duffy
2002-05-10  3:21       ` Keith Owens
2002-05-11  9:32   ` Keith Owens
2002-05-14  0:12     ` [kbuild-devel] " Thomas Duffy
2002-05-14  2:44       ` Keith Owens
2002-05-14  5:44     ` Keith Owens
2002-05-15  3:46       ` [kbuild-devel] " Thomas Duffy
2002-05-15 13:20         ` Keith Owens
2002-05-17  4:07           ` 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=19760.1020944739@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;
as well as URLs for NNTP newsgroup(s).