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 03:13:23 -0600 [thread overview]
Message-ID: <c573e523-62c3-e237-fc12-6efc13c8398e@gmail.com> (raw)
In-Reply-To: <20181124085840.2f9c1329@phoucgh.digimed.co.uk>
Neil Bothwick wrote:
> On Sat, 24 Nov 2018 02:29:10 -0600, Dale wrote:
>
>> 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. ;-)
> Try genlop -i or qlop -t
>
>
I need to read the man pages every once in a while. I don't recall
seeing that there last I looked. Still, it also includes when I install
from a pre-built binary which takes only a few seconds or a minute or
so. That throws off the average a bit. Sometimes a upgrade goes a
little sideways. When doing it in my head, I ignore those. Still
interesting to know about the -i option tho.
Going by the output of the -i tho, Seamonkey only takes a little longer
than Firefox. Of course, I've had to go back to a pre-built binary a
couple times with Firefox recently. Accounting for that, I suspect they
are roughly the same.
Thanks for sharing the -i info. Interesting.
Dale
:-) :-)
prev parent reply other threads:[~2018-11-24 9:13 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
2018-11-24 8:58 ` Neil Bothwick
2018-11-24 9:13 ` Dale [this message]
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=c573e523-62c3-e237-fc12-6efc13c8398e@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