On 5/20/22 14:30, Thomas Perrot wrote:
Hello Jacob,
On Fri, 2022-05-20 at 14:19 +0200, Jacob Kroon wrote:
On 5/20/22 14:16, Thomas Perrot via lists.openembedded.org wrote:
Otherwise the compilation may lead to out-of-memories.
Signed-off-by: Thomas Perrot <thomas.per...@bootlin.com>
---
meta/recipes-sato/webkit/webkitgtk_2.36.1.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-sato/webkit/webkitgtk_2.36.1.bb
b/meta/recipes-sato/webkit/webkitgtk_2.36.1.bb
index 65757c36a733..e7cfe49e2b87 100644
--- a/meta/recipes-sato/webkit/webkitgtk_2.36.1.bb
+++ b/meta/recipes-sato/webkit/webkitgtk_2.36.1.bb
@@ -80,6 +80,8 @@ setup_python_link() {
fi
}
+PARALLEL_MAKE = ""
+
EXTRA_OECMAKE = " \
-DPORT=GTK \
${@bb.utils.contains('GI_DATA_ENABLED', 'True', '-
DENABLE_INTROSPECTION=ON', '-DENABLE_INTROSPECTION=OFF', d)} \
@@ -164,4 +166,3 @@ src_package_preprocess () {
${B}/WebKit2Gtk/DerivedSources/webkit2/*.h
}
-
Why punish build machines with lots of RAM ? Maybe it could be set
depending on available RAM/number of cores ?
Why not.
Because it slows down the build for them, which is not good.
I tested on a build server with more than ~12GB ram available and 16
cores, then I tried to reduce the number of threads and when the value
is greater than 1 the build fails.
12GB RAM does not sound like much for a 16 core system.
Jacob
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#165931):
https://lists.openembedded.org/g/openembedded-core/message/165931
Mute This Topic: https://lists.openembedded.org/mt/91229473/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
