The same builds are included in a-full, so they tend to get queued up and cause delays in builds completion, as there's only a single worker allocated to them. Let's run them less frequently to mitiga

The right way would be to fix the recipe I think? What is doing that has to happen only on target and can't be done during do_rootfs? Alex

What recipe is it and what layer is it in? Alex

Right, I guess my usage of 'you' was ambiguous. It was not targeted at you specifically, my apologies for that. Alex

It should always be at the end of string, otherwise something like "/usr/bin/python3.9-config 123" will erroneously match against priority 9. Signed-off-by: Alexander Kanavin <alex.kanavin@...>

I am not complaining or bragging. I only want to set expectations, in public, and clearly. Otherwise some people will treat the project contributors as their unpaid contractors, and get upset when hel

I guess some people or companies somehow felt entitled to Tim doing continuing python2 layer support for them in a particularly annoying way, and this was a reality check for them. We are all voluntee

You should make a new image recipe, and define what goes into it there. Alex

I feel that porting from an older Yocto release to a newer one is not the best approach. The delta can be very large, and it can be very painful and time consuming to handle it all at once. By the tim

#yocto

Virgl only has been verified with Mesa, if your bsp provides something else for virtual/libgl, it is not going to work. Please ask your bsp supplier (Nvidia I guess?) what to do. Alex

It helps if you can show the recipe, and the git repo of the library. Alex

Michael Halstead has confirmed this. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/auh-config/upgrade-helper.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --gi

In some situation this may happen in initial builds and should not be treated as an error. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- modules/buildhistory.py | 11 ++++++++++- 1 file

The module was doing a lot of things, none of which are necessary: - setting up a separate buildhistory repo for each recipe - running cleansstate before doing initial build - messing about with build

The best is to ask your BSP supplier to provide a new version of the BSP that is compatible with recent Yocto versions. Backporting userspace stuff is difficult or impossible. Alex

And done, patches sent :) Bonus fix: one of the multilib tests was erroneously always skipped. Alex

binutils-symlinks is only an alias to the main package according to binutils.inc: RPROVIDES_${PN} += "${PN}-symlinks" I didn't write either of the tests, but yes - I can work on this tomorrow. Alex

Previously it was pulled in implicitly via poky default config. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff

Yocto does not provide a gcc that targets the host machine, only the cross gcc, whose output is unsuitable for running at configuration step. Meson assigns different meanings to these, yocto's host is

You probably need to adjust meson.cross which is written out by meson.bbclass. Alex