Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Python2.7.2 compatibility
Date: Mon, 16 Jan 2012 09:00:52 +0100	[thread overview]
Message-ID: <873008982550291386@unknownmsgid> (raw)
In-Reply-To: 4f13d827.8b7a0e0a.2808.ffffe10eSMTPIN_ADDED@mx.google.com

Hi All, I've read the OE-Classic repository will be stopped and alla the
new work will be on OE-Core one. Can you confirm this? If so, I'll have to
move my work on a given layer in this new developing tree. Please let me
know.
Best Regards,
Giuseppe


Inizio messaggio inoltrato:

*Da:* Giuseppe CONDORELLI <giuseppe.condorelli@st.com>
*Data:* 16 gennaio 2012 08:56:20 CET
*A:* <giuseppe.condorelli@gmail.com>
*Oggetto:* *FW: [oe] [OE] Python2.7.2 compatibility*



-----Original Message-----

From: openembedded-devel-bounces@lists.openembedded.org

[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of

Paul Eggleton

Sent: Wednesday, December 28, 2011 6:04 PM

To: Giuseppe Condorelli

Cc: openembedded-devel@lists.openembedded.org

Subject: Re: [oe] [OE] Python2.7.2 compatibility


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


_______________________________________________

Openembedded-devel mailing list

Openembedded-devel@lists.openembedded.org

http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


       reply	other threads:[~2012-01-16  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f13d827.8b7a0e0a.2808.ffffe10eSMTPIN_ADDED@mx.google.com>
2012-01-16  8:00 ` Giuseppe Condorelli [this message]
2012-01-16 19:18   ` Python2.7.2 compatibility Tom Rini
2012-01-17  8:20     ` Giuseppe Condorelli
2011-12-28 15:43 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

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=873008982550291386@unknownmsgid \
    --to=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