All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Bitbake requires Python 2.7.3
Date: Fri, 28 Jun 2013 10:40:21 +0100	[thread overview]
Message-ID: <76247853.lJbnn8TcbK@helios> (raw)
In-Reply-To: <14A8E2D5-FF50-4903-A839-806D77B12FF8@keylevel.com>

Hi Chris,

On Friday 28 June 2013 09:55:42 Chris Tapp wrote:
> I'm experimenting with meta-fsl-arm and I need to use 'master' for some of
> the latest updates. However, when I build I get told that "Bitbake requires
> Python 2.7.3".
> 
> My development system is Ubuntu 11.10, which only has 2.7.2 (and is out of
> support, so no updates!) and the "latest" "Quick Start" manual simply says
> that 2.7 is required.
> 
> Is 2.7.3 now a hard requirement (in which case the documentation could do
> with a minor change), or is the version test being too specific?

It is now a requirement, yes (as are git >= 1.7.5 and tar >= 1.24). As I 
understand it a documentation update is queued to cover this.

FWIW, for older hosts where installing these tools in the normal fashion is 
difficult or impractical, there is now buildtools-tarball (which replaces and 
extends the old external-python-tarball). This builds on the relocatable SDK 
installer to provide suitable versions of python, git, tar and other tools 
required on the build host. I believe the plan is to offer this for download so 
that people can get started immediately (and of course point to this in the 
documentation).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2013-06-28  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28  8:55 Bitbake requires Python 2.7.3 Chris Tapp
2013-06-28  9:06 ` ChenQi
2013-06-28 16:35   ` Chris Tapp
2013-06-28  9:40 ` Paul Eggleton [this message]
2013-06-28 10:16   ` Paul Barker
2013-06-28 10:29     ` Paul Eggleton
2013-06-28 10:53     ` Burton, Ross
2013-06-28 17:03       ` Mark Hatle
2013-06-28 17:07         ` Burton, Ross
2013-07-04  2:48       ` Trevor Woerner
2013-07-04  8:18         ` Burton, Ross
2013-06-28 10:25   ` Rifenbark, Scott M

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=76247853.lJbnn8TcbK@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=opensource@keylevel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.