Changeset ebffd4b

Timestamp:

06/14/2024 10:48:38 AM (2 weeks ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

trunk

Children:

d09f8bcc

Parents:

68df8455

git-author:

Xi Ruoyao <xry111@…> (06/14/2024 06:15:35 AM)

git-committer:

Xi Ruoyao <xry111@…> (06/14/2024 10:48:38 AM)

Message:

Update to rustc-1.79.0 (#19953)

Files:

• general/prog/rust.xml (modified) (6 diffs)
• introduction/welcome/changelog.xml (modified) (1 diff)
• packages.ent (modified) (1 diff)

general/prog/rust.xml

@@ -7 +7 @@
   <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.xz">
   <!ENTITY rust-download-ftp  " ">
-  <!ENTITY rust-md5sum        "ce1c084daec811aac07951cc954e7809">
-  <!ENTITY rust-size          "152 MB">
+  <!ENTITY rust-md5sum        "1a00ff85d5fdb48ddbe534dcf1f6183f">
+  <!ENTITY rust-size          "155 MB">
   <!ENTITY rust-buildsize     "8.9 GB (298 MB installed); add 6.4 GB if running the tests">
   <!ENTITY rust-time          "6.7 SBU (including download time; add 6.2 SBU for tests, both using parallelism=8)">
@@ -239 +239 @@
 # and updated it to follow the major changes of the building system,
 # so x.py will not warn us to do such a review.
-change-id = 121754
+change-id = 123711
 
 [llvm]
@@ -351 +351 @@
          https://github.com/rust-lang/rust/pull/115869, see my comment
 
-         regression-bad-location-list-67992.rs: rust bug or gdb bug ???? -->
+         regression-bad-location-list-67992.rs: rust bug or gdb bug ????
+
+         2024-06-14: Test result is clean with 1.79.0
     <para>
       Three tests, <filename>tests/ui/error-emitter/highlighting.rs</filename>,
@@ -357 +359 @@
       <filename>tests/debuginfo/regression-bad-location-list-67992.rs</filename>,
       are known to fail.
-    </para>
+    </para> -->
+
 <!-- Let's just comment this out.  Nobody has tested on a system w/o
      FileCheck for a long time.
@@ -367 +370 @@
 -->
     <para>
-      As with all large test suites, other tests might fail on some machines -
+      As with all large test suites, some tests might fail on some machines -
       if the number of additional failures is low,
       check the log for 'failures:' and review lines above that, particularly the
@@ -386 +389 @@
     <para>
       Therefore, you should determine the number of failures.
-    </para>
-
-    <para>
       The number of tests which passed and failed can be found by running:
     </para>

introduction/welcome/changelog.xml

@@ -39 +39 @@
     </listitem>
     -->
+
+    <listitem>
+      <para>June 14th, 2024</para>
+      <itemizedlist>
+        <listitem>
+          <para>[xry111] - Update to rustc-1.79.0.  Fixes
+          <ulink url="&blfs-ticket-root;19953">#19953</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
 
     <listitem>

packages.ent

@@ -377 +377 @@
 <!ENTITY ruby-version                 "&ruby-minor-version;.&ruby-patch-version;">
 <!ENTITY ruby-gemdir                  "/usr/lib/ruby/gems/&ruby-minor-version;.0">
-<!ENTITY rust-version                 "1.78.0">
+<!ENTITY rust-version                 "1.79.0">
 <!ENTITY rust-bindgen-version         "0.69.4">
 <!ENTITY scons-version                "4.7.0">