On Sunday, 14 January 2018 05:51:57 GMT tu...@posteo.de wrote: > On 01/13 11:39, Dale wrote: > > tu...@posteo.de wrote: > > > Hi Dale, > > > > > > one problem here is, that I am using firefox-bin, because compiling > > > firefox gave me compile errors in the past. > > > > > > One dependency of firefox-bin is....pulseaudio. > > > > > > Currently I am trying to compile firefox and will see how far it > > > goes... > > > > > > Short question: What timezone you are? > > > > > > Cheers > > > Meino > > > > I'm on CST here in the USA. May be around a little longer. Before you > > compile Firefox, make sure of your USE flags. No point compiling that > > monster and then realizing a USE flag is wrong. > > > > I suspect you can make this work with a compiled version. Just a > > feeling. > > > > Dale > > > > :-) :-) > > Hi Dale, > > I am on UTC+1 here... > > Thanks for the USEful :) hint! > Will see how far it goes. Currently rust is compiling and is > periodically > eating all my memory and my box starts swapping... > > This will take a while. > As soon I have further results, I will be back! > > Cheers! > Meino
With each job taking up to 1.2G of RAM you can quickly exhaust available memory on older PCs and swapping can start grinding the box to a halt. Since the move to profile 17.0 I found my old laptop comes to its knees on compiling larger packages like Chromium. If you also find swapping starts thrashing your drive and emerge moves nowhere fast as it becomes I/O bound, you should consider reducing the number of jobs with MAKEOPTS="-jX" where X is a lesser number than previously used and also reducing the --load-average to a low(er) number. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
