On Tuesday, 4 December 2018 08:06:22 GMT Alexander Kapshuk wrote: > On Tue, Dec 4, 2018 at 9:35 AM Mick <[email protected]> wrote: > > Two Intel systems with 4G RAM failed to build chromium, even after setting > > > > MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM: > > >>> Running pre-merge checks for www-client/chromium-70.0.3538.110 > > > > * Checking for at least 3 GiB RAM ... [ ok > > ] > > * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/ > > > > chromium-70.0.3538.110/temp" ... [ ok > > ] > > > > Given I've spent more than two days compiling to get nowhere with this, > > I'm > > thinking: > > > > a) Chromium probably needs more than 3G now. > > b) Either the ebuild, or portage, ought to check available RAM and > > dynamically adjust the number of jobs accordingly - or have I watched too > > many AI movies? > > > > -- > > Regards, > > Mick > > You're right. Chromium does require more than 3G of RAM to build. > Here are the current system requirements for building Chromium on Linux: > > System requirements > A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is > highly recommended.
OK it figures, an AMD system with 16G RAM and /var/portage/ on a tmpfs had no problem. > At least 100GB of free disk space. O_O What the ... ? > You must have Git and Python v2 installed already. > > See the link below for details. > https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instr > uctions.md#system-requirements Thanks for this. It may be I'll need to build chromium as a binary on the faster PC from now on and copy it over to the older clients, but I can't recall what command spews out the detailed CFLAGS for the client which I will need to run on the faster host's CLI to emerge the binary. Grateful for any hints. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
