All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Thomas Duffy <tduffy@directvinternet.com>
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: Tue, 14 May 2002 12:44:31 +1000	[thread overview]
Message-ID: <6641.1021344271@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "13 May 2002 17:12:08 MST." <1021335128.25750.23.camel@tduffy-lnx.afara.com>

On 13 May 2002 17:12:08 -0700, 
Thomas Duffy <tduffy@directvinternet.com> wrote:
>ok, kbuild-2.5-sparc64-2.5.15-1 is ready.

Does it still need sparc64 hacks or is the base 2.5.15 kernel clean for
sparc64?

>  CC drivers/scsi/aic7xxx/aic7xxx_core.o
>pp_makefile5: stat (drivers/scsi/aic7xxx/aic7xxx_seq.h) failed: No such file or directory
>pp_makefile5: dependencies (pid 15566) returned 1

Did not show up in my testing, it was hidden by out of order compiles
with -j4.  Will be in common-2.5.15-3.

diff -ur 2.5.15-kbuild-2.5/drivers/scsi/aic7xxx/Makefile.in 2.5.15-kbuild-2.5.new/drivers/scsi/aic7xxx/Makefile.in
--- 2.5.15-kbuild-2.5/drivers/scsi/aic7xxx/Makefile.in	Tue May 14 12:38:47 2002
+++ 2.5.15-kbuild-2.5.new/drivers/scsi/aic7xxx/Makefile.in	Tue May 14 12:37:20 2002
@@ -19,9 +19,9 @@
 
 extra_cflags_all($(src_includelist /drivers/scsi))
 
-# Only aic7xxx.c includes aic7xxx_seq.h.
+# Only aic7xxx_core.c includes aic7xxx_seq.h.
 
-$(objfile aic7xxx.o): $(objfile aic7xxx_seq.h)
+$(objfile aic7xxx_core.o): $(objfile aic7xxx_seq.h)
 
 # aic7xxx_reg.h is messy.  It is included by aic7xxx.h which is included by
 # aic7xxx_osm.h which is included by several .c files.  Play safe and make all


  reply	other threads:[~2002-05-14  2:44 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 [this message]
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=6641.1021344271@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tduffy@directvinternet.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.