Changeset ca97a2a
- Timestamp:
- 01/24/2022 08:14:04 PM (2 years ago)
- Branches:
- 11.1, 11.2, 11.3, 12.0, 12.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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 0044091
- Parents:
- da58f1a
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
rda58f1a rca97a2a 7 7 <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz"> 8 8 <!ENTITY rust-download-ftp " "> 9 <!ENTITY rust-md5sum " 6d1728cf0a86b0c5f33d3870379997ed">10 <!ENTITY rust-size "17 2MB">9 <!ENTITY rust-md5sum "275744c77bf07fd07abe0fd829e6dafb"> 10 <!ENTITY rust-size "176 MB"> 11 11 <!-- Gentle Reminder: buildsize is how much the user requires for the real 12 12 install, i.e. the source with its DESTDIR *plus* the DESTDIR. You … … 14 14 to measure it, or du -sm to look at the size of the build tree before and 15 15 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 273MB of ~/.cargo files if running the tests">18 <!ENTITY rust-time "2 7SBU (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)"> 19 19 ]> 20 20 … … 84 84 have reason to rebuild with a modified configuration (e.g. using the 85 85 shipped LLVM after building with shared LLVM, perhaps to compile crates 86 for architect res which the BLFS LLVM build does not support)86 for architectures which the BLFS LLVM build does not support) 87 87 it is possible for the install to leave a broken 88 88 <command>cargo</command> program. In such a situation, either remove … … 308 308 </para> 309 309 310 <!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used 310 311 <screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \ 311 312 -e '/^curl-sys /s/0.4.48/0.4.50/' \ 312 src/tools/cargo/Cargo.toml && 313 314 export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &&313 src/tools/cargo/Cargo.toml && --> 314 315 <screen><userinput>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" && 315 316 python3 ./x.py build --exclude src/tools/miri</userinput></screen> 316 317 … … 333 334 334 335 <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 341 341 (debuginfo/function-names.rs) can be expected. 342 # seems ok with 11.2 ken --> 342 343 </para> 343 344 … … 345 346 As with all large testsuites, other tests might fail on some machines - 346 347 if the number of additional failures is in the single digits, 347 check the log for ' FAILED' and review lines above that, particularly the348 check the log for 'failures:' and review lines above that, particularly the 348 349 'stderr:' lines. Any mention of 349 350 SIGSEGV or signal 11 in a failing test is a cause for concern. … … 449 450 </para> 450 451 451 452 <!--<para> 452 453 <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates 453 454 normally downloaded for this release do not correctly initialise … … 455 456 <application>openssl-3.0.0</application>. Upstream has fixed that for a 456 457 future release, this sed causes the fixed versions to be used. 457 </para> 458 </para>--> 458 459 459 460 <para> -
introduction/welcome/changelog.xml
rda58f1a rca97a2a 43 43 --> 44 44 <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> 45 55 <para>January 23rd, 2022</para> 46 56 <itemizedlist> -
packages.ent
rda58f1a rca97a2a 377 377 <!ENTITY ruby-version "&ruby-minor-version;.&ruby-patch-version;"> 378 378 <!ENTITY ruby-gemdir "/usr/lib/ruby/gems/&ruby-minor-version;.0"> 379 <!ENTITY rust-version "1.5 6.1">379 <!ENTITY rust-version "1.58.1"> 380 380 <!ENTITY scons-version "4.2.0"> 381 381 <!ENTITY slang-version "2.3.2">
Note:
See TracChangeset
for help on using the changeset viewer.