From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Python2.7.2 compatibility
Date: Wed, 28 Dec 2011 17:04 +0000 [thread overview]
Message-ID: <1467608.7NT73FzDoG@helios> (raw)
In-Reply-To: <CAOHjBZtAzdpynVMt6m=ofp6P+Xy9i7=NXaBU2mgT-4uR8MXf4Q@mail.gmail.com>
On Wednesday 28 December 2011 17:57:33 Giuseppe Condorelli wrote:
> This is the log error I catch, I can think it is due to python but maybe
> I'm wrong.
>
> ---------------------------------
> bitbake base-image
> ERROR: There is a comment on line 24 of file
> /home/condorg/work/openembedded/recipes/ekiga/ekiga_git.bb (#
> --enable-static-libs \) which is in the middle of a multiline expression.
> Bitbake used to ignore these but no longer does so, please fix your
> metadata as errors are likely as a result of this change.
OK, this has nothing to do with Python version - you're using a new BitBake
version with the OE classic metadata and the two are not compatible for the
reason shown in the error - comments are no longer allowed within multi-line
expressions.
There are three choices:
a) Switch back to an earlier version of BitBake (e.g. 1.12.x)
b) Move up to OE-Core [1]
c) Go through and fix all of these comments
Cheers,
Paul
[1] http://www.openembedded.org/wiki/OpenEmbedded-Core
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-28 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:43 Python2.7.2 compatibility Giuseppe Condorelli
2011-12-28 15:48 ` Paul Eggleton
2011-12-28 16:57 ` Giuseppe Condorelli
2011-12-28 17:02 ` Chris Larson
2011-12-28 17:04 ` Paul Eggleton [this message]
[not found] <4f13d827.8b7a0e0a.2808.ffffe10eSMTPIN_ADDED@mx.google.com>
2012-01-16 8:00 ` Giuseppe Condorelli
2012-01-16 19:18 ` Tom Rini
2012-01-17 8:20 ` 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=1467608.7NT73FzDoG@helios \
--to=paul.eggleton@linux.intel.com \
--cc=giuseppe.condorelli@gmail.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