* Messages for package www-client/chromium-64.0.3282.24: * Log file: /var/log/portage/www-client:chromium-64.0.3282.24:20171218-133744.log * There is NOT at least 12 GiB RAM * * Space constraints set in the ebuild were not met! * The build will most probably fail, you should enhance the space * as per failed tests. * * ERROR: www-client/chromium-64.0.3282.24::gentoo failed (pretend phase): * Build requirements not met! I'm pretty sure I've been able to build it with little to no problem with 4G of RAM and a little swap. The mistake seems to be assuming that number of jobs maps proportionally to memory usage which is far from true when using distcc. Furthermore, we aren't really adding memory constraints to every memory-intensive C++ build out there and it makes little to no sense to make chromium special here. People learn to deal with issues like this and throttle down makejobs if they need to.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9cba356dba5a20160911328339ba312ab8aa1158 commit 9cba356dba5a20160911328339ba312ab8aa1158 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2017-12-18 17:02:33 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2017-12-18 17:02:33 +0000 Revert "www-client/chromium: add memory check based on MAKEOPTS" This reverts commit 7efa454f0f38f0ec0cc36404faf7a16600e8a0f4. The job count may not have a direct relationship with memory usage in certain circumstances. Users are expected to manage their MAKEOPTS with respect to both CPU cores and available memory and other factors like use for ccache and distcc. Closes: https://bugs.gentoo.org/641564 www-client/chromium/chromium-63.0.3239.108.ebuild | 14 +++----------- www-client/chromium/chromium-64.0.3282.24.ebuild | 14 +++----------- www-client/chromium/chromium-65.0.3294.5.ebuild | 14 +++----------- 3 files changed, 9 insertions(+), 33 deletions(-)
