From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: error expanding variable do_*
Date: Tue, 21 Aug 2012 14:29:48 +0100 [thread overview]
Message-ID: <1631931.9ZRM3ET91W@helios> (raw)
In-Reply-To: <CAOHjBZvqMsh4nENivZWfrGUb9sXBLE58CfacjZp5U1LWBorGAw@mail.gmail.com>
On Tuesday 21 August 2012 15:15:42 Giuseppe Condorelli wrote:
> Hi,
>
> today I restarted to work on my own OE meta layer and, after having pulled
> last two months changes is OE-Core, I was able to
> build nothing.
> This is the error I met
>
> [****]$ bitbake core-image-minimal
> Pseudo is not present but is required, building this first before the main
> build
> NOTE: Error expanding variable do_unpack | ETA:
> 00:00:04
> NOTE: Error during finalise of
> /oelinux/condorg/openembedded-core/meta/recipes-sato/web/web_git.bb
> ERROR: Unable to parse
> /oelinux/condorg/openembedded-core/meta/recipes-sato/web/web_git.bb
> ERROR: Command execution failed: Exited with 1
>
> I tried with bitbake version 1.15.2 and 1.15.3, the latest two versions.
> What about the "Error expanding variable do_unpack?" I've read something in
> previous message on mailing list
> but with no understanding.
This is almost certainly because of the whitespace changes in python
functions. If you use master of OE-Core, you must use BitBake 1.15.3+; if you
use denzil, you need to use 1.15.2. I'm a bit confused as to how you could
have still got this error with 1.15.2 though since that change was not in that
version (unless you are using master of OE-Core with BitBake 1.15.2).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-21 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 13:15 error expanding variable do_* Giuseppe Condorelli
2012-08-21 13:29 ` Paul Eggleton [this message]
2012-08-21 13:52 ` Giuseppe Condorelli
2012-08-21 14:29 ` Paul Eggleton
2012-08-22 9:39 ` Giuseppe Condorelli
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=1631931.9ZRM3ET91W@helios \
--to=paul.eggleton@linux.intel.com \
--cc=giuseppe.condorelli@gmail.com \
--cc=openembedded-core@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