Date: Thu, 31 Jan 2013 23:33:52 +0400 From: Peter Vereshagin <peter@vereshagin.org> To: freebsd-questions@freebsd.org Subject: Re: binary updates for firefox and chromium? Message-ID: <20130131193153.GB55160@external.screwed.box> In-Reply-To: <keee2e$r38$1@ger.gmane.org> References: <20130131163225.GJ5719@external.screwed.box> <keee2e$r38$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. 2013/01/31 18:44:30 +0000 Walter Hurry <walterhurry@gmail.com> => To freebsd-questions@freebsd.org : WH> What, for example, is the problem with compiling Firefox 18 from the port? WH> WH> It takes about an hour to compile on my main box (9.1 Release on- WH> x86_64), which has nothing special at all by way of hardware. It use to take me a day (~20h) to rebuild each of: www/firefox, www.seamonkey, mail/thunderbird. In general I'm satisfied with speed of their work though. Starting from v17 upgrades I experience the problem I can't see the solution so I even don't ask about it. The details is that for all the 3 ports almost everything builds and then while linking the main (or almost the main) binary the compiler gets to lose the 'JSAutoCompartment.o'. I know I can buy some cloud to rebuild but is it of any rational if every hardware-like-mine owner shall follow this way when we can have it centralized? Thank you. -- Peter Vereshagin <peter@vereshagin.org> (http://vereshagin.org) pgp: 1754B9C1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130131193153.GB55160>