From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: llvm issue
Date: Fri, 16 Nov 2012 11:12:41 +0100 [thread overview]
Message-ID: <50A61199.3010309@nedap.com> (raw)
In-Reply-To: <20121116092221.GA6265@mi.fu-berlin.de>
On 11/16/2012 10:22 AM, Henning Heinold wrote:
> On Thu, Nov 15, 2012 at 03:06:30PM +0100, Jaap de Jong wrote:
>> Hi All,
>>
>> 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/llvm2.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/llvm2.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/llvm2.9_2.9.bb
>>
>> Anyone already know what is wrong here?
>>
>> Cheers!
>> Jaap
> Hi Jaap,
>
> khem posted some patches for the jdk7 branch unfornatly I dont have the much time
> to integrate them yet. Please look at the oe-dev patchwork or use his github repo.
So what would be the combination to go?
1) openembedded-core --> danny
2) meta-java --> khem: openjdk-7
Or something different?
>
> Maybee in christmas holiday I will find some time to merge jdk7 branch into master.
Sitting next to your Christmas tree! :-)
next prev parent reply other threads:[~2012-11-16 10:26 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
2012-11-16 9:22 ` Henning Heinold
2012-11-16 10:12 ` Jaap de Jong [this message]
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=50A61199.3010309@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