All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Kramer <robk@starhub.net.sg>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake r1090 (env hiding) makes my build fail.
Date: Tue, 25 Nov 2008 09:35:43 +0800	[thread overview]
Message-ID: <ggfkl5$bup$1@ger.gmane.org> (raw)
In-Reply-To: ggdhia$cv4$1@ger.gmane.org

[Re-posted with lines trimmed, sorry if this arrives twice]

Koen Kooi wrote:
> Why not put
> 
> CCACHE=""
> 
> in local.conf?

I just commented out the CCACHE line in bitbake.conf for testing. The result
then is a bit more interesting:

| + do_compile
| +
gcc -isystem/bulk/opt/oe/stable/build-ble-i586/tmp/staging/\
x86_64-linux/include  -O2 -isystem/bulk/opt/oe/stable/build\
-ble-i586/tmp/staging/x86_64-linux/include -o
oe_sha256sum main.c sha256.c
| gcc: error trying to exec 'cc1': execvp: No such file or directory
| gcc: error trying to exec 'cc1': execvp: No such file or directory
NOTE: Task
failed: /bulk/opt/oe/stable/build-ble-i586/tmp/work/\
shasum-native-1.0-r1/temp/log.do_compile.32323

I.e. gcc can't find its backend (which should be
at /usr/lib64/gcc/x86_64-suse-linux/4.3/cc1 on my machine). I can't see in
r1090 what could cause that. "export BB_PRESERVE_ENV=1" doesn't help.

> PS: Is that on a RH (derived) buildhost?

OpenSuse 11, x86_64, building i586..

Cheers!

    Rob




  parent reply	other threads:[~2008-11-25  1:36 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 [this message]
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='ggfkl5$bup$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 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.