I was trying to avoid this as only some parts of the build use large
amounts of memory and the build is so slow that it would really help to
have 2 build jobs, but it's causing the bulk build machines to swap too
much, which causes clocks to go out of sync (11 minutes in my current
build), which breaks all the KF5 things built on that machine afterwards
because cmake does stupid time checks on files installed in /usr/local
not just in the build directory.
GN_ARGS.
From 2013 until early 2021, Google permitted distribution builds of
Chromium to access Google APIs that added significant features to
Chromium including, but not limited to, Sync and geolocation.
As of March 15, 2021, any Chromium builds which pass client_id and/or
client_secret during build will prevent end-users from signing into their
Google account.
Hint:
If you wish to use sync, you have to build your own chromium package
and use the publicly available client_id and client_secret of the Chrome
browser.
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
cannot be loaded, they immediately exit:
: sthen@i386.p; chrome
/usr/local/bin/chrome[60]: /usr/local/chrome/chrome: Cannot allocate memory
: sthen@i386.p; size /usr/local/chrome/chrome
text data bss dec hex
180104608 3805736 1949616 185859960 b13ff78
exiting happens very early, before ld.so loads libraries:
: sthen@i386.p; LD_DEBUG=1 /usr/local/chrome/chrome
ksh: /usr/local/chrome/chrome: Cannot allocate memory
no point wasting 2x24h in build for these two.
