From: Peter Weilbacher <newsspam@weilbacher.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: firefox-bin optimizations?
Date: Sat, 09 Oct 2010 17:48:51 +0200 [thread overview]
Message-ID: <i8q2t3$81m$1@dough.gmane.org> (raw)
In-Reply-To: <20101005054908.GA22391@waltdnes.org>
On 05.10.2010 07:49, Walter Dnes wrote:
> On Thu, Sep 30, 2010 at 12:37:10PM -0700, walt wrote
>> On 09/30/2010 05:30 AM, Mark David Dumlao wrote:
>>> On Thu, Sep 30, 2010 at 8:00 PM, Johannes Kimmel<johannes.kimmel@gmx.de> wrote:
>>>> On 09/30/2010 12:58 PM, Mark David Dumlao wrote:
>>>>>
>>>>> Heya,
>>>>> I noticed that my firefox-bin is a lot smaller in memory footprint
>>>>> compared to ordinary gentoo-compiled firefox.
>>>>>
>>>>> Does anyone know what compiler flags upstream applies to their
>>>>> firefox?
>>
>> Try entering about:buildconfig in the URL bar.
>
> I tried it, and for good measure, did some spelunking in the
> .configure file in the firefox tarball. I have some questions, before
> possibly tweaking the Firefox ebuild and/or .configure on my machine...
>
> --enable-application=xulrunner
> will Firefox run without this?
>
> --enable-pango
> will Firefox run without this? I have the "moznopango" flag set, which
> is supposed to speed things up, but about:buildconfig indicates that
> pango is enabled.
>
> --disable-strip --disable-strip-libs --disable-install-strip
> Why? I thought most packages stripped code after install.
>
> --enable-default-toolkit=cairo-gtk2
> will Firefox run without this?
>
> --enable-oji
> will Firefox run without this? And what is "oji"? I can't find any
> mention of what it does.
>
> --enable-mathml
> I don't really need it right now.
>
> --enable-storage
> will Firefox run without this? The help says...
> "Enable mozStorage module and related components". Can someone please
> give a short explanation in plain English what this does?
>
> --disable-ogg
> One thing I might consider enabling. Is there a problem with Firefox's
> ogg support, or any other reason to disable it?
And you see all those options listed in firefox-bin buildconfig? Then this
is surely not the Firefox built by upstream (mozilla.com). They would only
use a minimal set of build options not all the rubbish (most of which is
currently ignored or just obsolete) that the Gentoo non-bin ebuilds set.
Peter.
prev parent reply other threads:[~2010-10-09 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 10:58 [gentoo-user] firefox-bin optimizations? Mark David Dumlao
2010-09-30 12:00 ` Johannes Kimmel
2010-09-30 12:30 ` Mark David Dumlao
2010-09-30 19:37 ` [gentoo-user] " walt
2010-09-30 20:36 ` Mark David Dumlao
2010-10-05 5:49 ` Walter Dnes
2010-10-05 13:12 ` Bill Longman
2010-10-05 15:16 ` walt
2010-10-06 3:27 ` Walter Dnes
2010-10-07 4:55 ` Walter Dnes
2010-10-07 7:52 ` William Kenworthy
2010-10-07 7:59 ` William Kenworthy
2010-10-07 9:03 ` Arttu V.
2010-10-09 5:17 ` Walter Dnes
2010-10-09 15:53 ` Arttu V.
2010-10-12 3:19 ` Walter Dnes
2010-10-14 4:12 ` Walter Dnes
2010-10-14 14:21 ` Paul Hartman
2010-10-09 15:54 ` Peter Weilbacher
2010-10-09 15:48 ` Peter Weilbacher [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='i8q2t3$81m$1@dough.gmane.org' \
--to=newsspam@weilbacher.org \
--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