Changeset 9a469bc

Timestamp:

10/28/2018 09:15:43 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, 8.4, 9.0, 9.1, bdubbs/svn, elogind, 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:

2bd2dce

Parents:

7810f94

Message:

Firefox: stop recommending system ICU, and use clang to save build space.

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

Files:

• introduction/welcome/changelog.xml (modified) (1 diff)
• xsoft/graphweb/firefox.xml (modified) (8 diffs)

introduction/welcome/changelog.xml

@@ -46 +46 @@
       <itemizedlist>
         <listitem>
+          <para>[ken] - Change the firefox instructions: stop recommending system
+          ICU because the build fails with the current version, and change to
+          using clang which saves build space (measurement is for 7.0, but 6.0 is
+          good enough and smaller).</para>
+        </listitem>
+        <listitem>
           <para>[ken] - Update to xorg-server-1.20.3 [security fix]. Fixes
           <ulink url="&blfs-ticket-root;11284">#11284</ulink>.</para>

xsoft/graphweb/firefox.xml

@@ -11 +11 @@
   <!-- 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     "9.9 GB (141 MB installed) without tests">
-  <!ENTITY firefox-time          "30 SBU (with parallelism=4) without tests">
+  <!ENTITY firefox-buildsize     "9.0 GB (153 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 in
+   doubt, round up -->
+  <!ENTITY firefox-time          "22 SBU (with parallelism=4) without tests">
 ]>
 
@@ -154 +157 @@
     <bridgehead renderas="sect4">Recommended</bridgehead>
     <para role="recommended">
-      <xref linkend="icu"/>,
+<!--  <xref linkend="icu"/>, with icu <61 or >62, JSContext FTBFS -->
       <xref linkend="libevent"/>,
       <xref linkend="libvpx"/>,
@@ -243 +246 @@
 ac_add_options --disable-gconf
 
-# Uncomment this if you have not installed nodejs
-# but note that nodejs will be required in firefox-64 
-#ac_add_options --disable-nodejs 
+# Uncomment this if you have not installed nodejs,
+# but note that nodejs will be required in firefox-64
+#ac_add_options --disable-nodejs
 
 # From firefox-61, the stylo CSS code can no-longer be disabled
@@ -256 +259 @@
 ac_add_options --with-system-nspr
 ac_add_options --with-system-nss
-ac_add_options --with-system-icu
+
+# Only enable system icu if the version is 61 or 62
+#ac_add_options --with-system-icu
+
+# The gold linker is no-longer the default
+ac_add_options --enable-linker=gold
+
+# You cannot distribute the binary if you do this
+ac_add_options --enable-official-branding
 
 # If you are going to apply the patch for system graphite
@@ -280 +291 @@
 # Optimization for size is broken with gcc7 and later
 ac_add_options --enable-optimize="-O2"
-
-ac_add_options --enable-official-branding
 
 # From firefox-61 system cairo is not supported
@@ -345 +354 @@
     </para>
 
-<screen><userinput>./mach build</userinput></screen>
+<screen><userinput>export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib &amp;&amp;
+./mach build &amp;&amp;
+unset CC CXX AR NM RANLIB</userinput></screen>
 
     <para>
@@ -382 +393 @@
 
     <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.
+    </para>
+
+    <para>
       <command>./mach build</command>: <application>Firefox</application>
       now uses this <application>python2</application> script to run the
@@ -391 +408 @@
       need details of which files are being compiled, together with any C or
       C++ flags being used.
+    </para>
+
+    <para>
+      <option>./mach build -j4</option>: In theory, <command>mach</command>
+      will use the number of online CPU cores - but on some machines the bulk
+      of the build will drag on as if only 1 core is present. Specifying the
+      number of jobs (4 in this example) fixes that.  Unlike traditional
+      recommendations for running <command>make</command>, the exact number
+      of cores is usually fastest - exceptionally, N+1 may be better on a
+      well-specified modern machine. But do NOT use this if building from a
+      term where <command>taskset</command> has been used to restrict the
+      available cores.
     </para>