From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake r1090 (env hiding) makes my build fail.
Date: Sun, 23 Nov 2008 22:54:00 -0600 [thread overview]
Message-ID: <492A3368.4070302@dls.net> (raw)
In-Reply-To: <ggd81q$re5$1@ger.gmane.org>
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.
Oddly enough, now ccache seems to work fine, and I can troubleshoot no
further.
Try messing about with ccache -- disable it, or clean the caches out,
and see if anything will help. Or you can just do what I did, and
disable it by brute force (rename the hosts' ccache binary).
Mike (mwester)
next prev parent reply other threads:[~2008-11-24 4:57 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) [this message]
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
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=492A3368.4070302@dls.net \
--to=mwester@dls.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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