From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] Build fixes
Date: Wed, 11 Nov 2009 03:07:27 +0000 [thread overview]
Message-ID: <200911110307.27227.paul@codesourcery.com> (raw)
In-Reply-To: <m3pr7wyl35.fsf@neno.mitica>
On Thursday 05 November 2009, Juan Quintela wrote:
> Daniel Jacobowitz <dan@codesourcery.com> wrote:
> > On Thu, Nov 05, 2009 at 05:17:46PM +0100, Juan Quintela wrote:
> >> How are you compiling?
> >> It works for me compiling in-tree with make -j3 (only 2 cores)
> >
> > I can reliably reproduce it by building all my QEMU configs at once.
> > I think that's a four-core or eight-core machine, -j4 in each build,
> > six separate qemu build trees. I've reproduced it in a single build
> > tree a couple of times, but not reliably.
>
> I have no way to reproduce reliablely :(
rm -f qemu-tool.[od] config-host.h
make qemu-tool.o
Reproduces reliably.
The following patch should expose any similar failures:
--- a/rules.mak
+++ b/rules.mak
@@ -44,5 +44,6 @@ cc-option = $(if $(shell $(CC) $1 $2 -S -o /dev/null -xc
/dev/
@test -f $@ || cp $< $@
%.h-timestamp: %.mak
+ sleep 60
$(call quiet-command, $(SRC_PATH)/create_config < $< > $@, " GEN
$*.h
@cmp $@ $*.h >/dev/null 2>&1 || cp $@ $*.h
Paul
next prev parent reply other threads:[~2009-11-11 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 13:42 [Qemu-devel] [PATCH 0/2] Build fixes Juan Quintela
2009-11-05 13:42 ` [Qemu-devel] [PATCH 1/2] fix parallel build Juan Quintela
2009-11-05 13:42 ` [Qemu-devel] [PATCH 2/2] fix type in CFLAGS name Juan Quintela
2009-11-05 14:13 ` [Qemu-devel] Re: [PATCH 0/2] Build fixes Daniel Jacobowitz
2009-11-05 16:17 ` Juan Quintela
2009-11-05 16:37 ` Daniel Jacobowitz
2009-11-05 16:47 ` Juan Quintela
2009-11-11 3:07 ` Paul Brook [this message]
2009-11-11 10:28 ` Juan Quintela
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=200911110307.27227.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.