| 1 |
> Thanks for this. It may be I'll need to build chromium as a binary on the |
| 2 |
> faster PC from now on and copy it over to the older clients, but I can't |
| 3 |
> recall what command spews out the detailed CFLAGS for the client which I will |
| 4 |
> need to run on the faster host's CLI to emerge the binary. Grateful for any |
| 5 |
> hints. |
| 6 |
|
| 7 |
app-portage/cpuid2cpuflags |
| 8 |
|
| 9 |
Mick wrote: |
| 10 |
> On Tuesday, 4 December 2018 08:06:22 GMT Alexander Kapshuk wrote: |
| 11 |
>> On Tue, Dec 4, 2018 at 9:35 AM Mick <michaelkintzios@×××××.com> wrote: |
| 12 |
>>> Two Intel systems with 4G RAM failed to build chromium, even after setting |
| 13 |
>>> |
| 14 |
>>> MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM: |
| 15 |
>>>>>> Running pre-merge checks for www-client/chromium-70.0.3538.110 |
| 16 |
>>> |
| 17 |
>>> * Checking for at least 3 GiB RAM ... [ ok |
| 18 |
>>> ] |
| 19 |
>>> * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/ |
| 20 |
>>> |
| 21 |
>>> chromium-70.0.3538.110/temp" ... [ ok |
| 22 |
>>> ] |
| 23 |
>>> |
| 24 |
>>> Given I've spent more than two days compiling to get nowhere with this, |
| 25 |
>>> I'm |
| 26 |
>>> thinking: |
| 27 |
>>> |
| 28 |
>>> a) Chromium probably needs more than 3G now. |
| 29 |
>>> b) Either the ebuild, or portage, ought to check available RAM and |
| 30 |
>>> dynamically adjust the number of jobs accordingly - or have I watched too |
| 31 |
>>> many AI movies? |
| 32 |
>>> |
| 33 |
>>> -- |
| 34 |
>>> Regards, |
| 35 |
>>> Mick |
| 36 |
>> |
| 37 |
>> You're right. Chromium does require more than 3G of RAM to build. |
| 38 |
>> Here are the current system requirements for building Chromium on Linux: |
| 39 |
>> |
| 40 |
>> System requirements |
| 41 |
>> A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is |
| 42 |
>> highly recommended. |
| 43 |
> |
| 44 |
> OK it figures, an AMD system with 16G RAM and /var/portage/ on a tmpfs had no |
| 45 |
> problem. |
| 46 |
> |
| 47 |
> |
| 48 |
>> At least 100GB of free disk space. |
| 49 |
> |
| 50 |
> O_O What the ... ? |
| 51 |
> |
| 52 |
> |
| 53 |
>> You must have Git and Python v2 installed already. |
| 54 |
>> |
| 55 |
>> See the link below for details. |
| 56 |
>> https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instr |
| 57 |
>> uctions.md#system-requirements |
| 58 |
> |
| 59 |
> Thanks for this. It may be I'll need to build chromium as a binary on the |
| 60 |
> faster PC from now on and copy it over to the older clients, but I can't |
| 61 |
> recall what command spews out the detailed CFLAGS for the client which I will |
| 62 |
> need to run on the faster host's CLI to emerge the binary. Grateful for any |
| 63 |
> hints. |
| 64 |
> |
Archives