When using a laptop with only 16 GB RAM to build with 8 or 16 threads, on what drive will the heavily used large swap partition be? gcc loves to use > 2 GB RAM for non-trivial C++ code, with 16 thread

Hi Armin, yes. cu Adrian

I have an interest in keeping warrior branch alive in poky and meta-oe, and I'll take this responsibility since noone else seems to be interested. I have some ideas, but not yet a fixed plan how I wil

Hi Stefano, one major difference between Yocto and most Linux distributions is that most Linux distributions enable automatic security updates by default. A normal Ubuntu system gets security updates

This is not true, package manager like dpkg are trying very very hard to make things atomic where they have to be and allow recovery from any kind of interruption. I do not recall anyone ever describi

The recipe in meta-openembedded cross-compiles without problem. cu Adrian

This is a bug: http://bugzilla.yoctoproject.org/show_bug.cgi?id=13306 I sometimes wonder whether something basic like "no more than one compile task at a time" would be sufficient in practice to avoid

Depends on what you are building. Building non-trivial C++ code (e.g. webkitgtk) with 24 cores but only 32 GB RAM will not work, for such code you need more than 2 GB/core. I would buy 128 GB RAM to n

This platform has been removed from master, and is therefore not in M3. cu Adrian

Please send a complete build log, this looks like a parallel build failure where some .c is compiled before some header it uses is fully generated (or something similar). I assume PARALLEL_MAKE = "" w

I would consider this too risky for a last-minute addition since it is a non-urgent optimization and not a regression fix. cu Adrian

It would be easier to follow only development discussions if these would move to a dedicated list. cu Adrian

Would it be possible to also create a yocto-devel or yocto-core mailing list for discussing development of Yocto? Currently the yocto list is a mixture of core development list and forum for newbie us

13.x is a short-term stable that will become EOL this June. 12.x is LTS with 2 years of upstream security support left when Yocto 3.1 releases. From a security support point of view shipping Python 2

The jm_cv_func_working_malloc test is: main () { exit (malloc (0) ? 0 : 1); } The C standard says that this is implementation defined, both results are permitted. glibc has the same behaviour forever,

The fork can be a .bbappend with a patch adding the required definitions to linux-libc-headers. cu Adrian

/bin/awk is missing on your target image that will run on the T4240 RDB. The smallest implementation is to enable CONFIG_AWK in your busybox config. cu Adrian

DEPENDS, not DEPENDS_${PN} cu Adrian

Three comments from me: 1. Patch review Merge requests work well when there is one maintainer who reviews everything. For not regressing on the current level of review before something hits master, me

The errata switches are only valid for aarch64, not for armv7a. There is likely some kind of "invalid option" earlier in your build. cu Adrian