From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libepoxy: Use native python3
Date: Thu, 23 Jul 2015 16:38:40 -0600 [thread overview]
Message-ID: <55B16CF0.80405@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0Lb41pKOft88tttTNE-47wDekSbSUbYyUWT12WydtKgaCw@mail.gmail.com>
On 2015-07-23 16:33, Burton, Ross wrote:
>
> On 23 July 2015 at 01:22, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
> This recipe needs python3. This patch arranges to use the bitbake-built
> version, not the host version (which may be missing or not work...)
>
>
> Needs is a strong word. The configure script does this:
>
> AC_CHECK_PROGS([PYTHON], [python3 python2 python])
>
>
> What's actually happening as a patch to simply remove python3 from that list will also solve most problems - we obviously depend on a fully working host python 2.
Well for me, the configure script ended up chosing python3,
even when I used 'pythonnative' (i.e. python2) in the recipe.
I could not get it to build any other way.
Since python3-native will most likely already be built, what's
the harm in doing it this way?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-07-23 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 0:22 [PATCH] libepoxy: Use native python3 Gary Thomas
2015-07-23 22:33 ` Burton, Ross
2015-07-23 22:38 ` Gary Thomas [this message]
2015-07-23 22:42 ` Burton, Ross
2015-07-23 23:00 ` Gary Thomas
2015-07-23 23:06 ` Richard Purdie
2015-07-23 23:15 ` Gary Thomas
2015-07-24 7:52 ` Richard Purdie
2015-07-24 14:45 ` Gary Thomas
2015-07-24 15:01 ` Gary Thomas
2015-07-24 15:08 ` Burton, Ross
2015-07-24 16:18 ` Gary Thomas
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=55B16CF0.80405@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.