Hi Op 13-06-2021 om 02:38 schreef Randy MacLeod: I watched running processes from KDE ksysguard and I believe the number of compilers was actually restricted with the patch. On the other hand the

Hi Ferry, Thanks for the update. Trevor and I saw similar (lack of ) results. Trevor even trying getting kea, which uses 'make' to be done the 'configure' stage, for two builds in differect dirs.

Hi Op 10-06-2021 om 22:35 schreef Ferry Toth: It works fine. To measure time I first built https://github.com/htot/meta-intel-edison (gatesgarth), so everything needed is downloaded and cached. Then

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

Hi, Not a fix, but a workaround, if you are willing to use containers is to create a build container and a similar sdk container. I added more information to the bug above. Regards, Robert

I think it may be this bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14428 We don't have a fix as yet, it looks difficult to solve :( Cheers, Richard

I was able to reproduce the error even with plain poky (without kas): ```bash git clone -b dunfell https://git.yoctoproject.org/git/poky cd poky source oe-init-build-env bitbake -c populate_sdk_ext

I have reconfigured our build system to use an internal server via bbappend: ICEDTEA_HG_URL = "https://internal.artifact.server/icedtea/" placed all the tarballs there according to expected locations,

Are you installing qemu into your image though? Qemu did get larger as it is built with more architectures enabled, but unless you're installing it in your image it won't make a difference. Ross

I have also the tarball but the build will fail later in the configure phase stating: icedtea7 "Invalid OpenJDK source zip specified". Is there something more I can try ?

Hi Experts, I am upgrading my Linux from Yocto Thud to Zeus (5.4 Kernel) . After building I could see a significant increase in the size of the image. On checking with buildhistory enabled, I could

From: Nagesh Shamnur <nagesh.shamnur@...> Currently only dfu and pyocd flashing are supported. Some boards such as Arduino Nano 33 BLE can be flashed via bossac which is released by Arduino

From: Nagesh Shamnur <nagesh.shamnur@...> Signed-off-by: Nagesh Shamnur <nagesh.shamnur@...> --- conf/machine/arduino-nano-33-ble.conf | 8 ++++++++ 1 file changed, 8 insertions(+)

From: Nagesh Shamnur <nagesh.shamnur@...> Some boards (e.g. Arduino Nano 33 BLE) require image in bin format for flashing with `-c flash_usb`. Provide that image along with ELF image on

From: Wojciech Zmuda <wojciech.zmuda@...> This patch set adds support for nRF52-based Arduino boards - Nano 33 BLE and BLE Sense - to both build and flash Zephyr applications. The board

From: Nagesh shamnur <nagesh.shamnur@...> Edit the test recipe removing obj_tracing tests that have been removed from Zephyr 2.6.0 release. Signed-off-by: Nagesh Shamnur

From: Wojciech Zmuda <wojciech.zmuda@...> Transition to Zephyr 2.6.0 broke meta-zephyr test suite. This patch fixes QEMU Cortex-M3 test suite (MACHINE=qemu-cortex-m3 bitbake

From: Davide Ricci <davide.ricci@...> Blinky is the most referenced sample in Zephyr's documentation and recall Arduino's first sketch example. This .bb file allows to build such

Lots of people use 20.04 so it seems odd that you'd have a problem specific to that host. Okay, please encourage them to reply on this thread. We may not always respond