Re: [yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

> 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 packages like > chromium etc. need minimal 16GB RAM to build. This should be reflected

Re: [linux-yocto][linux-yocto v5.10/standard/base][PATCH] OF: DT-Overlay configfs interface (v7)

There were some conflicts with the rpi and xlnx-soc branches. i kept the DT-overlay versions that were already in those BSPs (git merge -X ours), and only merged the non conflicting delta. If there's an issue with the results, please send follow up patches. Bruce On Tue, Aug 17, 2021 at 3:02

Re: [linux-yocto] [yocto-kernel-cache yocto-5.10]: nxp-s32g2xx: change CAN LLCE config to y to fix build warning

In message: [linux-yocto] [yocto-kernel-cache yocto-5.10]: nxp-s32g2xx: change CAN LLCE config to y to fix build warning on 16/08/2021 Zhantao Tang wrote: > > Hi Bruce, > > There is an patch related with CAN LLCE feature to fix a kernel build warning > for nxp-s32g2xx bsp, > would you please

Re: [linux-yocto][yocto-kernel-cache][yocto-5.10 only][PATCH] bsp: axxia: add new kernel options for axm56xx

merged. Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-5.10 only][PATCH] bsp: axxia: add new kernel options for axm56xx on 16/08/2021 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > This patch includes modifications as below: > 1. add CONFIG_PROFILING and

Re: [linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 0/6]

In message: [linux-yocto][v5.10/standard/preempt-rt/sdkv5.10/axxia][PATCH 0/6] on 16/08/2021 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > Would you please help merge these patches to the 2 branches? > > v5.10/standard/preempt-rt/sdkv5.10/axxia >

Re: [linux-yocto][yocto-kernel-cache-5.10][PATCH] nxp-ls1028: disable imx drivers and the dependence of the drivers.

In message: [linux-yocto][yocto-kernel-cache-5.10][PATCH] nxp-ls1028: disable imx drivers and the dependence of the drivers. on 16/08/2021 Zhang, Siyu wrote: > On kernel 5.10.57, if enable ARCH_MXC, we will > find errors during starting the board. > > The error log: > AXI BUS ERROR > [drm]

Re: [linux-yocto] [linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx]: nxp-s32g2xx: update kernel with 42 new patches from NXP pre-released SDK bsp30 rc5

In message: [linux-yocto] [linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx]: nxp-s32g2xx: update kernel with 42 new patches from NXP pre-released SDK bsp30 rc5 on 16/08/2021 Zhantao Tang wrote: > > Hi Bruce, > > There are 42 new patches from NXP pre-released SDK bsp30 v5.10 rc5 kernel >

[linux-yocto][linux-yocto-dev v5.13] kernel code for marvell octeon(cn96xx & cn106xx)

Hi Bruce, Linux kernel for marvell octeon(cn96xx & cn106xx) base on v5.13.4 is ready in my private repo. Please help to create branch and merge code into our linux-yocto-dev repo. repo: linux-yocto-dev branch: v5.13/standard/cn-sdkv5.4/octeon Thanks,

Re: [yocto] ZFS/ZoL on Yocto

On 17/08/2021 17:52:17+0200, Manuel Wagesreither wrote: > 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 can not go into the linux

Re: [yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

On Tue, Aug 17, 2021 at 10:36 AM wrote: > > Previously SDRAM was 3 GB allocated. > > After changing SDRAM to 4 GB. > then trying to build/make/bitbake.. 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

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

On 8/17/2021 9:19 PM, Joshua Watt wrote: >> I still would like to be able to static/dynamic link grpc/protobuf for >> my target using the SDK. > > 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

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

On 8/17/21 1:15 PM, Sinan Kaya wrote: On 8/17/2021 9:10 PM, Joshua Watt wrote: We have use cases of both dynamic and static linkage for the target build that we have not seen any issues with. Are you building with "mingw32" as the target (not as the SDK), and it works there? I wonder why it

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

On 8/17/2021 9:10 PM, Joshua Watt wrote: >> We have use cases of both dynamic and static linkage for the >> target build that we have not seen any issues with. > > 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

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

On 8/17/21 11:29 AM, Sinan Kaya wrote: On 8/17/2021 7:01 PM, Joshua Watt wrote: 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. Sounds good. What do you think

Re: [yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

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 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54456):

Re: [yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

On 8/17/21 8:38 AM, vishal.rana...@gmail.com wrote: Hi, I am using*ubuntu 16.04* (host) in VirtualBox. Memory allocated to VM machine is 100+ GB. how much DRAM is allocated. Poky*dunfell*. While trying to build the project fo*r x86_64.* Steps followed as per yocto quick guide for

Re: [yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

> /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/ \ > gcc/x86_64-poky-linux/9.3.0/as: > *out of memory allocating 4064 bytes after a total of 452272128 bytes* Looks to me

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

On 8/17/2021 7:01 PM, Joshua Watt wrote: > 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. Sounds good. What do you think about this? My reading of the problem

Re: [yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

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. On 8/17/21 10:09 AM, Sinan Kaya wrote: Dynamically linked protoc.exe is failing as follows: [libprotobuf ERROR

[yocto] ZFS/ZoL on Yocto

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 can not go into the linux kernel source tree, as it conflicts with the GPL. Hence, the linux

[yocto] Getting bitbake error after 54% recipes are baked. #dunfell #yocto

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 fo *r x86_64.* Steps followed as per yocto quick guide for "dunfell" // //

[yocto] [meta-mingw] [PATCH v3 5/5] conf/layer.conf: use BBFILES_DYNAMIC for dynamic layers

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 --- conf/layer.conf | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index

[yocto] [meta-mingw] [PATCH v3 3/5] grpc: static link tools when generating SDK

[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 failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

[yocto] [meta-mingw] [PATCH v3 1/5] protobuf: static link tools when generating sdk

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 FATAL google/protobuf/descriptor.cc:1371] CHECK failed:

[yocto] [meta-mingw] [PATCH v3 2/5] protobuf-c: static link when generating sdk

[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 failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

Re: [yocto] [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk

On 8/17/2021 5:33 PM, Joshua Watt wrote: >> +EXTRA_OECONF:append:sdkmingw32 = " --disable-shared" > > 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

Re: [yocto] [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk

On 8/17/2021 5:44 PM, Joshua Watt wrote: > 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 applied > only if meta-oe is present, something

[yocto] Yocto Project Status WW33`21

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 (

Re: [yocto] [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk

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 applied only if meta-oe is present, something like:  BBFILES_DYNAMIC += "\

Re: [yocto] [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk

On 8/17/21 9:07 AM, Sinan Kaya wrote: 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 FATAL google/protobuf/descriptor.cc:1371] CHECK failed:

[yocto] [meta-mingw] [PATCH] abseil-cpp: disable shared build as it is broken

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

[yocto] [meta-mingw] [PATCH v2 2/3] protobuf-c: static link when generating sdk

[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 failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

[yocto] [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk

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 FATAL google/protobuf/descriptor.cc:1371] CHECK failed:

[yocto] [meta-mingw] [PATCH v2 3/3] grpc: static link tools when generating SDK

[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 failed: GeneratedDatabase()->Add(encoded_file_descriptor, size): Switch to static linkage per upstream

Re: [yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

On 8/17/21 6:03 AM, Sinan Kaya wrote: On 8/17/2021 6:26 AM, Khem Raj wrote: +EXTRA_OECONF:append:class-nativesdk = " --disable-shared" This is not an inert change can it use some mingw specific override as well Change is targeting meta-mingw repository. I looked at other files in the

[yocto] [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner

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 alleviate this issue the number of total tests with number of failed ones is printed before exit. To

[yocto] [PATCH v2 ptest-runner 1/2] mem: Refactor ptest_list cleanup

From: 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 code but does not fix a concrete bug. Signed-off-by: Adrian Freihofer --- Changes for v2 [lukma]: - Rebase from origin/dev to

Re: [yocto] [meta-mingw] [PATCH 1/3] protobuf: static link tools when generating sdk

On 8/17/2021 6:26 AM, Khem Raj wrote: > +EXTRA_OECONF:append:class-nativesdk = " --disable-shared" > > > This is not an inert change can it use some mingw specific override as well  Change is targeting meta-mingw repository. I looked at other files in the repo to see what the pattern is.

[yocto] How to disable installing python in Hardknott version?

Hello, I used dbus-send and installed the dbus package in Zeus, it did not install python, but in Hardknott, the python3 and dbus-python installed automatically, the python3 size is too large, how can I disable installing python3? Thank you. Kind regards, - jh -=-=-=-=-=-=-=-=-=-=-=- Links:

Re: [yocto] execute a python code in raspberrypi #python

On Fri, 2021-08-13 at 02:40 -0700, yasminebenghoz...@gmail.com wrote: > Hello beautiful people,  > > I successfully executed helloworld.py on the raspberrypi by making a > layer. BUt now i need to add a whole python code with classes etc, > which exists in different files like the picture, I

Re: [yocto] best way to get feature of systemd v248 in yocto-hardknott (systemd v247)?

On Fri, 2021-08-13 at 15:31 -0600, Bill Plunkett wrote: > I'd like to use a systemd DHCP client feature that became available > in v248 in my yocto-hardknott system.  Is there any hope of using the > complete v249.1 recipe from the oe master branch? > To backport a newer version, I usually just

[linux-yocto][linux-yocto v5.10/standard/base][PATCH] OF: DT-Overlay configfs interface (v7)

From: Pantelis Antoniou commit ba900332d141bf2d1d3b6aa7da8f01fe4b9fb256 from https://github.com/altera-opensource/linux-socfpga.git Add a runtime interface to using configfs for generic device tree overlay usage. With it its possible to use device tree overlays without having to use a