see how xorg.conf is defined for different qemu based machines in xserver-xf86-config recipe [1] [1] https://git.yoctoproject.org/poky/tree/meta/recipes-graphics/xorg-xserver/xserver-xf86-config > >

Few things comes to mind. You could deploy the systemd unit fragment strategy https://wiki.archlinux.org/title/systemd#Drop-in_files so any customizations you have could be done via these drop-ins and

<alex.kanavin@...> wrote: I have something like this on yoe/mut branch on contrib repo ( due to musl removing the LFS hacks). However there are packages which need to be fixed at build time. thi

This is true and it happens because they all provide something commonly, perhaps virtual/libc or somesuch. However, each one of them does not replace exact providers so they must match for one to over

<poornesh.g@...> wrote: always look into layerindex for available packages. A search for realmd reveals that there is no recipe for it. So you have to write one https://layers.openembedded.or

#zeus

.config should be in build tree of u-boot, when you do bitbake u-boot, please look into the builddir of u-boot under work folder

On Tue, Nov 29, 2022 at 10:07 AM Vaijayanthi via lists.yoctoproject.org <vaijayanthi=silver-peak.com@...> wrote: what are benefits of having separate recipes for them? I would say c

#yocto

Look into the logs in the rootfs build area and it might reveal the underlying problem perhaps some missing library or qemu user mode crash could be the reason

#dunfell

I should have said libedit and not editline

you can also look into replacing readline with editline and see if this would work for your package needs. That will be one less package needed from meta-gpl2

<zoran.stojsavljevic@...> wrote: yes that will do it. Infact thats what poky-altconfig does largely as well. see https://git.yoctoproject.org/poky/tree/meta-poky/conf/distro/poky-altcfg.conf#n11

If you are using poky then ssytemd is not default init system, its sysvinit. For enabling systemd its best to start with DISTRO = "poky-altcfg" <vdeshpande@...> wrote:

Try something like https://git.openembedded.org/meta-openembedded/commit/?h=master-next

#yocto

lgtm

Looks ok perhaps you want to double check using lnr we have dropped its usage in master but I am not sure if hardknott needs it or not. I would simily use ln -sf test ${D}/usr/bin/test-x and avoid usi

https://docs.yoctoproject.org/migration-guides/migration-4.0.html?highlight=network#fetching-changes https://git.yoctoproject.org/poky/commit/?id=23ac8859f4f336dead2264f320a382d696b48370

yes cmake has the downloader module which perhaps is good from development point of view, however, with yocto where one goal is about reproducibility its important to have sourcecode immutable and ens

I was not sure of if it will break some use cases therefore I just wanted to add what works and not delete anything I have not tested

Signed-off-by: Khem Raj <raj.khem@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index a2661f9..0e28857 100644 --- a

Your machine is fine I think bitbake is extremely parallel and that might be issue that it’s eating up all the memory. How many cores does this machine have? And ram ? Usually it’s good to keep 3-4gb