linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Duffy <tduffy@directvinternet.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Kbuild Devel <kbuild-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.4 is available
Date: 14 May 2002 20:46:38 -0700	[thread overview]
Message-ID: <1021434398.17954.14.camel@tduffy-lnx.afara.com> (raw)
In-Reply-To: <7875.1021355042@kao2.melbourne.sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Mon, 2002-05-13 at 22:44, Keith Owens wrote:
> On Sat, 04 May 2002 00:19:10 +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.

Just for shits and giggles, I updated kbuild 2.5 for 2.4.19-pre8.

(actually, I did this because sparc32 builds on that kernel and I am
going to start work to get that port underway and wanted a buildable
base to start with)

this patch is just the diff between 2.4.18 and 2.4.19-pre8

0) untar 2.4.18 and apply patch-2.4.19-pre8
1) apply kbuild-2.5-core-14
2) apply kbuild-2.5-common-2.4.18-6
3) apply kbuild-2.5-i386-2.4.18-2
4) then apply kbuild-2.5-common-2.4.19-pre8-update

I have only tested x86 as of this moment.  If anyone is dying for a
clean kbuild-2.5-common-2.4.19-pre8-1, let me know and I can turn those
wheels.  BTW, there are a few things that don't build on this kernel in
kbuild 2.4 as probably already reported on lkml.

-tduffy

[-- Attachment #2: kbuild-2.5-common-2.4.19-pre8-update.bz2 --]
[-- Type: application/x-bzip, Size: 10004 bytes --]

  reply	other threads:[~2002-05-15  3:49 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
2002-05-10  1:46     ` [kbuild-devel] " 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       ` Thomas Duffy [this message]
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=1021434398.17954.14.camel@tduffy-lnx.afara.com \
    --to=tduffy@directvinternet.com \
    --cc=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).