starting to think about a new laptop that will, among other things, do lots of OE/YP builds, and i'll start with this as the basis for a few questions about hard

Does it mean that with the local.conf line: # enable,disable,depends,rdepends # PACKAGECONFIG[qemu] = "--with-qemu,--without-qemu,qemu," The QEMU is completely removed (this is all that needs to be

Yes, look at the PACKAGECONFIGs and setting QEMU_TARGETS. Ross

Hello, you can use wildebeest's mirror: ICEDTEA_HG_URL = "http://icedtea.wildebeest.org/hg/release/${ICEDTEA_PREFIX}" Marvin

Hello. Fixed. Indeed, I did not test with 2.5. Thanks for spotting. Fixed. I send a v3 now. regards Stefan Schmidt

From: Stefan Schmidt <stefan.schmidt@...> Similar to the normal echo-client example it demonstrates socket usage, but in this variant we enable the OpenThread config overlay and add the needed

From: Stefan Schmidt <stefan.schmidt@...> OpenThread support in Zephyr is realised as an external module. Make sure we pull it in and have it available for applications to use

Thanks for the clarification, yes I am installing QEMU in my image. Is there some way that we can disable the additional architectures and streamline the size ? Thanks

(Buried on my desktop, better late than never) Attendees: Alex, Richard, Saul, Randy, Tony, Trevor 1. valgrind: - taskset work-around really helps. - working on stack_changes bug for qemuarm43

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