enable static flag in mozilla-firefox mozilla-thunderbird mozilla ebuilds. We system tuners like it, because with static linking programs start faster. Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is too drastic to make part of the ebuild. You're free to add flags in make.conf etc, but this isn't something we're prepared to do.
Acctually it's only a small change that needs to be done for mozconfig.eclass. I agree that this would be nice to have! --- mozconfig.eclass 2005-03-24 04:06:21.000000000 +0100 +++ mozconfig.eclass.static 2005-03-30 12:06:35.000000000 +0200 @@ -7,7 +7,7 @@ ECLASS=mozconfig INHERITED="$INHERITED $ECLASS" -IUSE="java gnome ldap debug xinerama xprint moznoxft" +IUSE="java gnome ldap debug xinerama xprint moznoxft static" case ${PN} in mozilla) IUSE="${IUSE} mozdevelop mozxmlterm mozsvg" ;; *firefox) IUSE="${IUSE} mozdevelop mozxmlterm" ;; @@ -194,6 +194,16 @@ fi fi + if use static; then + mozconfig_annotate +static \ + --enable-static \ + --disable-shared + else + moconfig_annotate -static \ + --enable-shared \ + --disable-static + fi + # Here is a strange one... if is-flag '-mcpu=ultrasparc*'; then mozconfig_annotate "building on ultrasparc" --enable-js-ultrasparc
Please reconsider/reopen. Mozilla static builds are well documented and supported by Mozilla Organization: http://www.mozilla.org/build/static-build.html They are not like traditional static builds. The system libraries get still linked dinamically. Only mozilla internal components get statically linked to the "*-bin" executable. This make sense, since those components are not shared between aplications. By using a static build you get a faster executable (start and runtime). Official firefox releases by Mozilla.org are statically linked (see size of *-bin executable and the missing shared libraries, or check "about:buildconfig") (And I guess official Thunderbird realeases also). Since the meaning of mozilla static build is not the same of a traditional static built application (ie. system libraries still get linked dinamically) I suggest we should create a new USE flag (mozstatic?)