public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox and Thunderbird compile issue
Date: Sat, 24 Nov 2018 02:29:10 -0600	[thread overview]
Message-ID: <35804e36-7200-e68e-1314-a42957b788ac@gmail.com> (raw)
In-Reply-To: <pt1h6g$hqd$1@blaine.gmane.org>

(Nuno Silva) wrote:
> On 2018-11-18, Daniel Frey wrote:
> [...]
>> It's really unfortunate that on massive builds distcc is not an option.
>> Maybe I should consider -bin instead.
> If you do happen to have a more powerful machine running Gentoo on a
> compatible architecture[1], you could also try Gentoo binary packages
> (that is, not -bin, but binary packages made from www-client/firefox and
> mail-client/thunderbird on that machine, either automatically with
> FEATURES=buildpkg, or manually using quickpkg or emerge --buildpkg).
>
> [1] I guess it should also be possible to cross-compile, but that will
> require additional steps, with which I am not acquainted.
>
> Do you know Seamonkey? If you like it and it works for everything you
> use Firefox and Thunderbird with, another idea to consider would be
> replacing Firefox and Thunderbird with Seamonkey Navigator and Seamonkey
> Mail&News.  That way, it would be "just" one massive build instead of
> two.
>

I looked at the build times of both Firefox and Seamonkey, they both
average out to about the same.  For me here, about 1.5 hours.  Of
course, it varies a bit but that's a rough average.  While genlop -t
shows compile times, it doesn't average them out.  It's just rough in my
head quick math.  ;-)  I agree that Seamonkey may be a good option for
Daniel.

I use Seamonkey for my email and some web browsing.  While the new
Firefox has some advantages in some areas, Seamonkey does work well.  I
have both installed here. 

Dale

:-)  :-) 

P. S.  For those who keep up with my slow upgrades.  I just ordered a
FX-8350 CPU and 32GBs of ram.  The new Firefox with Content Process set
to 4 would use all my memory and cause my system to crash, reboot
actually.  I had to go back to one.  With the new 32GBs of ram, I hope
to be able to set it to 2, 3 or maybe 4.  For what I do, I think 2 would
be enough.  They should be here in a few days.  Sort of dread putting
the CPU in.  Always concerned something could go sideways.  :/  Old
parts will go on a older mobo I have.  It may turn into a server for all
those hard drives I need to have.  lol 


  reply	other threads:[~2018-11-24  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18  7:35 [gentoo-user] Firefox and Thunderbird compile issue Daniel Frey
2018-11-18 10:47 ` Alarig Le Lay
2018-11-18 17:52   ` Daniel Frey
2018-11-18 18:19     ` [gentoo-user] " Nuno Silva
2018-11-18 19:01       ` Daniel Frey
2018-11-20 17:46         ` Nuno Silva
2018-11-24  8:29           ` Dale [this message]
2018-11-24  8:58             ` Neil Bothwick
2018-11-24  9:13               ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35804e36-7200-e68e-1314-a42957b788ac@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox