there is system integration testing that happens on autobuilders which you can check reports for ptests are generic and one can add more to a package but usually you will see that its trying to run th

#systemd #yocto

minimal image is not ideal target as it is console only image perhaps use core-image-weston (wayland) or core-image-x11/core-image-sato ( X11 ) as starting point.

#yocto

find if docs can be disabled during build, and perhaps that will get you moving forward

#yocto

Yes, it lets you build custom Linux distribution and eases the way to add needed customization that one might require.

Usually these errors pop up when qemu usermode fails to run the needed programs during cross build. check the logs thoroughly and see if it leaves traces when executing update_icon_cache of any such i

#yocto

please use https://github.com/riscv/riscv-openjdk fork.

ensure that you are using same release branches for all layer repos generally RDEPENDS and RRECOMMENDS should be replaced with RDEPENDS_<pkgname> etc.

#kernel

Please try backporting this fix https://sourceware.org/git/?p=elfutils.git;a=commit;h=a01938d584b91e747167bb4b3f30ec300c4d6e43 if this is not enough then I think you just need to edit config/eu.am to

this class is provided by meta-oe layer. Make sure you have meta-oe layer in your bblayers.conf > >

#yocto

x11-* features is primarily to control what kind of x11 packages you want to include in image e.g. ./meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb is pulled in when x11-sato is added t

you will need python3 in image IMAGE_INSTALL+= "python3" might be minimally needed. > >

#raspberrypi

5.4 recipe has been dropped from oe-core Signed-off-by: Khem Raj <raj.khem@...> --- ...-Keep-rk3288-tinker-SD-card-IO-power.patch | 31 ------------------- recipes-kernel/linux/linux-yocto_5.4.bb

Signed-off-by: Khem Raj <raj.khem@...> --- conf/machine/include/rk3066.inc | 2 +- conf/machine/include/rk3188.inc | 2 +- conf/machine/include/rk3288.inc | 2 +- conf/machine/include/rk3328.inc |

keep in mind that based upon how many vcores you allocate to VM will determine memory pressure as well. So if you have 2 cores perhaps 4GB is ok or maybe even 4 cores might workout ok but some bigger

#yocto #dunfell

how much DRAM is allocated.

#yocto #dunfell

This is not an inert change can it use some mingw specific override as well

Look at kernel kconfig options that should be enabled here https://cgit.freedesktop.org/systemd/systemd/tree/README#n38

<alex.kanavin@...> wrote: Interesting, outside AB we build extended world on musl and it works well. systemd porters usually port the patches as needed for musl yes, I think thats a fair point,

https://github.com/openembedded/meta-openembedded/blob/dunfell/meta-multimedia/conf/layer.conf#L34 says it works with dunfell releases and depends on core and meta-python layers. So I wonder what rele

Please report the problems to mailing list and we can try to help if they do not work with musl. We do support systemd/musl combination and try to keep it working this will limit testing this combinat