<alexandre.belloni@...> wrote: yeah my bad, too many context switches, the patch was applied before any other patches from meta-gpl2 to isolate the issue, but then I should have rebased it bef

Signed-off-by: Khem Raj <raj.khem@...> --- ...-includes-for-glibc-2.34-portability.patch | 35 +++++++++++++++++++ recipes-core/coreutils/coreutils_6.9.bb | 1 + 2 files changed, 36 insertions(+)

Signed-off-by: Khem Raj <raj.khem@...> --- ...-includes-for-glibc-2.34-portability.patch | 39 +++++++++++++++++++ recipes-core/coreutils/coreutils_6.9.bb | 1 + 2 files changed, 40 insertions(+)

this is fine, if you are interested submit it as a patch to include in metadata in meta-python

#sdk

This version looks good to me.

Can you file a ticket in bugzilla for this as well please.

#devtool #dunfell

while I appreciate this change, it does have an effect of removing the users away from BSP variables that core metadata layers have, e.g. SERIAL_CONSOLES is a well defined and documented variable and

I think the advantage is not on high end CPUs but more on less powerful ones, so perhaps trying it on something like rpi0 or lower would be good

This ensures that DISTRO_FEATURES can translates correctly for qtbate packageconfigs and we can get right platforms enabled Signed-off-by: Khem Raj <raj.khem@...> --- conf/layer.conf | 5 +++++ .

I think this will be hard to support unless your applications are self contained and will bring its own runtime as well in that case you can build a SDK from newer releases which matches compiler you

right and thats why I will be reluctant to go too far at distro level unless there is general interest in wider communities as it can make us an island. you could tool it as a packageconfig for system

Finding dlopen dependencies is a neat idea, but it has to be accepted cross distro, and also applications have to manually declare it in code if I understand systemd's patch correctly. This will be ha

Please find out which layer is adding this bbappend you could use bitbake-layers show-appends sysvinit It seems recipe version is newer perhaps and the bbappend is still made for older recipe, these t

#dunfell

it will depend on release, if you are on 3.0+ then yes single setting will work, older releases would mean above is needed. see https://docs.yoctoproject.org/ref-manual/migration-3.0.html?highlight=in

#dunfell

there is similar segv I see on master, Can you test this patch on master and see if that works? secondly, also try master branch of weston and see if it fixed it then we can narrow down needed backpor

see http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.3.bb?h=dunfell#n114 change that to -Dfdkaac=enabled if it works, then perhaps tu

#yocto

this is upto your component's build system, so perhaps you should look into that and ensure that its using right options. Second place to look is recipe for your package and ensure right vars and opti

<Jasper.Orschulko@...> wrote: I see, this is a workaround that will work in this case but may not work in case where the PN is not empty but static linking it happening. So I think in cas

<Jasper.Orschulko@...> wrote: I am not sure why you will include empty packages in your manifest

<nicolas.dechesne@...> wrote: perhaps good time to consider matrix