xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] stubdom: disable parallel build
Date: Tue, 31 Jul 2012 10:44:08 +0200	[thread overview]
Message-ID: <20120731084408.GA9850@aepfle.de> (raw)
In-Reply-To: <1343723296.15432.62.camel@zakaz.uk.xensource.com>

On Tue, Jul 31, Ian Campbell wrote:

> On Mon, 2012-07-30 at 17:35 +0100, Olaf Hering wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1343666089 -7200
> > # Node ID ccbebdbe44da0460408172338af9daab31e56788
> > # Parent  db8adce4f09307a90f96103f7fd67efa97fc9ac0
> > stubdom: disable parallel build
> > 
> > Recently I changed my rpm xen.spec file from doing
> > 'make -C tools -j N && make stubdom' to 'make -j N stubdom' because
> > stubdom depends on tools, so both get built.
> > The result was the failure below.
> 
> I always do -j12 builds of the stubdom sub=tree and I don't see
> parallelisation issues. The stubdom build is pretty big and time
> consuming so it would be a shame to needlessly linearise it.

Is it always a clean build?
For me nothing in stubdom is built in parallel, if I interpret the
repated output of 'ps fax' right.

Olaf

> > make[2]: *** INTERNAL: readdir: Bad file descriptor
> 
> This is an internal error inside make? That's surely more critical than
> any problem with our build system and needs to be solved before adding
> workarounds to our tree.

Perhaps there is an issue, yes. I will see if I find something.

Olaf

  reply	other threads:[~2012-07-31  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 16:35 [PATCH] stubdom: disable parallel build Olaf Hering
2012-07-31  8:28 ` Ian Campbell
2012-07-31  8:44   ` Olaf Hering [this message]
2012-07-31  8:50     ` Ian Campbell
2012-07-31  9:06       ` Olaf Hering
2012-07-31  9:17   ` Olaf Hering
2012-07-31 12:50   ` Olaf Hering
2012-08-01 11:26     ` Ian Campbell
2012-08-01 12:18       ` Olaf Hering

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=20120731084408.GA9850@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).