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

Add a dynamic BBFILES pattern so that patches for openembedded-layer are conditionally applied only if meta-oe is present. Signed-off-by: Sinan Kaya <okaya@...> --- conf/layer.conf | 9

Signed-off-by: Sinan Kaya <okaya@...> --- recipes-devtools/abseil-cpp/abseil-cpp_%.bbappend | 1 + 1 file changed, 1 insertion(+) create mode 100644

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK

Dynamically linked protoc.exe is failing as follows: [libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf

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 static linkage for the target build that we

I wasn't aware of this functionality. Will post v3.

Current Dev Position: YP 3.4 M3 Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze) Next Team Meetings: Bug Triage meeting Thursday Aug. 19th at 7:30am PDT

These 3 recipes are in meta-oe, not OE-core which means that the bbappends are going to cause a dangling appends error/warning. Please add a dynamic BBFILES pattern[1] so that these are conditionally

Apologies, this should use the :mingw32 override, since it's not *specific* to the SDK, but MinGW in general. Anyway, I fixed this up for you since I wasn't clear; this is in master-next and I'll get

Signed-off-by: Sinan Kaya <okaya@...> --- recipes-devtools/abseil-cpp/abseil-cpp_%.bbappend | 1 + 1 file changed, 1 insertion(+) create mode 100644

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK

Dynamically linked protoc.exe is failing as follows: [libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: google/protobuf/descriptor.proto [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK

All of the bbappends in meta-mingw should be using the :mingw32 override (or sdkmingw32 if it specific to just the SDK). If you found an example in the current code where that is not the case, it

Up till now ptest-runner2 returns number of failed tests with its exit status code. Such use case is not recommended [1] and may cause issues when there are more than 256 tests to be executed. To

From: Adrian Freihofer <adrian.freihofer@...> Try to make memory management more robust by assigning always NULL to struct ptest_list pointers. It's a refactoring which probably improves the

Change is targeting meta-mingw repository. I looked at other files in the repo to see what the pattern is.