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 07:55:48 -0500 [thread overview]
Message-ID: <492AA454.20009@balister.org> (raw)
In-Reply-To: <ggdhia$cv4$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Koen Kooi wrote:
> On 24-11-08 05:54, Mike (mwester) wrote:
>> Rob Kramer wrote:
>>> Hia,
>>>
>>> I'm tracking the stable branch and recently updated bitbake to HEAD.
>>> When
>>> trying a build-from-scratch, I noticed BB quickly failed in
>>> shasum-native.
>>> Some manual svn disecting pointed to r1090 as the one that caused the
>>> fail.
>>> I tried adding a BB_PRESERVE_ENV, but no difference.
>>>
>>> Output is at http://pastebin.com/m65e66603. There is no log.do_compile
>>> generated for some reason, and a build with -D shows nothing much.
>>> The gcc
>>> invoke actually works OK and produces the oe_shasum256 executable.
>>>
>>> Any ideas what could be wrong with my setup?
>>
>> You've gotten further than I have in tracking this down! Good find in
>> pointing the finger of suspicion on the env hiding stuff.
>>
>> There have been a number of folks who have encountered this problem --
>> including me, at one point. I struggled with it, determined it was
>> ccache that was messing up, and at that point I took the easy way out
>> and just renamed the /usr/bin/ccache binary to get my builds running
>> again.
>
> 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.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-11-24 12:58 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 [this message]
2008-11-24 13:08 ` Leon Woestenberg
2008-11-24 13:14 ` Philip Balister
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=492AA454.20009@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 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.