From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: yocto@yoctoproject.org
Subject: Re: Bitbake requires Python 2.7.3
Date: Fri, 28 Jun 2013 11:29:01 +0100 [thread overview]
Message-ID: <13073341.mysd8saUrS@helios> (raw)
In-Reply-To: <CANyK_8d7jphmfZq2Pz5hp=jJ_OZ_c5PU67angHeZY5PZ55BqLw@mail.gmail.com>
Hi Paul,
On Friday 28 June 2013 11:16:14 Paul Barker wrote:
> On 28 June 2013 10:40, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> > 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).
>
> Just chiming in to say that sounds excellent. Will this contain a
> known-working make as well for those with a broken make 3.82?
A patch has recently been merged to do exactly this, yes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-28 10:29 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
2013-06-28 10:16 ` Paul Barker
2013-06-28 10:29 ` Paul Eggleton [this message]
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=13073341.mysd8saUrS@helios \
--to=paul.eggleton@linux.intel.com \
--cc=paul@paulbarker.me.uk \
--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.