You can try adding nographic option to runqemu if you do not need to see graphical output from your image. Alex

#linux #warning #toolchain #bitbake #dunfell

This is optional, enabled by default, and allows easy extraction of patches and other information to one's local disk (no need to go over individual maintainer emails). Signed-off-by: Alexander Kanavi

MIMEBase should not be used directly and results in sending raw binary data without encoding it with base64. Signed-off-by: Alexander Kanavin <alex@...> --- modules/utils/emailhandler.py | 6

The key message is: Command '('sudo', '/home/nikita/yoctoproject/poky/scripts/runqemu-ifup', '1000', '1000', '/home/nikita/yoctoproject/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recip

#linux #warning #toolchain #bitbake #dunfell

Where and how the decision was made? Alex

This addresses the failure with wayland 1.21: | ../wayland-1.21.0/tests/meson.build:2:1: ERROR: Problem encountered: -Dtests=true requires -Dlibraries=true Signed-off-by: Alexander Kanavin <alex@linut

If the change is private to you, then you can make a simple layer and make all the needed modifications there. Is this not possible? Alex <arasilinux1086@...> wrote:

I don't remember any such discussion. If you want this to happen, you are welcome to develop the feature. Alex

I think what should help you is EXCLUDE_FROM_SHLIBS = "1" which disables poking into libraries to auto-generate those dependencies that otherwise cause both qa and dnf errors. Alex

Can you drop insane_skip for a moment and show what errors then happen? Alex

Can you show the recipe that you wrote for the blob? Alex

Python3 isn't directly pulled into the SDK, but is a runtime dependency of other items, such as meson. You can check that by $ bitbake core-image-minimal -g -c populate_sdk and reading/grepping the .d

I need to do additional investigation to give a better answer, but is it possible for the team to start the host python with a full path, e.g. /usr/bin/python3, so that PATH doesn't get in the way? Al

It would help if you explain what the problems are. Generally things are tested together with the python provided from yocto, so if you use tooling from the host, you might run into other problems. Al

Then you should look at something like ROOTFS_POSTPROCESS_COMMAND, which runs an extensible set of functions after the rootfs for a target image has been formed through package install in do_rootfs. A

I'd say it's better to modify the original recipe, can you do that? Alex <JoseAntonio.Cardenas@...> wrote:

You can do this with a postinst scriptlet, or with an image post processing task, but generally this looks like a hack regardless of how you do it. What is the file for, and why does it need to be rep

It helps if you can share the recipe that you're trying to build. Alex

#bitbake #toolchain #rust #kirkstone

Hello Philip, when would the time slots be allocated? It doesn't look optimal to leave this to the last minute, as people need to plan their day. Alex

Accessing the network is not allowed from do_compile, or any other task for that matter. You need to provide every needed item in SRC_URI and rely on standard fetchers to form a complete source tree.