On 18/12/2014 03:33, Alec Ten Harmsel wrote:
>
> On 12/17/2014 04:59 PM, Alan McKinnon wrote:
>> On 18/12/2014 04:45, Harry Putnam wrote:
>>> Is there any advantage one way or the other emerging firefox.bin vs firefox?
>> Depends on your needs:
>>
>> firefox:
>> - pro: you get all the USE flags
>> - pro: you don't get bundled libs from Mozilla, the ebuild can use
>> system libs
>> - pro: the compiled binaries are integrated into gentoo like other ebuilds
>> - con: slow compiles. I have 8 i7 cores and 16G. the merge takes 20-35
>> minutes...
>
> Really? 20-35 minutes? I have 6 cores and 32G, and firefox only takes 10
> minutes. Do you have PORTAGE_TMPDIR mounted on tmpfs?
Yes, it is a tmpfs. I notice firefox compile times have been steadily
increasing over time, and also vary a lot. But, with 16G ram, I've
stopped worrying about what else the machine is doing when emerging.
I'll easily do an mp4 encode with handbrake while building firefox and
not worry about load :-)
Sat Aug 2 14:08:00 2014 >>> www-client/firefox-31.0
merge time: 18 minutes and 37 seconds.
Mon Sep 1 00:08:02 2014 >>> www-client/firefox-31.0
merge time: 13 hours, 54 minutes and 44 seconds.
Thu Sep 4 23:53:39 2014 >>> www-client/firefox-32.0
merge time: 19 minutes and 50 seconds.
Sun Sep 14 10:43:15 2014 >>> www-client/firefox-32.0
merge time: 41 minutes and 59 seconds.
Thu Oct 16 19:50:24 2014 >>> www-client/firefox-33.0
merge time: 34 minutes and 56 seconds.
Fri Nov 7 20:34:48 2014 >>> www-client/firefox-33.0-r1
merge time: 21 minutes and 13 seconds.
Sun Dec 7 14:01:03 2014 >>> www-client/firefox-34.0.5-r1
merge time: 37 minutes and 31 seconds.
--
Alan McKinnon
alan.mckin...@gmail.com
