Changeset 69d1a8e for general/prog/rust.xml

Timestamp:

03/31/2020 02:23:02 AM (3 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, ken/inkscape-core-mods, lazarus, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226

Children:

876948d

Parents:

73db5703

Message:

Update to rustc-1.42.0 to again use system llvm for a smaller build,
but indicate why system llvm is a bad idea if using earlier llvm.
Patch seamonkey for this rustc version, its build is much slower.

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

File:

• general/prog/rust.xml (modified) (7 diffs)

general/prog/rust.xml

@@ -7 +7 @@
   <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz">
   <!ENTITY rust-download-ftp  " ">
-  <!ENTITY rust-md5sum        "b348233fdbbf7858763bab7cb9c314ae">
-  <!ENTITY rust-size          "146 MB">
+  <!ENTITY rust-md5sum        "ff5731326898a7010403e1b148375de4">
+  <!ENTITY rust-size          "130 MB">
   <!-- Gentle Reminder: buildsize is how much the user requires for the real
        install, i.e. the source with its DESTDIR *plus* the DESTDIR.  You
@@ -15 +15 @@
        after the tests. -->
 
-  <!ENTITY rust-buildsize     "9.0 GB (747 MB installed) including 344 MB of ~/.cargo files for the user building this. Add 2.3 GB if running the tests">
-  <!ENTITY rust-time          "52 SBU (add 15 SBU for tests, both on a 4-core machine)">
+  <!ENTITY rust-buildsize     "5.7 GB (250 MB installed) including 344 MB of ~/.cargo files for the user building this. Add 2.5 GB if running the tests">
+  <!ENTITY rust-time          "33 SBU (add 17 SBU for tests, both on a 4-core machine)">
 ]>
 
@@ -188 +188 @@
     </para>
 
-<!--<bridgehead renderas="sect4">Recommended</bridgehead>
+    <bridgehead renderas="sect4">Recommended</bridgehead>
     <para role="recommended">
       <package>clang</package> from <xref linkend="llvm"/>
       (built with -DLLVM_LINK_LLVM_DYLIB=ON so that rust can link to
       system LLVM instead of building its shipped version)
-    </para> FIXME reinstate when next using system llvm -->
+      If using an older version, see the config.toml file below re
+      using the shipped llvm, because of rust issue 69225.
+    </para>
 
     <bridgehead renderas="sect4">Optional</bridgehead>
@@ -237 +239 @@
 <screen><userinput>cat &lt;&lt; EOF &gt; config.toml
 <literal># see config.toml.example for more possible options
-# See the 9.1 book for an example using system LLVM
-# e.g. if you are still using llvm-9.0.1
+# See the 8.4 book for an example using shipped LLVM
+# e.g. if not installing clang, or using a version before 10.0
 [llvm]
 # by default, rust will build for a myriad of architectures
@@ -305 +307 @@
       <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename>
       fails, presumably because we are using only stable features.
-      <!-- https://github.com/rust-lang/rust/issues/63520 -->
-      A fifth test, run-make-fulldeps/linker-output-non-utf8, is broken.
       <!-- gdb appears to be fixed now
       If gdb has been installed, in some circumstances tests in
@@ -318 +318 @@
 
     <para>
-      Therefore, you should determine the number of tests, failures, etc. The
-      total number of tests which were considered is found by running:
-    </para>
-
-<screen remap="test"><userinput>grep 'running .* tests' rustc-testlog | awk '{ sum += $2 } END { print sum }'</userinput></screen>
-
-    <para>
-      That should report 17349 tests. Similarly, the total tests which failed can
-      be found by running:
+      If you get any <emphasis>other</emphasis> failing test which reports an
+      issue number then you should search for that issue.  For example, when
+      rustc &gt;= 1.41.1 is built with a version of sysllvm before 10.0 the test
+      for issue 69225 fails <ulink
+      url="https://github.com/rust-lang/rust/issues/69225"/> and that should be
+      regarded as a critical failurei (they released 1.41.1 because of it).
+      Most other failures will not be critical.
+    </para>
+
+    <para>
+      Therefore, you should determine the number of failures. The total number
+      of tests varies depending on which dependencies are present, e.g. more
+      will be run if <command>gdb</command> is available. If you wish, the
+      total number which were considered can be found if you run:
+    </para>
+
+<screen remap="test"><userinput>egrep 'running [[:digit:]]+ test' rustc-testlog | awk '{ sum += $2 } END { print sum }'</userinput></screen>
+
+    <para>
+      More importantly, the total of tests which failed can be found by running:
     </para>
 
@@ -332 +343 @@
 
     <para>
-      And similarly for the tests which passed use $4, for those which were ignored
-      (i.e. skipped) use $8 (and $10 for 'measured', $12 for 'filtered out' but both
-      are probably zero). The breakdown does not quite match the overall total.
+      And similarly if you care about how many tests passed use $4, for those
+      which were ignored (i.e. skipped) use $8 (and $10 for 'measured', $12 for
+      'filtered out' but both are probably zero).
     </para>