<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hey Jens,</p>
<p><br>
</p>
<p>As I explained before, when you create a manifest for python
(target), it uses the native build as base (it literally runs the
native python that was just built), it is assumed its the same
version as target and contains all the modules provided by
upstream, otherwise the missing modules cannot be checked for
dependencies, and the manifest becomes incoherent, so its not an
option to have an incomplete python native build.<br>
</p>
<p><br>
</p>
<p>Yes you probably need a patch to look at the correct directories
for the h files, as well as a dependency to make the h files
available on recipe-sysroot-native.</p>
<p>Alejandro<br>
</p>
<br>
<div class="moz-cite-prefix">On 09/10/2018 02:05 PM, Jens Rehsack
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F9FC0A02-BAE6-45CB-A38D-7AE4E39E5587@netbsd.org">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hey Alejandro,
<div class=""><br class="">
</div>
<div class="">I fixed that for cross-compile only, since I would
need add a patch and a dependency python3-native for one thing:
calculate uuids.</div>
<div class="">When you can explain to me why the python-native
needs that, I'll change that from -target & nativesdk to
all.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class="">Jens<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Am 10.09.2018 um 22:17 schrieb Alejandro
Enedino Hernandez Samaniego <<a
href="mailto:alejandro.enedino.hernandez-samaniego@xilinx.com"
class="" moz-do-not-send="true">alejandro.enedino.hernandez-samaniego@xilinx.com</a>>:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hey Jens,<br class="">
<br class="">
The compilation log for python3-native still shows that
it didn't build the uuid module<br class="">
<br class="">
<br class="">
Python build finished successfully!<br class="">
The necessary bits to build these optional modules were
not found:<br class="">
_uuid<br class="">
<br class="">
Please look at my previous reply to find how this can be
solved (its likely a missing DEPENDS).<br class="">
<br class="">
<br class="">
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:<br
class="">
<br class="">
<br class="">
| ERROR:<br class="">
| The following files are repeated (contained in more
than one package),<br class="">
| this is likely to happen when new files are introduced
after an upgrade,<br class="">
| please check which package should get it,<br class="">
| modify the manifest accordingly and re-run the
create_manifest task:<br class="">
|
${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_blake2.*.so<br
class="">
|
${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_sha3.*.so<br
class="">
|
${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_contextvars.*.so<br
class="">
| ${libdir}/python${PYTHON_MAJMIN}/contextvars.py<br
class="">
|
${libdir}/python${PYTHON_MAJMIN}/__pycache__/contextvars.*.pyc<br
class="">
|
${libdir}/python${PYTHON_MAJMIN}/lib-dynload/_queue.*.so<br
class="">
<br class="">
<br class="">
Cheers,<br class="">
<br class="">
<br class="">
Alejandro<br class="">
<br class="">
<br class="">
On 09/10/2018 09:38 AM, Burton, Ross wrote:<br class="">
<blockquote type="cite" class="">One thing to be aware
of is that I've been fixing up Python's PGO<br
class="">
support and there's a slew of patches in master-next
and more just<br class="">
posted that this needs to be rebased on top of. Good
news is that my<br class="">
patches remove two of the patches we've been carrying!<br
class="">
<br class="">
Ross<br class="">
<br class="">
On 10 September 2018 at 17:36, Jens Rehsack <<a
href="mailto:sno@netbsd.org" class=""
moz-do-not-send="true">sno@netbsd.org</a>> wrote:<br
class="">
<blockquote type="cite" class=""><br class="">
Am 10.09.2018 um 11:35 schrieb Alexander Kanavin
<<a href="mailto:alex.kanavin@gmail.com" class=""
moz-do-not-send="true">alex.kanavin@gmail.com</a>>:<br
class="">
<br class="">
Large parts of dnf and friends have been rewritten
in c++. I have not<br class="">
yet updated and reviewed that, that will happen in
the next cycle.<br class="">
<br class="">
<br class="">
If I can prepare something for you - drop me a note.<br
class="">
Otherwise - the perl-5.28 update ("." in @INC, regex
buffer overflow, ...)<br class="">
is also<br class="">
awaiting some progress (I can keep "myself" busy).<br
class="">
<br class="">
There's already enough disruption to deal with
(postinsts errors,<br class="">
openssl 1.1, both caused by me :)<br class="">
<br class="">
<br class="">
You know, corner, ash, ... things happen. But there
is progress! Great!<br class="">
<br class="">
Good that we got all the way to do_rootfs though
with 3.7.<br class="">
<br class="">
<br class="">
Yeah, but than came postinst (coreutils :P) :D<br
class="">
<br class="">
Cheers<br class="">
<br class="">
Alex<br class="">
<br class="">
2018-09-10 0:38 GMT+02:00 Tim Orling <<a
href="mailto:ticotimo@gmail.com" class=""
moz-do-not-send="true">ticotimo@gmail.com</a>>:<br
class="">
<br class="">
I did not review the patches closely, but I did try
to build<br class="">
core-image-full-cmdline with the tip of poky and
these patches applied.<br class="">
Everything was fine until do_rootfs... I've attached
the log.<br class="">
<br class="">
Essentially, there are some bits of dnf and so on
which are not ready for<br class="">
Python 3.7. We have dnf version 2.7.5, but the
latest upstream release is<br class="">
3.4.0 (with a 3.5.0 just 3 days ago). Not sure yet
if that would have<br class="">
helped.<br class="">
<br class="">
--<br class="">
_______________________________________________<br
class="">
Openembedded-core mailing list<br class="">
<a
href="mailto:Openembedded-core@lists.openembedded.org"
class="" moz-do-not-send="true">Openembedded-core@lists.openembedded.org</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br
class="">
<br class="">
<br class="">
--<br class="">
Jens Rehsack - <a class="moz-txt-link-abbreviated" href="mailto:rehsack@gmail.com">rehsack@gmail.com</a><br class="">
<br class="">
<br class="">
--<br class="">
_______________________________________________<br
class="">
Openembedded-core mailing list<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br
class="">
<br class="">
</blockquote>
</blockquote>
<br class="">
-- <br class="">
_______________________________________________<br
class="">
Openembedded-core mailing list<br class="">
<a
href="mailto:Openembedded-core@lists.openembedded.org"
class="" moz-do-not-send="true">Openembedded-core@lists.openembedded.org</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
<div class="">-- </div>
<div class="">Jens Rehsack - <a
href="mailto:rehsack@gmail.com" class=""
moz-do-not-send="true">rehsack@gmail.com</a></div>
</div>
</div>
</div>
<br class="">
</div>
</blockquote>
<br>
</body>
</html>