From: Jeremy Puhlman <jpuhlman@...> * Fix various mutlilib issues. * Update python3 issues * License updates were change of address for FSF Signed-off-by: Jeremy A. Puhlman

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.21.bb | 4 ++-- 1 file changed, 2

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.21.bb | 2 +- 1 file changed, 1

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/recipes-cgl/crmsh/crmsh_3.0.3.bb | 2 +- 1 file changed, 1 insertion(+), 1

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb | 4 ++-- 1 file changed, 2

From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> Signed-off-by: Adrian Dudau <adrian.dudau@...> ---

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

My build machine has lots of RAM and I do builds in a 32GB tmpfs with rm_work (and no, I don't build webkit, which would make this impractical). As you say, with sufficient RAM the build speed is

Hi Laurent and Quentin - Thank you both so much for your help! I did just end up patching the source code for my recipe - I had to both add the 3 and remove the -mt, and the OS does build now! If

Some of these started 2 years ago. Probably Krogoth timeframe thru rocko. (Did I get the names right!) Not downloading from the net. But we had an inhouse git mirror of yocto. We tried being a

anyway this sounds like a complete rebuild not taking advantage of shard-state cache -- Yann Dirson <yann@...> Blade / Shadow -- http://shadow.tech

4 hours seems extremely long to me for a 8 core system, but I have not tried this in a while. Were you removing all the sources and re-downloading them for every build? From: <yocto@...> on behalf

My own experience (pardon me if already discussed) Fought the build times for several months - ending up eventually at 8 cores (but specifying 16 threads in poky builds). Best times for my build about

Well, I can't build with under 2 gigs per core or I run out of physical memory and kernel oom-killer kicks in to kill the build. Also can't run with yocto default parallel settings which only take

Other replies look good to me, here are few additions: If you want to compare how terrible your current VM compares with some other builders, you can

Hi Emily, You can create a patch for it. You can use devtool modify <your-recipe> and create the patch from there, you have access to the sources with that. devtool build <your-recipe> to check it

Hi Laurent - Unfortunately I don't have full control over the repo that's using boost_python-mt so I'm not sure I can switch it right now. I realize this is not a long-term solution, as I'll need to

Seems a bit excessive to buy hardware just to handle a particular corner case. Most of OE/Yocto code is plain C, not even C++. My rig only has 8GB but doesn't run into memory issues during big GUI

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

Sorry - wrong number. My rig does not have a 1900, but an "AMD Ryzen 7 1700".