Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake r1090 (env hiding) makes my build fail.
Date: Mon, 24 Nov 2008 08:14:26 -0500	[thread overview]
Message-ID: <492AA8B2.8070101@balister.org> (raw)
In-Reply-To: <c384c5ea0811240508x4d870ac8m2b44679db394755d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

Leon Woestenberg wrote:
> Hello guys,
> 
> On Mon, Nov 24, 2008 at 1:55 PM, Philip Balister <philip@balister.org> wrote:
>> Koen Kooi wrote:
>>> On 24-11-08 05:54, Mike (mwester) wrote:
>>>> Rob Kramer wrote:
>>>>> Hia,
>>> Why not put
>>>
>>> CCACHE=""
>>>
>>> in local.conf?
>>>
>>> regards,
>>>
>>> Koen
>>>
>>> PS: Is that on a RH (derived) buildhost?
>> I had this problem on a RHEL4 machine.
>>
> 
> Q: Did this problem reproduce reliably each time?
> 
> 
> Background: I have seen my builds-from-scratch fail very early as
> well, but it does not reproduce often. In my case, I suspect a
> concurrency issue, i.e. BB_NUMBER_THREADS larger than 1? It fails
> every 1 out of 50 times or so here... I am still tracking that one
> down.

100% failure. Identical symptoms to mwester.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2008-11-24 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24  3:45 Bitbake r1090 (env hiding) makes my build fail Rob Kramer
2008-11-24  4:54 ` Mike (mwester)
2008-11-24  6:28   ` Koen Kooi
2008-11-24 12:55     ` Philip Balister
2008-11-24 13:08       ` Leon Woestenberg
2008-11-24 13:14         ` Philip Balister [this message]
2008-11-24 17:57     ` Mike (mwester)
2008-11-25  1:35     ` Rob Kramer
2008-12-11 10:20 ` Update: " Rob Kramer

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=492AA8B2.8070101@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox