From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: python3 on build host
Date: Tue, 26 Jul 2016 16:57:20 +0200 [thread overview]
Message-ID: <57977A50.7080102@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LYOYF=czvyC4HzhbuP1zFaQv2jwrXz82tmnoG3rnuxQBg@mail.gmail.com>
On 2016-07-26 16:20, Burton, Ross wrote:
>
> On 26 July 2016 at 15:09, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
> I have a build host that I've used for years. It is not
> possible to [directly] update python3 on this system to
> one which is identified as suitable for use with bitbake.
>
> To try and work around this, I created a meta-toolchain SDK
> for my target. I remember needing to do this years ago when
> one of my boxes also became out of date. Sadly, this process
> has not led me to a solution.
>
> First question: is this the proper way to solve this problem?
> I simply can't update python3 on this box (I've tried), so I
> need another solution so I can continue to use this workhorse.
>
>
> The buildtools-tarball is what you want: you can either build your own (bitbake buildtools-tarball) or just download the
> one we've built for you. This looks like the right one:
>
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/buildtools/poky-glibc-x86_64-buildtools-tarball-core2-64-buildtools-nativesdk-standalone-2.1.sh
>
Yes, this is just what I needed (except I had to build my own because my box is i686)
My bitbake build is now running and it looks like this will work for me.
Thanks
> Second question: even if this is not the correct way to solve my initial problem
> of providing a suitable python3 on my build host, shouldn't I be able to run
> bitbake (or indeed any suitably complex python3 program) using the SDK I installed?
>
>
> Looks like this SDK doesn't actually contain a full copy of Python, just the pieces to make what you have in the SDK
> work (theoretically, at least). This is why we add python3-modules to the buildtools-tarball, so if you want your SDK
> to ship its own complete Py3 runtime then add python3-core python3-modules to it.
What would be the best way to do that?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-07-26 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:09 python3 on build host Gary Thomas
2016-07-26 14:20 ` Burton, Ross
2016-07-26 14:57 ` Gary Thomas [this message]
2016-07-26 15:00 ` Burton, Ross
2016-07-26 20:58 ` 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=57977A50.7080102@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ross.burton@intel.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.