Hey Alejandro,

I fixed that for cross-compile only, since I would need add a patch and a 
dependency python3-native for one thing: calculate uuids.
When you can explain to me why the python-native needs that, I'll change that 
from -target & nativesdk to all.

From my point of view it's not a question of having every (unneeded) python 
module being built for the native python, which is used for cross-compiling 
python and some modules only.

Cheers,
Jens

> Am 10.09.2018 um 22:17 schrieb Alejandro Enedino Hernandez Samaniego 
> <[email protected]>:
> 
> Hey Jens,
> 
> The compilation log for python3-native still shows that it didn't build the 
> uuid module
> 
> 
> Python build finished successfully!
> The necessary bits to build these optional modules were not found:
> _uuid
> 
> Please look at my previous reply to find how this can be solved (its likely a 
> missing DEPENDS).
> 
> 
> Also, this patch is missing the new python3 manifest for this release, there 
> appears to be a few new modules that we need to decide which package they 
> belong to, this is the output of bitbake python3 -c create_manifest:
> 
> 
> | ERROR:
> | The following files are repeated (contained in more than one package),
> | this is likely to happen when new files are introduced after an upgrade,
> | please check which package should get it,
> |  modify the manifest accordingly and re-run the create_manifest task:
> | ${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_blake2.*.so
> | ${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_sha3.*.so
> | ${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_contextvars.*.so
> | ${libdir}/python${PYTHON_MAJMIN}/contextvars.py
> | ${libdir}/python${PYTHON_MAJMIN}/__pycache__/contextvars.*.pyc
> | ${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_queue.*.so
> 
> 
> Cheers,
> 
> 
> Alejandro
> 
> 
> On 09/10/2018 09:38 AM, Burton, Ross wrote:
>> One thing to be aware of is that I've been fixing up Python's PGO
>> support and there's a slew of patches in master-next and more just
>> posted that this needs to be rebased on top of.  Good news is that my
>> patches remove two of the patches we've been carrying!
>> 
>> Ross
>> 
>> On 10 September 2018 at 17:36, Jens Rehsack <[email protected]> wrote:
>>> 
>>> Am 10.09.2018 um 11:35 schrieb Alexander Kanavin <[email protected]>:
>>> 
>>> Large parts of dnf and friends have been rewritten in c++. I have not
>>> yet updated and reviewed that, that will happen in the next cycle.
>>> 
>>> 
>>> If I can prepare something for you - drop me a note.
>>> Otherwise - the perl-5.28 update ("." in @INC, regex buffer overflow, ...)
>>> is also
>>> awaiting some progress (I can keep "myself" busy).
>>> 
>>> There's already enough disruption to deal with (postinsts errors,
>>> openssl 1.1, both caused by me :)
>>> 
>>> 
>>> You know, corner, ash, ... things happen. But there is progress! Great!
>>> 
>>> Good that we got all the way to do_rootfs though with 3.7.
>>> 
>>> 
>>> Yeah, but than came postinst (coreutils :P) :D
>>> 
>>> Cheers
>>> 
>>> Alex
>>> 
>>> 2018-09-10 0:38 GMT+02:00 Tim Orling <[email protected]>:
>>> 
>>> I did not review the patches closely, but I did try to build
>>> core-image-full-cmdline with the tip of poky and these patches applied.
>>> Everything was fine until do_rootfs... I've attached the log.
>>> 
>>> Essentially, there are some bits of dnf and so on which are not ready for
>>> Python 3.7. We have dnf version 2.7.5, but the latest upstream release is
>>> 3.4.0 (with a 3.5.0 just 3 days ago). Not sure yet if that would have
>>> helped.
>>> 
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> [email protected]
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>> 
>>> 
>>> --
>>> Jens Rehsack - [email protected]
>>> 
>>> 
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> [email protected]
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>> 
> 
> --
> _______________________________________________
> Openembedded-core mailing list
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
Jens Rehsack - [email protected]

Attachment: signature.asc
Description: Message signed with OpenPGP

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to