Hi guys, we are currenlty working on adding automatically checking the binaries we put into an image for the presence of certain recommended compiler features. To achieve this, we created a bbclass

Add class to analyze binaries with checksec.py. checksec.py is a tool that checks if security features of a compiler have been used. To do so, it analyses the resulting binaries: * NX Proctection is

Add selftest that executes binary analysis on small rootfs Signed-off-by: Maximilian Blenk <Maximilian.Blenk@...> --- .../cases/hardened_binaries_checker.py | 42 +++++++++++++++++++ 1

Hi, I share an sstate-cache with my fellow developers and I was assessing why sometimes things got rebuild even though I did not expect this. One of the things I discovered was that we had two

Hello, I am trying to create tarballs to store yocto downloads. This is primarily to avoid old commits breaking when some random git repository changes their master branch name or something like

Hi, Any help on this topic would be much appreciated. Thanks, Nir. From: yocto@... <yocto@...>On Behalf Of Geller, Nir Sent: Wednesday, August 11, 2021 6:40 PM To: yocto@... Subject:

This should be reflected somewhere in YOCTO documentation. Especially for chromium. In the section: Host HW Requirements (with some explanation why). Zee _______

I'm guessing that ZFS is not really popular on embedded systems ;) -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

keep in mind that based upon how many vcores you allocate to VM will determine memory pressure as well. So if you have 2 cores perhaps 4GB is ok or maybe even 4 cores might workout ok but some bigger

ah, mine is both arm and arm64. No need to touch the recipe then.

RIght, the "mingw32" override shouldn't affect what you do with the *target* unless your target is MinGW; I'm not sure if anyone is actually doing that, most SDKs target Linux for ARM, Linux for

I see two classes of problems based on my engagement with the mingw32. Some recipes just don't build without using the static method for the SDK and the target both. (abseil-cpp is one of them) The

Are you building with "mingw32" as the target (not as the SDK), and it works there? I wonder why it only fails for the SDK build and not the target build? If that is truly the case, then yes I suppose

Previously SDRAM was 3 GB allocated. After changing SDRAM to 4 GB. then trying to build/make/bitbake.. getting new error i.e. Unable to connect to bitbake server

how much DRAM is allocated.

> /home/vrana/Desktop/yocto_Practice/build/tmp/ \ > work/core2-64-poky-linux/gcc/9.3.0-r0/recipe-sysroot-native/ \ > usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/ \ >

Sounds good. What do you think about this? My reading of the problem says that the problem only happens on win32 platforms due to how DLLs initialize the heap. We have use cases of both dynamic and

I had to clean these up a little bit and pushed them to master-next. Please verify that they still work for you and if not used them as a starting point and send a V4 patchset.

Hello all, I would like to know if anyone has experiences with equipping Yocto created images with ZFS support. If I'm not mistaken, the main problems of using ZFS in linux are of legal nature. ZFS

Hi, I am using ubuntu 16.04 (host) in VirtualBox. Memory allocated to VM machine is 100+ GB. Poky dunfell. While trying to build the project for x86_64. Steps followed as per yocto quick guide