From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: 'bitbake opie-image' problem
Date: Tue, 9 Mar 2010 12:52:17 -0000 (GMT) [thread overview]
Message-ID: <25809.193.195.44.178.1268139137.squirrel@webmail12.pair.com> (raw)
In-Reply-To: <f275a9df1003090417s3ea8bcf5y3b547ce7303d5e32@mail.gmail.com>
Jiason Li wrote:
> I was trying to make some images followed the getting_started guide,
> 'bitbake nano', 'bitbake console-image' all succeeded,
> but soon I encountered problem when doing 'bitbake opie-image'.
>
> Do you have any idea about this issue?
This is due to libopkg's C headers having changed recently. Not only has
the API changed, but the headers are now uncompilable within a C++
program. I am in the process of fixing this, hopefully I will have some
patches done this evening.
Cheers,
Paul
next prev parent reply other threads:[~2010-03-09 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 12:17 'bitbake opie-image' problem Jiason Li
2010-03-09 12:52 ` Paul Eggleton [this message]
2010-03-09 14:20 ` Jiason Li
2010-03-17 23:40 ` Paul Eggleton
2010-03-18 16:14 ` Bernhard Guillon
2010-03-23 2:18 ` Jiason Li
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=25809.193.195.44.178.1268139137.squirrel@webmail12.pair.com \
--to=bluelightning@bluelightning.org \
--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