Hi All, I have a macchina.io recipe that fetches the source from Github and compiles it correctly. In the WORKDIR , there is a samples directory with many examples, and each example has a Makefile,

Over in the OpenBMC project, we rebased on yocto master (https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/37488). After this we started seeing intermittent issues with our os-release.bb recipe.

Hi, Thanks for the reply. Setting LD to $CC didn't work as well.

Thanks, no problem :)

Hi, In my project, I ended up by overlaying not the entire /etc but only subparts I needed to modify. (/etc/machine-id is maybe already a bind mount from /run/machine-id) Hope it helps, Best

I see that your linker is not using proper sysroot perhaps using LD=${CC} might help.

maybe pregeenerate machine ID sometimes you can seed it from CPU Id or soc ID from eeprom.

Current Dev Position: YP 3.2 Final Build Next Deadline: YP 3.2 Final Release Next Team Meetings: Bug Triage meeting Thursday Oct. 29th at 7:30am PDT

[Re: [yocto] [meta-selinux][PATCH] layer.conf: add gatesgarth compatibility] On 20.10.27 (Tue 16:00) nefethael wrote: Yeah, I've had that older patch in my work-tree for a while now and haven't

Hi Jon, There is already a pending patch submitted some time ago by Aníbal Limó here https://patchwork.openembedded.org/patch/177350/ Best regards, Vincent

Running into this also. Here's another report of the same issue: https://lists.yoctoproject.org/g/yocto/message/50856 Regards //Ernst

Hi All, I have an SDK populated from an image. After sourcing the SDK env file, I try to run make on a project with this command : I specified the CFLAGS and CXXFLAGS as mentionned in Yocto document

Hi, In our current Yocto project we are using an overlayfs on top of /etc This seems to trigger the systemd-machine-id-setup service which fails with the error below: systemd-machine-id-setup[204]:

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.rc2 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

A build flagged for QA (yocto-3.2.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc2 Build hash information: bitbake:

Thanks for this Sangeeta and team! Since this is final 3.2 we're keen to ensure we sort out the issues we can. There was a buildhistory issue that became apparent in the last few days. Adding in the

All, YP M+ or high bugs which moved to a new milestone in WW43 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11449 Allow overriding classes to

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 50 bug owners as of the end of WW43 of who have open medium or higher bugs and enhancements against YP 3.3. There are 126 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on