Hi, This[1] is what I usually add as well to the security flags. With respect to the "default" flags I had some fun with the SDK and -D_FORTIFY_SOURCE=2 and -fstack-protector-strong. I guess they do

These seem like reasonable things to do, are there any downsides to them? I'd be happy to test some patches, see if they do cause issues... Cheers, Richard

All, YP M+ or high bugs which moved to a new milestone in WW05 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12368 persistent bitbake server does not

All, The below were the owners of enhancements or bugs closed during the last week! Who Count mhalstead@... 1 trevor.gamblin@... 1 randy.macleod@... 1 richard.purdie@... 1 Grand

All, Below is the list as of top 44 bug owners as of the end of WW05 of who have open medium or higher bugs and enhancements against YP 3.5. There are 62 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

Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build Next Team Meetings: Bug Triage meeting Thursday Feb. 3rd 7:30 am PDT

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (2/1) Yocto Project Technical Team Meeting: We encourage people attending the meeting to

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

Thanks, Alex! That was it. The script that started the matchbox-terminal is /usr/bin/mini-x-session. I just edited this file and commented out the terminal line and another line that was setting my

Hi all. The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can change it in a recipe? I try to understand why my file defconfig is not used my kernel configurator MZ

In Zeus I have a recipe that installs the file (a u-boot boot.scr for me): install -m 0644 boot.scr ${DEPLOYDIR} Make sure the recipe is included in your image. Then in my machine

Hello @Nicolas @Erik @Khem, Update from my side: After following some discussion from other posts, I added "config" file. ~/.ssh/config: Host git.example.com HostName git.example.com User

The logs reveal that 'packagegroup-core-x11 packagegroup-core-x11-base packagegroup-core-x11-xserver' are all installed. x11-base pulls in recipes-graphics/mini-x-session/mini-x-session_0.1.bb which

Hi all, This is the full report for yocto-3.5_M2.rc6: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Thanks, Alex. The log file is attached. By the way, I'd be happy with a solution that involves changing a file on the target system after the Yocto build is complete. The fix doesn't need to be in

Please share the log.do_rootfs for your image, otherwise it's difficult to say why the terminal ends up being there and gets autostarted. Alex

Hello Yocto Community - I am using Yocto to build a core-image-minimal image for Intel hardware. When the system boots, it automatically starts a matchbox-terminal as root. This is a huge security

see https://github.com/lkrg-org/lkrg Support new stable and mainline kernels 5.14 to at least 5.16-rc* Support new longterm kernels 5.4.118+, 4.19.191+, 4.14.233+ update SRC_URI as location

Hello everyone, I need to put the boot.sh file in the build/deploy/images/$IMAGE_NAME/ directory during the build, how can I do this using the yocto build system?