| 1 |
Two Intel systems with 4G RAM failed to build chromium, even after setting |
| 2 |
MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM: |
| 3 |
|
| 4 |
>>> Running pre-merge checks for www-client/chromium-70.0.3538.110 |
| 5 |
* Checking for at least 3 GiB RAM ... [ ok ] |
| 6 |
* Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/ |
| 7 |
chromium-70.0.3538.110/temp" ... [ ok ] |
| 8 |
|
| 9 |
Given I've spent more than two days compiling to get nowhere with this, I'm |
| 10 |
thinking: |
| 11 |
|
| 12 |
a) Chromium probably needs more than 3G now. |
| 13 |
b) Either the ebuild, or portage, ought to check available RAM and dynamically |
| 14 |
adjust the number of jobs accordingly - or have I watched too many AI movies? |
| 15 |
|
| 16 |
-- |
| 17 |
Regards, |
| 18 |
Mick |
Archives