public inbox for linux-kernel@vger.kernel.org
 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.0 is available
Date: Tue, 16 Apr 2002 11:58:12 +1000	[thread overview]
Message-ID: <11907.1018922292@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 14 Apr 2002 23:23:16 +1000." <2833.1018790596@ocs3.intra.ocs.com.au>

On Sun, 14 Apr 2002 23:23:16 +1000, 
Keith Owens <kaos@ocs.com.au> wrote:
>Updates for kbuild 2.5 at
>http://sourceforge.net/project/showfiles.php?group_id=18813
>kbuild-2.5-i386-2.5.8-pre3-1.bz2

i386-2.5.8-pre3-1 was missing this bit, against i386-2.5.8-pre3-1.
Apply this patch or use kbuild-2.5-i386-2.5.8-pre3-2.bz2.

diff -urN 2.5.8-pre3-kbuild-2.5/arch/i386/kernel/Makefile.in 2.5.8-pre3-kbuild-2.5-save/arch/i386/kernel/Makefile.in
--- 2.5.8-pre3-kbuild-2.5/arch/i386/kernel/Makefile.in	Tue Apr 16 11:09:25 2002
+++ 2.5.8-pre3-kbuild-2.5-save/arch/i386/kernel/Makefile.in	Sun Apr 14 11:45:28 2002
@@ -27,5 +27,11 @@
 
 # uses_asm_offsets(entry.o)
 
+# "Unterminated character constants", due to mismatched ' in comments
+extra_aflags(entry.o -traditional)
 extra_aflags(head.o -traditional)
 extra_aflags(trampoline.o -traditional)
+
+extra_cflags(acpi.o $(fixme_acpi_includes))
+extra_cflags(pci-irq.o $(fixme_acpi_includes))
+extra_cflags(setup.o $(fixme_acpi_includes))


  reply	other threads:[~2002-04-16  1:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 11:26 Announce: Kernel Build for 2.5, Release 2.0 is available Keith Owens
2002-04-06  2:03 ` Keith Owens
2002-04-06 16:35   ` Russell King
2002-04-06 23:12     ` Keith Owens
2002-04-06 18:17   ` Larry McVoy
2002-04-07 14:18 ` Roman Zippel
2002-04-07 14:28   ` Keith Owens
2002-04-07 14:51     ` Roman Zippel
2002-04-07 14:53       ` Keith Owens
2002-04-07 15:38         ` Roman Zippel
2002-04-07 23:35         ` [kbuild-devel] " Brendan J Simon
2002-04-08  8:50   ` Keith Owens
2002-04-08  9:06     ` Roman Zippel
2002-04-08 12:04 ` Keith Owens
2002-04-09 13:08   ` Keith Owens
2002-04-09 19:00     ` [kbuild-devel] " Thomas Duffy
2002-04-10  1:11       ` Keith Owens
2002-04-10 11:48     ` Keith Owens
2002-04-14 13:23     ` Keith Owens
2002-04-16  1:58       ` Keith Owens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-06  7:20 Keith Owens
2002-04-07  0:51 ` Keith Owens
     [not found] <p73k7rms6ba.fsf@oldwotan.suse.de.suse.lists.linux.kernel>
     [not found] ` <7853.1018011163@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 14:37   ` Andi Kleen
2002-04-05 14:52     ` Keith Owens
     [not found] <7022.1018005968@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 12:01 ` Andi Kleen
2002-04-05 12:52   ` Keith Owens
2002-04-05 13:29     ` Russell King
2002-04-05 14:33       ` Keith Owens
2002-04-05 10:59 Keith Owens
2002-04-05 11:09 ` Pavel Machek
2002-04-05 11:23   ` Sebastian Heidl
2002-04-05 18:25     ` Mike Fedyk
2002-04-06 18:31       ` Peter Samuelson
2002-04-08 16:16   ` Matthias Andree

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=11907.1018922292@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