There is a problem with the Yocto recipe for Python 3 in warrior. It
is missing ntpath in the list of core modules listed in
python3-manifest.json.

Since warrior is EOL, I was hoping to fix this by patching the
python3-manifest.json file but it doesn't work. I think the reason is
that the manifest file is read by an anonymous function in the recipe,
which I understand is executed during recipe parsing (which I assume
happens before the patches are applied).

I know the patch is being applied correctly because the content of
python3-manifest.json file is correct when I inspect it in the
build/tmp/work... directory.

My question is whether there is any method in bitbake to apply patches
early enough to fix this issue?

Hello.
I hope you're going well in this period.
I'm working with yocto (zeus version) with a soc i.MX6 and kernel 4.19. Actually, I meet a weird issue about the recipe "qtwebengine" in all of my projects that are using zeus version.
The compilation was working fine until there, but since approximatively two weeks, with no particular reason, whatever the project I want to compile, I'm unable to compile qtwebengine and making a rootfs image with it inside.

So I have tested:

1) bitbake qtwebengine
2) bitbake myimage

PS: myimage contain the recipe qtwebengine.

But whatever the bitbake commands 1 or 2, Bitbake shows me the same error I don't understand and this error follows:

-----------------------------------------------------------------------------------
| In file included from /usr/include/bits/errno.h:26:0,
|                  from /usr/include/errno.h:28,
|                  from /usr/include/c++/7/cerrno:42,
|                  from /usr/include/c++/7/ext/string_conversions.h:44,
|                  from /usr/include/c++/7/bits/basic_string.h:6361,
|                  from /usr/include/c++/7/string:52,
|                  from /usr/include/c++/7/stdexcept:39,
|                  from /usr/include/c++/7/array:39,
|                  from /usr/include/c++/7/tuple:39,
|                  from /usr/include/c++/7/bits/unique_ptr.h:37,
|                  from /usr/include/c++/7/memory:80,
|                  from ../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.h:9,
|                  from ./../../../../git/src/3rdparty/chromium/v8/src/torque/cfg.cc:5,
|                  from v8_snapshot/gen/v8/torque_base_jumbo_1.cc:5:
| /usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory
|  #include <asm/errno.h>
|           ^~~~~~~~~~~~~
| compilation terminated.
...
| Makefile.gn_run:340: recipe for target 'run_ninja' failed
| make[3]: *** [run_ninja] Error 1
| make[3]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed
| make[2]: *** [sub-gn_run-pro-make_first] Error 2
| make[2]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src/core'
| Makefile:76: recipe for target 'sub-core-make_first' failed
| make[1]: *** [sub-core-make_first] Error 2
| make[1]: Leaving directory '/home/yocto/Dev/build_zeus/tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi/qtwebengine/5.13.0+gitAUTOINC+5d4bac57a0_8a28c0bb19-r0/build/src'
| Makefile:48: recipe for target 'sub-src-make_first' failed
| make: *** [sub-src-make_first] Error 2
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/yocto/Dev/build_zeus/../meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile) failed with exit code '1'
-----------------------------------------------------------------------------------

I don't understand why bitbake don't find '<asm/errno.h>', because it is present in the kernel 4.19 and in my host system ubuntu 18. Furthermore, I don't understand the problem with run_ninja.

I try to change my PC for compilation, but I have got the same error. The PC I use to compile with bitbake got 20 cores intel xeon and 32GB of ram. I think the problem is not from here. :-)

Does someone already meet this problem?

Does someone know where could be the problem?

Thanks for all and best reguards: Anthony.

Thanks Andy,

I tried to boot the linux kernel using TFTP/NFS, i got this below error

Hi,
Thanks for the reply,

Yes, that did the trick.

Thanks, Talel

Hi Talel,

On Wed, Nov 11, 2020 at 03:30:33AM -0800, Bel Hadj Salem Talel wrote:

Hi All,

I created two different machines "menzu-console" and "menzu-media"
I have main patch for device tree for both , and only one patch specific for menzu-media machine
So in the linux recipe bbappend I want to set something like this:
SRC_URI += "file://main.patch" # FOR BOTH MACHINES
SRC_URI_menzu-media += "file://media.patch" # FOR menzu-media ONLY

SRC_URI_append_mezu-media = " file://media.patch"
is what you should use.

The issue with your suggestion is that it **replaces** the original
variable iff the recipe is built for menzu-media. What you want is to
append to the variable iff the recipe is built for menzu-media, that's
what the line above does.

Quentin

Hi All,

I created two different machines "menzu-console" and "menzu-media"
I have main patch for device tree for both , and only one patch specific for menzu-media machine
So in the linux recipe bbappend I want to set something like this:
SRC_URI += "file://main.patch" # FOR BOTH MACHINES
SRC_URI_menzu-media += "file://media.patch" # FOR menzu-media ONLY

But this didn't work, only "media.patch" is unpacked and moreover the kernel recipe workdir does not contain a content as if unpack didn't work properly.
How can I do it ?

Thanks, Talel

On Wed, Nov 11, 2020 at 08:39:42AM +0100, Belisko Marek wrote:

On Wed, Nov 11, 2020 at 8:04 AM <Mikko.Rapeli@...> wrote:

Hi,

On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:

Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
| File "setup.py", line 25, in <module>
| from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?

When backporting changes, I find it better to cherry-pick the changes for e.g.
python3 update from master to the old branch that I have to use. In my case I can
not update anything which breaks ABIs on target images but can update all
development tools like python3. Often fixes and/or updates to components which
fail to build are also easy to find from master and cherry-pick, especially if you
don't need to build all recipes from poky but only a certain subset. Over
time this will make your local branch look horrible though, but at least
merges from stable branches will in most cases work, if they are still alive.

Thanks for sharing. But I'm using official poky release from git so I
cannot cherry pick changes.
Or you have clone of poky repo and add changes on top from newest versions?

Locally, as developer you always have a local branch where you can cherry-pick
changes. With git submodules and repo tooling, you should use a local or
project specific clone of poky. Or move all updates and changes to your own
layers, but I find this doesn't scale and instead branching in git works
better.

Cheers,

-Mikko

Hi All,

I'm not trying to export or create a variable inside a recipe because that's easy and not my case.
But I want to create a variable that a user can define in local.conf or in other conf files and a recipe that checks the value of that variable and do some stuff with it like:
python (){
 a = d.getVar('MY_VARIABLE' or '')
}
How can I do this?
Thanks, Talel

On Wed, Nov 11, 2020 at 8:04 AM <Mikko.Rapeli@...> wrote:

Hi,

On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:

Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
| File "setup.py", line 25, in <module>
| from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?

When backporting changes, I find it better to cherry-pick the changes for e.g.
python3 update from master to the old branch that I have to use. In my case I can
not update anything which breaks ABIs on target images but can update all
development tools like python3. Often fixes and/or updates to components which
fail to build are also easy to find from master and cherry-pick, especially if you
don't need to build all recipes from poky but only a certain subset. Over
time this will make your local branch look horrible though, but at least
merges from stable branches will in most cases work, if they are still alive.

Thanks for sharing. But I'm using official poky release from git so I
cannot cherry pick changes.
Or you have clone of poky repo and add changes on top from newest versions?

But like Alex said, using 3.1 dunfell LTS or 3.2 gatesgarth would be better.

Yes but it's not an option for me to do it now ;).

Hope this helps,

-Mikko

Thanks,

Marek

Howdy!

Am Mi., 11. Nov. 2020 um 08:18 Uhr schrieb Robert Berger@...
<robert.berger.yocto.user@...>:
<snip>

So it looks like it's extensible SDK specific.

Can you please try with the "standard" sdk instead of the extensible sdk
to see if this works for you?

<snip>

Tried that. Standard SDK works, it's definitely related to the tasks
of the eSDK.

Greetz

Hi,

And as far as I understand you tried to build some extensible SDK against an x86-64 container.

Please note, that my SDK most likely contains a bit more than the "standard" stuff[0], but this should not make much of a difference here.

[0] https://gitlab.com/meta-layers/meta-resy/-/blob/dunfell/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend

I take a container-x86-64:

bitbake app-container-image-mosquitto-oci [1]

[1] https://pastebin.com/T9hX1H8f

bitbake app-container-image-mosquitto-oci -c populate_sdk [2]

[2] https://pastebin.com/eujc57DG

bitbake app-container-image-mosquitto-oci -c populate_sdk_ext

breaks in a similar way[3]

[3] https://pastebin.com/rV9ewZa9

So it looks like it's extensible SDK specific.

Can you please try with the "standard" sdk instead of the extensible sdk to see if this works for you?

You might want to play with IMAGE_CONTAINER_NO_DUMMY = "1" which is defined in poky/meta/classes/image-container.bbclass and try to build a container with a kernel as a workaround in case you build an eSDK.

Regards,

Robert

Hi,

On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:

Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
| File "setup.py", line 25, in <module>
| from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?

When backporting changes, I find it better to cherry-pick the changes for e.g.
python3 update from master to the old branch that I have to use. In my case I can
not update anything which breaks ABIs on target images but can update all
development tools like python3. Often fixes and/or updates to components which
fail to build are also easy to find from master and cherry-pick, especially if you
don't need to build all recipes from poky but only a certain subset. Over
time this will make your local branch look horrible though, but at least
merges from stable branches will in most cases work, if they are still alive.

But like Alex said, using 3.1 dunfell LTS or 3.2 gatesgarth would be better.

Hope this helps,

-Mikko

Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
| File "setup.py", line 25, in <module>
| from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?

Thanks and BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com