From: Bruce Ashfield <bruce.ashfield@...> Richard, This is a follow on to my oe-core series that drops the 5.4 recipes. I haven't had any issues with 5.10/5.13 in my local testing, but I

This change is prompted by the recent period where musl patches wouldn't even apply to systemd, which broke half of AUH upgrade attempts. You need to enable systemd/musl on the autobuilder matrix

Am So, 15. Aug 2021, um 03:39, schrieb Khem Raj: My bad again. I had the modified layer.conf still in my meta-oe directory, and this prevented kas from switching to the new commit. Fixed this and

Am Sa, 14. Aug 2021, um 12:14, schrieb Robert Berger: Alright, thanks for the info. Did they switch from the underline _ to a colon : as seperator? Guess underline was becoming ambigous. Manuel

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

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

We've all done this sort of thing :-) Looks like another case of the layer's master/honister branch instead of dunfell. Steve

Am Fr, 13. Aug 2021, um 23:59, schrieb Steve Sakoman: I feel like an idiot right now. Thank you! With dunfell it builds indeed. Now I have to deal with the following: ``` ERROR: Layer

There was an OVERRIDE syntax change and this is what are seeing. Some layers, like meta-openembedded incorporated this change into their master branch. So either you need to update all your layers as

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/auh-config/local.conf.append | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

It is not guaranteed to build or work otherwise, and causes update failures in unrelated recipes when building for musl for instance. Signed-off-by: Alexander Kanavin <alex.kanavin@...> ---

Note that you are using the master branch of meta-oe ^^^^^^^^ If you use the dunfell branch you won't have this issue. Steve

I'd like to use a systemd DHCP client feature that became available in v248 in my yocto-hardknott system. Is there any hope of using the complete v249.1 recipe from the oe master branch? Bill

Hello all, I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d Since

Both repos have been added to check-layer-nightly so we need to make sure the dunfell branches of the repos are being used Signed-off-by: Steve Sakoman <steve@...> --- schedulers.py | 2 ++

Hi Daniel, Those commands only add directories, you still need to copy your files to one of those directories. Use for example: install ${S}/path/to/lib.so.x.y ${D}${libdir} Any specific reason for

meta-oe and auh are not for SWAT, change the default to be false Signed-off-by: Alexandre Belloni <alexandre.belloni@...> --- schedulers.py | 6 +++++- 1 file changed, 5 insertions(+), 1

Hmm, I'm not sure why I missed this. However, why is the MinGW build producing the .a files and not all the builds? It seems like this could go in the oe-core version of the recipe (w/o the

Thud has not been supported for a very long time actually. To really find out what is happening, it would help if you make an archive of tmp/work/../gdb/ and put it somewhere for inspection. Alex

Hi Alexander and KhemRaj, I am using the Yocto "thud" version which has long term support. The architecture used is aarch64-oe-linux The gdb directory or executables were not created in