<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hey Jens,<br>
</p>
<br>
<div class="moz-cite-prefix">On 09/10/2018 11:58 PM, Jens Rehsack
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0EC3E010-56C9-4EB4-90B4-FD9A68F99AAC@netbsd.org">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Am 10.09.2018 um 23:33 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="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Hey Jens,</p>
<p class=""><br class="">
</p>
<p class="">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.</p>
</div>
</div>
</blockquote>
<div>In that case, uuid for target never gets deployed, but it
is. And I didn't see any packaging issues for `python3` nor
for `nativesdk-python3`</div>
</div>
</blockquote>
<br>
<br>
I don't see what that has to do with anything, fixing the native
build should not affect what gets deployed on target, thats exactly
why we have a manifest, so they user can decide what to install and
what not to install.<br>
I know you didn't see any packaging issues, but that doesn't mean
they don't exist, just from the log I showed you, I can tell you
that the python3-crypt package is not created correctly, for
example, if you do:<br>
<br>
IMAGE_INSTALL_append = " python3-crypt"<br>
<br>
Boot the image, run python3 and you try to import sha3, it will
fail, because the sha3*.so library won't be on the filesystem.<br>
<br>
<br>
And thats because the sha3.*.so library was just introduced in this
upgrade, and our manifest isn't aware it exists, hence it'll end up
on python3-misc and you have just created an unnecessary dependency
from python3-crypt to python3-misc (and worse, a dependency which
were not even aware of, until we test it manually), which beats the
whole purpose of the manifest.<br>
<br>
The do_package function is not gonna fail just because, so you won't
see errors, but the files will be packaged incorrectly, causing
runtime errors as a consequence, the create_manifest task tries to
solve these runtime issues before they happen.<br>
<br>
Cheers,<br>
<br>
Alejandro<br>
<br>
<br>
<blockquote type="cite"
cite="mid:0EC3E010-56C9-4EB4-90B4-FD9A68F99AAC@netbsd.org">
<div>
<blockquote type="cite" class="">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">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>
</div>
</div>
</blockquote>
Please check the submission.</div>
</blockquote>
<br>
I did, its not checking inside recipe-sysroot-native.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:0EC3E010-56C9-4EB4-90B4-FD9A68F99AAC@netbsd.org">
<div><br class="">
</div>
<div>Jens<br class="">
<blockquote type="cite" class="">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Alejandro<br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 09/10/2018 02:05 PM, Jens
Rehsack wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:F9FC0A02-BAE6-45CB-A38D-7AE4E39E5587@netbsd.org"
class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
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 class=""><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"
moz-do-not-send="true">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"
moz-do-not-send="true">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"
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"
moz-do-not-send="true">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"
moz-do-not-send="true">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space; line-break:
after-white-space;" class="">
<div style="letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
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 class="">
</div>
-- <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>
</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="">
</blockquote>
<br>
</body>
</html>