| 1 |
On 13/10/20 07:48, J. Roeleveld wrote: |
| 2 |
> On Tuesday, October 13, 2020 8:28:01 AM CEST Andreas Fink wrote: |
| 3 |
>> On Tue, 13 Oct 2020 02:10:04 -0400 |
| 4 |
>> |
| 5 |
>> Jude DaShiell <jdashiel@×××××.com> wrote: |
| 6 |
>>> x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated |
| 7 |
>>> program cc1plus compilation terminated. |
| 8 |
>> |
| 9 |
>> These two lines stongly suggest that you ran out of memory while |
| 10 |
>> compilation. You could try to build it with only one job (-j1), |
| 11 |
>> currently you are using -j2. |
| 12 |
>> Another option would be to buy more RAM ;) |
| 13 |
>> And last but not least, you could increase your swap memory, but be |
| 14 |
>> prepared that your system becomes unresponsive and compilation will |
| 15 |
>> probably take forever. |
| 16 |
> |
| 17 |
> One more suggestion, your PORTAGE_TMPDIR is set to "/var/tmp". |
| 18 |
> By default, this is a tmpfs, which means it's all kept in RAM. |
| 19 |
|
| 20 |
If that's true then somebody has ****ed up! |
| 21 |
|
| 22 |
/tmp is specified as "files may disappear at any time" |
| 23 |
|
| 24 |
/var/tmp is specified as "temporary storage that should survive a reboot" |
| 25 |
|
| 26 |
Okay, that's not the exact wording, but that is the effect. |
| 27 |
> |
| 28 |
> If your system is that low on RAM, you might want to change that to a |
| 29 |
> different location that is backed by a real disk. |
| 30 |
> |
| 31 |
The other thing about default tmpfs, is it defaults to half of ram. So |
| 32 |
it could actually be quite small. I explicitly set mine to be big, |
| 33 |
because I configure oodles of swap. |
| 34 |
|
| 35 |
Cheers, |
| 36 |
Wol |
Archives