All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libtool: Add missing DEPENDS on libtool-cross
Date: Thu, 04 Oct 2012 13:58:15 +0100	[thread overview]
Message-ID: <1349355495.18301.93.camel@ted> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED10159242C29@DLEE12.ent.ti.com>

On Thu, 2012-10-04 at 12:39 +0000, Maupin, Chase wrote:
> I was able to reproduce this consistently on my build server which has
> 24 cores running at 3.5 GHz.  I was using:
> 
> BB_NUMBER_THREADS = "24"
> 
> And
> 
> PARALLEL_MAKE = "-j 24"
> 
> I can try a build reducing the number of threads and see if the issue
> goes away as this might be a difference between our builds.  Can you
> tell me what you are using?

I tested this with 48/48 in master.

> It seemed like a race condition because after I got the error I was
> able to do a -c cleanall of libtool and kick off the build again once
> libtool-cross was built and it would pass.  Likewise I did:
> 
> bitbake libtool-cross
> bitbake libtool
> 
> and that would work but just
> 
> bitbake libtool
> 
> would fail.

"bitbake libtool" works here quite consistently. I therefore don't want
to add this dependency until we figure out exactly what is racing
against what or have a better understanding of why this is failing.
Something doesn't seem right as if your premise of a missing dependency
is correct, the above wouldn't work.

Cheers,

Richard






  reply	other threads:[~2012-10-04 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 21:30 [PATCH] libtool: Add missing DEPENDS on libtool-cross Chase Maupin
2012-10-04  9:21 ` Richard Purdie
2012-10-04 12:39   ` Maupin, Chase
2012-10-04 12:58     ` Richard Purdie [this message]
2012-10-04 13:02       ` Maupin, Chase
2012-10-04 14:06         ` Maupin, Chase
2012-10-04 14:29           ` Richard Purdie
2012-10-04 15:50             ` Maupin, Chase
2012-10-04 16:10               ` Scott Garman

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=1349355495.18301.93.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chase.maupin@ti.com \
    --cc=openembedded-core@lists.openembedded.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 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.