Looks good to me. Lucky you :) -Mikko

Hi, openssl is tricky to update and requires backporting fixes for many, many recipes to get builds passing etc. Depending on project size, it may be possible to update only those components which

Do you perhaps want gdb-cross-mipsel ? cross-canadian is designed to be run as part of the SDK. Cheers, Richard

Hi, Good pointers in this thread already. Here are mine: * Share sstate mirror and download cache from release builds to developer topic builds. NFS, web server or rsync before calling bitbake

its perhaps due to the fact that host where this will run is sdkhost and not your normal buildhost, so perhaps you can use uninative tarball provided glibc to run it if your sdkhost is similar to

how big is the image its creating, might affect the time. Secondly use some system perf monitor to see which tool is taking so long.

Hi, (lets keep this on the list too) You can add _class-[target|native|nativesdk] to all variables to override defaults. Verify with "bitbake -e". Hope this helps, -Mikko

I'm trying to add support for ostree to out boot2qt yocto warrior build for raspberry pi4. I've added meta-updater & meta-updater-raspberrypi to the build and when I start bitbake I get the following

> DEPENDS_class-target += "systemd" You surely meant DEPENDS_append_class-target = " systemd" here

Hi, Make the systemd dependency for target only, e.g. DEPENDS_class-target += "systemd" etc. There may be relevant use cases to build some of systemd components or tools to native or nativesdk

https://layers.openembedded.org/layerindex/branch/master/recipes/?q=opentk says that there are not any known recipes, so you'll have to write one yourself. Ross

Hi JH, None. Or all of them, depends on how one sees it. You just create a directory in do_install of a recipe. You then make sure this directory is part of a package by checking it's in one of the

Hi, My build connman on Thud works on WiFi, but Zeus does not work, the connman could not get WiFi DHCP response, it puts a local IP address 169.254.24.188 to my WiFi interface. Has anyone found that

Well I have zeus and am using read-only rootfs with volatile binds and I did not need anything extra. I would dig into this /var/log thing and patch it away. I use systemd journal so no need for

LGTM, merged! -- Cheers, Alejandro

It also seems mwifiex_sdio tried to write to RO rootfs and failed and triggled RF Killm, does mwifiex_sdio needs some system directories for RW? [ 26.636845] mwifiex_sdio mmc0:0001:1:

Hi, Can you pls provide output of systemctl status systemd-rfkill There should be some more info what issue is. Pls this one also: systemctl status run-postinsts BR, marek

Hi Belisko, Thanks for your resonse. Failed at step STATE_DIRECTORY spawning /lib/systemd/systemd-rfkill: Read-only file system, did it try to write something in /lib/systemd? How should I fix

(trimming lists to yocto only) Hi, I think you may be missing volatile-binds package and service from your image. See poky/meta/recipes-core/volatile-binds/volatile-binds.bb It may be missing

Does anybody have any tips or tricks for how I might debug the (cross-canadian) gdb built by Yocto's SDK? I need to add some printf's to the gdb code to help track down why something isn't working,