From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [denzil][meta-ti] Problems building compiler for Pandaboard
Date: Thu, 09 Aug 2012 11:57:19 -0600 [thread overview]
Message-ID: <5023F9FF.10204@mlbassoc.com> (raw)
In-Reply-To: <2803677.9qrQhhpNF3@helios>
On 2012-08-09 11:36, Paul Eggleton wrote:
> On Thursday 09 August 2012 11:32:21 Gary Thomas wrote:
>> On 2012-08-09 11:26, Luke A. Guest wrote:
>>> Can anybody help me get started with this? I've only been able to build
>>> an qemux86 image so far which is not that useful for real boards.
>>
>> Try cleaning out your build tree (remove sstate-cache/ and tmp/) and run
>> it again. The error you are seeing is related to reusing the same tree
>> with [somewhat] different target machines.
>
> Sharing build directory between disparate machines should be perfectly
> allowable, if there are failures that block it we should fix them. I'm not sure
> what this specific failure is caused by though.
I see this problem a lot when updating my master tree and trying
to rebuild. Sadly, once it happens, it's hard to reproduce and
I never know when it will bite me.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-08-09 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 17:26 [denzil][meta-ti] Problems building compiler for Pandaboard Luke A. Guest
2012-08-09 17:32 ` Gary Thomas
2012-08-09 17:36 ` Paul Eggleton
2012-08-09 17:57 ` Gary Thomas [this message]
2012-08-10 14:53 ` Luke A. Guest
2012-08-10 14:58 ` Gary Thomas
2012-08-11 15:08 ` Luke A. Guest
2012-08-12 5:41 ` Khem Raj
2012-08-14 22:56 ` Luke A. Guest
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=5023F9FF.10204@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.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.