All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/2] Build fixes
Date: Thu, 5 Nov 2009 11:37:41 -0500	[thread overview]
Message-ID: <20091105163741.GA3983@caradoc.them.org> (raw)
In-Reply-To: <m38welc5ed.fsf@neno.mitica>

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.

> > Also, your changes to $(QEMU_PROG) and recurse-all are not necessary;
> 
> before recurse-all is necesary, because the sub-targets use
> config-host.h (they don't use config-all-devices.h, but it don't hurt to
> also generate it).

Oh, you're right.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2009-11-05 16:37 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 [this message]
2009-11-05 16:47       ` Juan Quintela
2009-11-11  3:07         ` Paul Brook
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=20091105163741.GA3983@caradoc.them.org \
    --to=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.