From: Rusty Trivial Russell <trivial@rustcorp.com.au>
To: Justin Gibbs <gibbs@btc.adaptec.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-scsi@vger.kernel.org, axboe@suse.de
Cc: John Cherry <cherry@osdl.org>
Subject: [TRIVIAL] fix parallel builds for aic7xxx]
Date: Wed, 24 Sep 2003 12:56:01 +1000 [thread overview]
Message-ID: <20030924032922.BE68C2C21F@lists.samba.org> (raw)
[ Sorry, did you guys end up with consensus on this? Should I forward
or drop? Thanks, Rusty ]
From: John Cherry <cherry@osdl.org>
My compile regression scripts were getting random build failures for
aic7xxx. The two makefiles could not handle parallel build.
Occasionally they would succeed...timing dependent. The following two
patches fix this.
Part 1 - drivers/scsi/aic7xxx/Makefile
Part 2 - drivers/scsi/aic7xxx/aicasm/Makefile
John
--- trivial-2.6.0-test5-bk10/drivers/scsi/aic7xxx/Makefile.orig 2003-09-24 12:27:20.000000000 +1000
+++ trivial-2.6.0-test5-bk10/drivers/scsi/aic7xxx/Makefile 2003-09-24 12:27:20.000000000 +1000
@@ -58,7 +58,9 @@
-p $(obj)/aic7xxx_reg_print.c -i aic7xxx_osm.h
ifeq ($(CONFIG_AIC7XXX_BUILD_FIRMWARE),y)
-$(aic7xxx-gen-y): $(src)/aic7xxx.seq $(src)/aic7xxx.reg $(obj)/aicasm/aicasm
+$(aic7xxx-gen-y): $(src)/aic7xxx.seq
+
+$(src)/aic7xxx.seq: $(obj)/aicasm/aicasm $(src)/aic7xxx.reg
$(obj)/aicasm/aicasm -I$(src) -r $(obj)/aic7xxx_reg.h \
$(aicasm-7xxx-opts-y) -o $(obj)/aic7xxx_seq.h \
$(src)/aic7xxx.seq
@@ -72,7 +74,9 @@
-p $(obj)/aic79xx_reg_print.c -i aic79xx_osm.h
ifeq ($(CONFIG_AIC79XX_BUILD_FIRMWARE),y)
-$(aic79xx-gen-y): $(src)/aic79xx.seq $(src)/aic79xx.reg $(obj)/aicasm/aicasm
+$(aic79xx-gen-y): $(src)/aic79xx.seq
+
+$(src)/aic79xx.seq: $(obj)/aicasm/aicasm $(src)/aic79xx.reg
$(obj)/aicasm/aicasm -I$(src) -r $(obj)/aic79xx_reg.h \
$(aicasm-79xx-opts-y) -o $(obj)/aic79xx_seq.h \
$(src)/aic79xx.seq
--- trivial-2.6.0-test5-bk10/drivers/scsi/aic7xxx/aicasm/Makefile.orig 2003-09-24 12:27:20.000000000 +1000
+++ trivial-2.6.0-test5-bk10/drivers/scsi/aic7xxx/aicasm/Makefile 2003-09-24 12:27:20.000000000 +1000
@@ -49,14 +49,18 @@
clean:
rm -f $(clean-files)
-aicasm_gram.c aicasm_gram.h: aicasm_gram.y
+aicasm_gram.c: aicasm_gram.h
+ mv $(<:.h=).tab.c $(<:.h=.c)
+
+aicasm_gram.h: aicasm_gram.y
$(YACC) $(YFLAGS) -b $(<:.y=) $<
- mv $(<:.y=).tab.c $(<:.y=.c)
mv $(<:.y=).tab.h $(<:.y=.h)
-aicasm_macro_gram.c aicasm_macro_gram.h: aicasm_macro_gram.y
+aicasm_macro_gram.c: aicasm_macro_gram.h
+ mv $(<:.h=).tab.c $(<:.h=.c)
+
+aicasm_macro_gram.h: aicasm_macro_gram.y
$(YACC) $(YFLAGS) -b $(<:.y=) -p mm $<
- mv $(<:.y=).tab.c $(<:.y=.c)
mv $(<:.y=).tab.h $(<:.y=.h)
aicasm_scan.c: aicasm_scan.l
--
What is this? http://www.kernel.org/pub/linux/kernel/people/rusty/trivial/
Don't blame me: the Monkey is driving
File: John Cherry <cherry@osdl.org>: [TRIVIAL][PATCH] fix parallel builds for aic7xxx]
next reply other threads:[~2003-09-24 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 2:56 Rusty Trivial Russell [this message]
2003-09-24 12:36 ` [TRIVIAL] fix parallel builds for aic7xxx] Christoph Hellwig
2003-09-24 14:10 ` James Bottomley
2003-09-24 14:39 ` Justin T. Gibbs
2003-09-24 16:21 ` John Cherry
2003-09-26 4:20 ` Rusty Russell
2003-09-26 15:02 ` John Cherry
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=20030924032922.BE68C2C21F@lists.samba.org \
--to=trivial@rustcorp.com.au \
--cc=axboe@suse.de \
--cc=cherry@osdl.org \
--cc=gibbs@btc.adaptec.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-scsi@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