This is a verbatim copy of go 1.16 recipes from oe-core master just before they were updated to 1.17. Link:

Reviewed-by: Martin Kaistra <martin.kaistra@...> Signed-off-by: Alexander Kanavin <alex@...> --- COPYING.MIT | 17 +++++++++++++++++ README | 23

<bluelightning@...> wrote: That is good testimony, it will be good to know how this option impacts performance and does it work across architectures and libc's supported in OE.

I guess you can submit a patch, and it can be taken for a spin on the autobuilder? Alex

Another quirk of this - with dunfell, the buildepoxy SDK test fails on Ubuntu 18.04 with -fstack-clash-protection because the version of meson in dunfell uses the same LDFLAGS value for both host

Thanks, Khem. I sent a patch to OE. -- Rudolf J Streif CEO/CTO ibeeto +1.855.442.3386 x700

<rudolf.streif@...> wrote: seems an oversight.

It's been a while, but I was able to build yocto sumo (2.5) using https://github.com/crops/poky-container

Hi all I'd like to install my python3 application in a custom folder with all local packages and data. The source code folder has this

I got a question about the linux-firmware-bcm4373 package. The link /lib/firmware/brcm/brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob is packaged into linux-firmware and not into

I think the best way out for you is to set up a container with a supported older distribution. Usually you need an older gcc version from the host machine, so the container will have that. Alex

Hi, Has anyone tried to build yocto 2.6 on Ubuntu 20.04? I know it's not supported, but it's a major task for me to upgrade to yocto 3.x. I tried it myself and it fails on building qemu-native. I

Hello, so I'm a bit at a loss. I admit, I've not yet been using Yocto for a long time. I'm trying to use base-utils as provided by packagegroup-core-base-utils to have a more full featured set of base

Hi, Please don't include CVE twice in the variable name, that's was annoying and just got used to the CVE_CHECK_WHITELIST one. CVE_CHECK_IGNORE would do. Cheers, -Mikko

Hi Michael, One change at a time please ☺️ This should be done right after the git checkout. It's better to ensure what you build is clean that try to ensure the next oneto build has a clean

Hello All, Advice on working with Yocto and Raspberry Pi CM4 Lite would be helpful.I recently got my hands on with CM4 and now I want to build Yocto image with u-boot as bootloader. I have few

I am trying to fetch a private gitlab repo within Yocto image recipe using SSH protocol. In my image recipe I have passed SRC_URI as: SRC_URI = " \

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.5_M2.rc6. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

The layer index does already support this, it's just not exposed (at the time I introduced it - some time ago - I thought it might encourage people to deviate from the release branch names, but in

Hi folks I've been looking into a couple of compiler flags for hardening that I think we might want to consider enabling by default in security-flags.inc: 1) -fstack-clash-protection This option