Changeset e399c12 for xsoft/graphweb/firefox.xml

Timestamp:

05/21/2019 04:35:28 PM (5 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 9.0, 9.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

ba6d702

Parents:

77deb22e

Message:

Firefox-67.0

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@21615 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• xsoft/graphweb/firefox.xml (modified) (11 diffs)

xsoft/graphweb/firefox.xml

@@ -7 +7 @@
   <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;/source/firefox-&firefox-version;.source.tar.xz">
   <!ENTITY firefox-download-ftp  " ">
-  <!ENTITY firefox-md5sum        "a3d00fb4e950558135f08a5155745d4e">
-  <!ENTITY firefox-size          "269 MB">
+  <!ENTITY firefox-md5sum        "41a5d504deaed12ebf0e25bb1420f08">
+  <!ENTITY firefox-size          "270 MB">
   <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
     But the extra cached cargo files, if any, seem to be minimal -->
-  <!ENTITY firefox-buildsize     "11.8 GB (156 MB installed) without tests">
+  <!ENTITY firefox-buildsize     "3.8 GB (154 MB installed) without tests">
   <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
    most practical way to get a timing on a machine with more cores, if taking
    cores offline is not practical. If in doubt, round up -->
-  <!ENTITY firefox-time          "25 SBU (with parallelism=4) without tests">
+  <!ENTITY firefox-time          "28 SBU (with parallelism=4) without tests">
 ]>
 
@@ -139 +139 @@
       <xref linkend="autoconf213"/>,
       <xref linkend="cbindgen"/>,
-      <application>Clang</application> (from <xref linkend="llvm"/>),
       both <xref linkend="gtk3"/> and
       <xref linkend="gtk2"/>,
@@ -162 +161 @@
 <!-- fails to build in 65.0 (headers changed)
       <xref linkend="libvpx"/>, -->
-      <xref linkend="libwebp"/>, and
+      <xref linkend="libwebp"/>,
+      <xref linkend="nasm"/>, and
       <xref linkend="sqlite"/>
     </para>
@@ -257 +257 @@
 ac_add_options --with-system-icu
 
-# The gold linker is no-longer the default
-ac_add_options --enable-linker=gold
-
-# The shipped libdavid (av1 decoder) is not built by default,
-# at least on linux, but if nasm is not present libxul tries to
-# link to one of libdavid's objects and fails.  It is thought
-# libdavid will be enabled in firefox-67, at which point nasm
-# might be required.
-ac_add_options --disable-av1
+# Do not specify the gold linker which is not the default. It will take
+# longer and use more disk space when debug symbols are disabled.
+
+# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
+# has not been installed.
+#ac_add_options --disable-av1
 
 # You cannot distribute the binary if you do this
@@ -279 +276 @@
 #ac_add_options --disable-strip
 #ac_add_options --disable-install-strip
+
+# Disabling debug symbols makes the build much smaller and a little
+# faster. Comment this if you need to run a debugger.
+ac_add_options --disable-debug-symbols
 
 # The BLFS editors recommend not changing anything below this line:
@@ -290 +291 @@
 ac_add_options --disable-tests
 
-# With clang, unlike gcc-7 and later, the default level
-# of optimization produces a working build.
+# The default level of optimization again produces a working build with gcc.
 ac_add_options --enable-optimize
 
@@ -362 +362 @@
 
     <para>
-<!--  Invoke the Python script to compile the package: -->
-      To use the system version of ICU, run a sed to avoid a conflict between
+      If you are still using ICU-63, run a sed to avoid a conflict between
       upstream ICU's use of <literal>CheckImpl()</literal> in their public headers
       and firefox's internal use of a different <literal>CheckImpl()</literal>.
-      Then invoke the Python2 script to compile the package.
-    </para>
-
-<screen><userinput>sed -e 's/checkImpl/checkFFImpl/g' -i js/src/vm/JSContext*.h &amp;&amp;
-export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib &amp;&amp;
+    </para>
+
+<screen role="nodump"><userinput>sed -e 's/checkImpl/checkFFImpl/g' -i js/src/vm/JSContext*.h</userinput></screen>
+
+    <para>
+      Invoke the Python2 script to compile the package.
+    </para>
+
+<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
 export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
 ./mach build</userinput></screen>
@@ -398 +401 @@
     </para>
 
-<screen><userinput>unset CC CXX AR NM RANLIB MOZBUILD_STATE_PATH</userinput></screen>
+<screen><userinput>unset CC CXX MOZBUILD_STATE_PATH</userinput></screen>
 
   </sect2>
@@ -407 +410 @@
     <para>
       <command>sed -e 's/checkImpl/checkFFImpl/g' ...</command>: Although the
-      package ships with a modified version of <application>ICU-59</application>
-      and only tests that the system version, if requested, is at least 59,
-      changes in <emphasis>some</emphasis> versions cause builds with the system
-      version to fail with error messages of the form <literal>no void
-      JSContext::checkImpl_NN member function</literal> where NN is the system
-      <application>ICU</application> version. The sed renames the local function.
-    </para>
-
-    <para>
-      <command>export CC=clang CXX=clang++ ...</command>: Upstream now use
-      <application>clang</application> and building with any recent version
-      saves a lot of space.
+      package ships with a modified version of <application>ICU-63</application>
+      and only tests that the system version, if used, is at least 63, changes
+      from upstream 63 cause builds with the system version to fail with an error
+      message <literal>no void JSContext::checkImpl_63 member function</literal>.
+      The sed renames the local function. Upstream ICU-64 works around this.
+    </para>
+
+    <para>
+      <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
+      <application>clang</application>, but gcc is a more secure compiler and
+      now produces reasonably-sized builds.
     </para>
 
@@ -454 +456 @@
       of cores, e.g. -j4 for 4 cores: First, if using all the cores causes
       the build to swap because you have insufficient memory (e.g. for 4 cores
-      a build without system graphite2 and harfbuzz now uses slightly over 8GB
+      a build without system graphite2 and harfbuzz now uses towards 8GB
       of RAM). In such cases, using fewer cores can be faster. Second, on some
       machines the middle part of the build can drag on as if only one core is
@@ -474 +476 @@
       class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
       symbolic link is made to keep all the plugins installed in one folder.
+    </para>
+
+    <para>
+      <option>export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib</option>:
+      Use this as an alternative to building with gcc and g++ if you wish to use
+      the clang toolchain. Remember to unset these variables after the build.
     </para>