Changeset ca97a2a


Ignore:
Timestamp:
01/24/2022 08:14:04 PM (4 months ago)
Author:
Ken Moffat <ken@…>
Branches:
11.1, lazarus, trunk, xry111/intltool, xry111/test-20220226
Children:
0044091
Parents:
da58f1a
Message:

Update to rustc-1.58.1.

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • general/prog/rust.xml

    rda58f1a rca97a2a  
    77  <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz">
    88  <!ENTITY rust-download-ftp  " ">
    9   <!ENTITY rust-md5sum        "6d1728cf0a86b0c5f33d3870379997ed">
    10   <!ENTITY rust-size          "172 MB">
     9  <!ENTITY rust-md5sum        "275744c77bf07fd07abe0fd829e6dafb">
     10  <!ENTITY rust-size          "176 MB">
    1111  <!-- Gentle Reminder: buildsize is how much the user requires for the real
    1212       install, i.e. the source with its DESTDIR *plus* the DESTDIR.  You
     
    1414       to measure it, or du -sm to look at the size of the build tree before and
    1515       after the tests. -->
    16 
    17   <!ENTITY rust-buildsize     "8.8 GB (370 MB installed) including 309 MB of ~/.cargo files for the user building this. Add 6.2 GB including extra 273 MB of ~/.cargo files if running the tests">
    18   <!ENTITY rust-time          "27 SBU (including download time; add 13 SBU for tests, both on a 4-core machine)">
     16       
     17  <!ENTITY rust-buildsize     "8.7 GB (417 MB installed) including 296 MB of ~/.cargo files for the user building this. Add 6.5 GB including extra 281 MB of ~/.cargo files if running the tests">
     18  <!ENTITY rust-time          "25 SBU (including download time; add 13 SBU for tests, both on a 4-core machine)">
    1919]>
    2020
     
    8484        have reason to rebuild with a modified configuration (e.g. using the
    8585        shipped LLVM after building with shared LLVM, perhaps to compile crates
    86         for architectres which the BLFS LLVM build does not support)
     86        for architectures which the BLFS LLVM build does not support)
    8787        it is possible for the install to leave a broken
    8888        <command>cargo</command> program. In such a situation, either remove
     
    308308    </para>
    309309
     310<!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used
    310311<screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \
    311312       -e '/^curl-sys /s/0.4.48/0.4.50/' \
    312        src/tools/cargo/Cargo.toml &amp;&amp;
    313 
    314 export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &amp;&amp;
     313       src/tools/cargo/Cargo.toml &amp;&amp; -->
     314
     315<screen><userinput>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &amp;&amp;
    315316python3 ./x.py build --exclude src/tools/miri</userinput></screen>
    316317
     
    333334
    334335    <para>
    335       At a minimum, fifteen tests will fail: all the tests (twelve) in
    336       the <quote>assembly</quote> suite, apparently because warnings are
    337       tuened on,
    338       run-make-fulldeps/long-linker-command-lines, run-make-fulldeps/print-cfg,
    339       run-make-fulldeps/sysroot-crates-are-unstable.
    340       If <command>gdb</command> is installed,  another failure
     336      At a minimum, 49 tests will fail: all 48 of the tests in
     337      the <quote>assembly</quote> suite which are not skipped (various lints
     338      cause the warnings in these tests to be treated as errors), and
     339      run-make-fulldeps/long-linker-command-lines.
     340<!--  If <command>gdb</command> is installed,  another failure
    341341      (debuginfo/function-names.rs) can be expected.
     342      # seems ok with 11.2 ken -->
    342343    </para>
    343344
     
    345346      As with all large testsuites, other tests might fail on some machines -
    346347      if the number of additional failures is in the single digits,
    347       check the log for 'FAILED' and review lines above that, particularly the
     348      check the log for 'failures:' and review lines above that, particularly the
    348349      'stderr:' lines. Any mention of
    349350      SIGSEGV or signal 11 in a failing test is a cause for concern.
     
    449450    </para>
    450451
    451     <para>
     452<!--<para>
    452453      <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates
    453454      normally downloaded for this release do not correctly initialise
     
    455456      <application>openssl-3.0.0</application>. Upstream has fixed that for a
    456457      future release, this sed causes the fixed versions to be used.
    457     </para>
     458    </para>-->
    458459
    459460    <para>
  • introduction/welcome/changelog.xml

    rda58f1a rca97a2a  
    4343    -->
    4444    <listitem>
     45      <para>January 24th, 2022</para>
     46      <itemizedlist>
     47        <listitem>
     48          <para>[ken] - Update to rustc-1.58.1 (Security Update). Fixes
     49          <ulink url="&blfs-ticket-root;16003">#16003</ulink>.</para>
     50        </listitem>
     51      </itemizedlist>
     52    </listitem>
     53
     54    <listitem>
    4555      <para>January 23rd, 2022</para>
    4656      <itemizedlist>
  • packages.ent

    rda58f1a rca97a2a  
    377377<!ENTITY ruby-version                 "&ruby-minor-version;.&ruby-patch-version;">
    378378<!ENTITY ruby-gemdir                  "/usr/lib/ruby/gems/&ruby-minor-version;.0">
    379 <!ENTITY rust-version                 "1.56.1">
     379<!ENTITY rust-version                 "1.58.1">
    380380<!ENTITY scons-version                "4.2.0">
    381381<!ENTITY slang-version                "2.3.2">
Note: See TracChangeset for help on using the changeset viewer.