Re: [PATCH] libepoxy: Use native python3

[Gary Thomas <gary@mlbassoc.com>]

On 2015-07-24 08:45, Gary Thomas wrote:
> On 2015-07-24 01:52, Richard Purdie wrote:
>> On Thu, 2015-07-23 at 17:15 -0600, Gary Thomas wrote:
>>> 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.
>>
>> Personally, I'd probably use "buildtools-tarball" for this so I'd go and
>> edit the buildtools-tarball.bb file and add nativesdk-python3-modules to
>> it which should pull in the bulk of python3 (not sure if you'd need
>> nativesdk-python3-core too, I'd hope that would be automatic from the
>> other).
>
> Sadly, this failed:
> | Objects/obmalloc.o: In function `_PyObject_DebugMallocStats':
> | obmalloc.c:(.text+0x1793): undefined reference to `pool_is_in_list'
> | collect2: error: ld returned 1 exit status
> | make: *** [Parser/pgen] Error 1
> | make: *** Waiting for unfinished jobs....
> | ERROR: oe_runmake failed
> | ERROR: Function failed: do_compile (log file is located at
> /local/p0382-cutting-edge_2014-11-21/tmp/work/i686-nativesdk-amltdsdk-linux/nativesdk-python3/3.4.3-r1.0/temp/log.do_compile.27165)
> ERROR: Task 163 (virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-devtools/python/python3_3.4.3.bb, do_compile) failed with exit code '1'

It seems that python3 doesn't like being built without Py_DEBUG set.
I worked through that only to find this additional error:

Collected errors:
  * satisfy_dependencies_for: Cannot satisfy the following dependencies for nativesdk-python3-modules:
  *      nativesdk-python3-robotparser *
  * opkg_install_cmd: Cannot install package nativesdk-python3-modules.

>
>>
>> You prefer your meta-toolchain? Then set:
>> TOOLCHAIN_HOST_TASK_append = " nativesdk-python3-modules"
>> in local.conf and it should add python3 to all meta-toolchain builds.
>>
>>> 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)
>>
>> The line is drawn over python. Bitbake is built with python (2 at the
>> moment, 3 in the future) and since we need python to run bitbake,
>> rebuilding it seems silly. Yes, we do need to build a python-native to
>> be able to build python (target) which is sad but such is the nature of
>> cross compiling. We therefore tend to assume the provided python(s) are
>> sane.
>

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