Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rob Kramer <robk@starhub.net.sg>
To: openembedded-devel@openembedded.org
Subject: Update: Bitbake r1090 (env hiding) makes my build fail.
Date: Thu, 11 Dec 2008 18:20:10 +0800	[thread overview]
Message-ID: <ghqphb$kt0$1@ger.gmane.org> (raw)
In-Reply-To: ggd81q$re5$1@ger.gmane.org

Hia,

After several hours of hunting, the problem (for stable branch) comes down
to this: there needs to be an 'export PATH' in one of the config files,
otherwise my host compiler fails in the previously stated manner (calling
it explicitly as /usr/bin/gcc also works). The .dev trunk has the export in
bitbake.conf.

Even with the export, I still get screwy ccache behaviour, but if I just add
a CCACHE = "" then all is well.

Cheers,

    Rob


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?
> 
> Cheers!
> 
>     Rob





      parent reply	other threads:[~2008-12-11 10:24 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
2008-11-24 17:57     ` Mike (mwester)
2008-11-25  1:35     ` Rob Kramer
2008-12-11 10:20 ` Rob Kramer [this message]

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='ghqphb$kt0$1@ger.gmane.org' \
    --to=robk@starhub.net.sg \
    --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