Re: [PATCH] libepoxy: Use native python3

[Gary Thomas <gary@mlbassoc.com>]

On 2015-07-23 17:06, Richard Purdie wrote:
> On Thu, 2015-07-23 at 17:00 -0600, Gary Thomas wrote:
>> It's an old host (Fedora 13) that I am unable to upgrade, but it still
>> works quite well.  I get around most of the Yocto/bitbake worries by
>> using a Yocto-built meta-toolchain to fill in the blanks (correct make,
>> python2, etc), but python3 is not part of the meta-toolchain :-(
>
> You could likely build a customised meta-toolchain which did contain
> python3 though?

Do you know how I would make that happen?  For me, meta-toolchain is
a black box - I know very little of the internals.

Question about policy: it seems that a good many "native" packages
are built, many just to "level the playing field".   I just checked
and one of my average builds has 148 native packages sitting there.
For example, why build bison-native when my host's bison is even the
same vintage and hence just as adequate?  Why then, draw the line
over python3 in this one recipe?  (Just asking, I'll figure out how
to fix this anyway)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------