From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: llvm issue
Date: Fri, 16 Nov 2012 09:24:43 +0100 [thread overview]
Message-ID: <50A5F84B.6080501@nedap.com> (raw)
In-Reply-To: <50A5F00A.9050703@nedap.com>
On 11/16/2012 08:49 AM, Jaap de Jong wrote:
> On 11/15/2012 04:25 PM, Paul Eggleton wrote:
>> On Thursday 15 November 2012 15:06:30 Jaap de Jong wrote:
>>> when I checkout openjdk-7 on meta-java and bitbake <anything> I get
>>> these errors:
>>>
>>> ERROR: Unable to parse
>>> /data/jenkins/jobs/myTest/workspace/sources/meta-java/recipes-core/llvm/llvm
>>> 2.9_2.9.bb
>>> | ETA: 00:00:15
>>>
>>> ERROR: Command execution failed: Exited with 1
>>> NOTE: Error expanding variable populate_packages
>>> NOTE: Error during finalise of
>>> /data/jenkins/jobs/myTest/workspace/sources/meta-java/recipes-core/llvm/llvm
>>> 2.8_2.8.bb NOTE: Error expanding variable populate_packages
>>> NOTE: Error during finalise of
>>> /data/jenkins/jobs/myTest/workspace/sources/meta-java/recipes-core/llvm/llvm
>>> 2.9_2.9.bb
>> Are you using the denzil branch of OE-Core perhaps? I suspect meta-java has
>> been updated to use spaces for python function indentation which only works
>> with danny/master. I don't see a denzil branch in meta-java, perhaps it would
>> be worth adding one...?
> Yes, I'm using denzil.
> And for you second question: I'm probably not the one who should answer
> this, but: yes, that would help!
> What would be the way to use the 'danny' branch? I don't see any branch
> of that name under sources/*/
about danny:
cd sources/openembedded-core
git checkout danny
Unfortunately: same problem...
next prev parent reply other threads:[~2012-11-16 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 14:06 llvm issue Jaap de Jong
2012-11-15 15:25 ` Paul Eggleton
2012-11-16 7:49 ` Jaap de Jong
2012-11-16 8:24 ` Jaap de Jong [this message]
2012-11-16 9:22 ` Henning Heinold
2012-11-16 10:12 ` Jaap de Jong
2012-11-16 11:06 ` Henning Heinold
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=50A5F84B.6080501@nedap.com \
--to=jaap.dejong@nedap.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox