Changeset ec2353a
- Timestamp:
- 03/17/2020 07:50:34 PM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 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, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- dca1247
- Parents:
- 4969ec3c
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
r4969ec3c rec2353a 1 1 <!-- $LastChangedBy$ $Date$ --> 2 2 3 <!ENTITY day "1 6"> <!-- Always 2 digits -->3 <!ENTITY day "17"> <!-- Always 2 digits --> 4 4 <!ENTITY month "03"> <!-- Always 2 digits --> 5 5 <!ENTITY year "2020"> -
general/graphlib/librsvg.xml
r4969ec3c rec2353a 5 5 %general-entities; 6 6 7 <!ENTITY librsvg-download-http "&gnome-download-http;/librsvg/2.4 6/librsvg-&librsvg-version;.tar.xz">8 <!ENTITY librsvg-download-ftp "&gnome-download-ftp;/librsvg/2.4 6/librsvg-&librsvg-version;.tar.xz">9 <!ENTITY librsvg-md5sum " aca4001b267de77924b786886a1ad64a">10 <!ENTITY librsvg-size "1 2MB">11 <!ENTITY librsvg-buildsize " 849 MB (add 375 MB for tests)">12 <!ENTITY librsvg-time " 1.7 SBU (add 1.2 SBU for tests)">7 <!ENTITY librsvg-download-http "&gnome-download-http;/librsvg/2.48/librsvg-&librsvg-version;.tar.xz"> 8 <!ENTITY librsvg-download-ftp "&gnome-download-ftp;/librsvg/2.48/librsvg-&librsvg-version;.tar.xz"> 9 <!ENTITY librsvg-md5sum "1f682259f2d11e786f283079e4ed02b7"> 10 <!ENTITY librsvg-size "13 MB"> 11 <!ENTITY librsvg-buildsize "1.3 GB (83 MB installed), add 616 MB for tests"> 12 <!ENTITY librsvg-time "2.3 SBU (on a 4-core machine), add 1.0 SBU for tests"> 13 13 ]> 14 14 … … 77 77 <para role="required"> 78 78 <xref linkend="gdk-pixbuf"/>, 79 <xref linkend="libcroco"/>,80 79 <xref linkend="cairo"/>, 81 80 <xref linkend="pango"/>, and … … 113 112 114 113 <para> 115 To test the results, issue: <command>make check</command>. Over 100 tests 116 fail as a result of problems with the test suite. These test failures 117 are primarily related to svg1.1, and are comparison problems due to 118 using a later version of Pango than what the developers created the 119 initial SVG files with. 114 To test the results, issue: <command>make check</command>. 115 <!-- https://gitlab.gnome.org/GNOME/librsvg/issues/511 --> 116 Many of the tests in 'reftests' may fail (45 failed in March 2020) because 117 they produce, and then diff, graphic files with text and the details such 118 as spacing vary when the system versions of cairo, freetype, pixman, pango 119 and perhaps harfbuzz differ from the versions on the system where the 120 reference files were created. 120 121 </para> 121 122 -
general/prog/rust.xml
r4969ec3c rec2353a 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 " e67432b37150f13e186ebfb67e5192fb">10 <!ENTITY rust-size "14 7MB">9 <!ENTITY rust-md5sum "b348233fdbbf7858763bab7cb9c314ae"> 10 <!ENTITY rust-size "146 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. --> 15 15 16 <!ENTITY rust-buildsize " 5.3GB (375 MB installed) including 429MB of ~/.cargo files for the user building this. Add 1.7GB if running the tests">17 <!ENTITY rust-time "24 SBU (add 1 3 SBU for tests, both with 4 processors)">16 <!ENTITY rust-buildsize "7.7 GB (607 MB installed) including 398 MB of ~/.cargo files for the user building this. Add 2.1 GB if running the tests"> 17 <!ENTITY rust-time "24 SBU (add 12 SBU for tests, both on a 4-core machine)"> 18 18 ]> 19 19 … … 42 42 <para> 43 43 This package is updated on a six-weekly release cycle. Because it is 44 such a large and slow package to build, and is at the moment only required 45 by a few packages in this book, the BLFS editors take the view that it 46 should only be updated when that is necessary (either to fix problems, 47 or to allow a new version of <application>firefox</application> to build). 44 such a large and slow package to build, is at the moment only required 45 by a few packages in this book, and particularly because newer versions 46 tend to break older mozilla packages, the BLFS editors take the view that 47 it should only be updated when that is necessary (either to fix problems, 48 or to allow a new version of a package to build). 48 49 </para> 49 50 … … 82 83 class="directory">/opt</filename> directory. In particular, if you 83 84 have reason to rebuild with a modified configuration (e.g. using the 84 shipped LLVM after building with shared LLVM, but perhaps alsothe85 reverse situation) it i tpossible for the install to leave a broken85 shipped LLVM after building with shared LLVM, or for the 86 reverse situation) it is possible for the install to leave a broken 86 87 <command>cargo</command> program. In such a situation, either remove 87 88 the existing installation first, or use a different prefix such as … … 167 168 </itemizedlist> 168 169 169 170 <!--<bridgehead renderas="sect3">Additional Downloads</bridgehead> 170 171 <itemizedlist spacing="compact"> 171 172 <listitem> … … 175 176 </para> 176 177 </listitem> 177 </itemizedlist> 178 </itemizedlist>--> 178 179 179 180 <bridgehead renderas="sect3">Rust Dependencies</bridgehead> … … 276 277 EOF</userinput></screen> 277 278 278 279 <!--<para> 279 280 Adapt rustc to allow it to build and function with the changes in LLVM-9: 280 281 </para> 281 282 282 <screen><userinput remap="pre">patch -Np1 -i ../rustc-&rust-version;-llvm9_fixes-1.patch</userinput></screen> 283 284 <para> 285 Now compile <application>Rust</application> by running the following283 <screen><userinput remap="pre">patch -Np1 -i ../rustc-&rust-version;-llvm9_fixes-1.patch</userinput></screen>--> 284 285 <para> 286 Compile <application>Rust</application> by running the following 286 287 commands: 287 288 </para> … … 316 317 <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename> 317 318 fails, presumably because we are using only stable features. 318 <!-- appears to be fixed now 319 <!-- https://github.com/rust-lang/rust/issues/63520 --> 320 A fifth test, run-make-fulldeps/linker-output-non-utf8, is broken. 321 <!-- gdb appears to be fixed now 319 322 If gdb has been installed, in some circumstances tests in 320 323 <filename class="directory">debuginfo</filename> may fail.--> As with all … … 324 327 'stderr:' lines. Any mention of 325 328 SIGSEGV or signal 11 in a failing test is a cause for concern. 326 A fifth test, run-make-fulldeps/linker-output-non-utf8, is known to fail.327 329 </para> 328 330 … … 335 337 336 338 <para> 337 That should report 1 6499 tests. Similarly, the total tests which failed can339 That should report 17349 tests. Similarly, the total tests which failed can 338 340 be found by running: 339 341 </para> … … 528 530 <seglistitem> 529 531 <seg> 530 cargo-clippy, cargo-fmt, cargo-miri, cargo, clippy-driver, miri, rls, rust-gdb, rust- lldb, rustc, rustdoc, rustfmt.532 cargo-clippy, cargo-fmt, cargo-miri, cargo, clippy-driver, miri, rls, rust-gdb, rust-gdbgui, rust-lldb, rustc, rustdoc, rustfmt. 531 533 </seg> 532 534 <seg> … … 651 653 </varlistentry> 652 654 655 <varlistentry id="rust-gdbgui"> 656 <term><command>rust-gdbgui</command></term> 657 <listitem> 658 <para> 659 is a wrapper script for a graphical front end to gdb that runs in a 660 browser. 661 </para> 662 <indexterm zone="rust rust-gdbgui"> 663 <primary sortas="b-rust-gdbgui">rust-gdbgui</primary> 664 </indexterm> 665 </listitem> 666 </varlistentry> 667 653 668 <varlistentry id="rust-lldb"> 654 669 <term><command>rust-lldb</command></term> -
gnome/platform/gnome-shell.xml
r4969ec3c rec2353a 81 81 <xref linkend="gnome-autoar"/>, 82 82 <xref linkend="gnome-control-center"/>, 83 <!-- FIXME in gnome-shell-3.36.0 libcroco will be included, 84 so when that goes in please archive libcroco --> 83 85 <xref linkend="libcroco"/>, 84 86 <xref linkend="mutter"/>, -
introduction/welcome/changelog.xml
r4969ec3c rec2353a 43 43 --> 44 44 <listitem> 45 <para>March 17th, 2020</para> 46 <itemizedlist> 47 <listitem> 48 <para>[ken] - Adjust seamonkey-2.53.0 to build with 49 rustc-1.39.0. Fixes 50 <ulink url="&blfs-ticket-root;13271">#13271</ulink>.</para> 51 </listitem> 52 <listitem> 53 <para>[ken] - Update to librsvg-2.48.0, and hence update to 54 rustc-1.39.0. Fixes 55 <ulink url="&blfs-ticket-root;13230">#13230</ulink>.</para> 56 </listitem> 57 </itemizedlist> 58 </listitem> 59 60 <listitem> 45 61 <para>March 16th, 2020</para> 46 62 <itemizedlist> -
packages.ent
r4969ec3c rec2353a 214 214 <!ENTITY libmypaint-version "1.5.1"> <!-- version 1 only --> 215 215 <!ENTITY libpng-version "1.6.37"> 216 <!ENTITY librsvg-version "2.4 6.4"> <!-- Normally even minors -->216 <!ENTITY librsvg-version "2.48.0"> <!-- Normally even minors --> 217 217 <!ENTITY libraw-version "0.19.5"> 218 218 <!ENTITY libtiff-version "4.1.0"> … … 353 353 <!ENTITY ruby-patch-version "0"> 354 354 <!ENTITY ruby-version "&ruby-minor-version;.&ruby-patch-version;"> 355 <!ENTITY rust-version "1.3 7.0">355 <!ENTITY rust-version "1.39.0"> 356 356 <!ENTITY scons-version "3.1.2"> 357 357 <!ENTITY slang-version "2.3.2"> -
xsoft/graphweb/firefox.xml
r4969ec3c rec2353a 15 15 most practical way to get a timing on a machine with more cores, if taking 16 16 cores offline is not practical. If in doubt, round up --> 17 <!ENTITY firefox-time "23 SBU ( with parallelism=4) without tests">17 <!ENTITY firefox-time "23 SBU (on a 4-core machine) without tests"> 18 18 ]> 19 19 -
xsoft/graphweb/seamonkey.xml
r4969ec3c rec2353a 10 10 <!ENTITY seamonkey-size "277 MB"> 11 11 <!ENTITY seamonkey-buildsize "6.9 GB (154 MB installed)"> 12 <!ENTITY seamonkey-time "19 SBU ( using parallelism=4)">12 <!ENTITY seamonkey-time "19 SBU (on a 4-core machine)"> 13 13 ]> 14 14 … … 220 220 ac_add_options --with-system-nss 221 221 ac_add_options --with-system-icu 222 223 222 <!-- seems OK with icu-60, seamonkey-2.49 224 223 # Use the internal version of icu due to execution problems--> … … 280 279 281 280 <screen><userinput>sed -i -e '/pid_t gettid/,+3 s@^@//@' mozilla/tools/profiler/core/platform.h</userinput></screen> 281 282 <para> 283 No adapt the code for a change introduced in rustc-1.39.0: 284 </para> 285 286 <screen><userinput>sed -i '/deny(warnings)/d' mozilla/xpcom/rust/nsstring/src/lib.rs</userinput></screen> 287 282 288 <!-- Doesn't seem to be needed anymore with 2.53.1 283 289 <para> … … 362 368 </para> 363 369 --> 370 <para> 371 <command>sed -i '/deny(warnings)/d' ...</command> : rust-1.39 deprecated 372 the "try!" call in favour of "?" which causes warnings, nsstring was 373 treating warnings as errors. 374 </para> 375 364 376 <para> 365 377 <command>make -f client.mk</command>: Mozilla products are packaged to -
xsoft/other/thunderbird.xml
r4969ec3c rec2353a 10 10 <!ENTITY thunderbird-size "316 MB"> 11 11 <!ENTITY thunderbird-buildsize "8.9 GB (145 MB installed)"> 12 <!ENTITY thunderbird-time "27 SBU (with -j4, estimated 81 SBU with -j1)"> 13 <!-- Verified the time at -j1 on another system for posterity's sake. --> 12 <!ENTITY thunderbird-time "27 SBU (on a 4-core machine)"> 13 <!-- Removed the -j1 time because python and rust do not obey it, although 14 the C/C++ code appears to obey it --> 14 15 ]> 15 16 … … 154 155 155 156 <screen><userinput>cat > mozconfig << "EOF" 156 <literal># If you have a multicore machine, the build may be faster if using parallel 157 # jobs. The build system automatically adds -jN to the "make" flags, where N 158 # is the number of CPU cores. The option below is therefore useless, unless 159 # you want to use a smaller number of jobs: 157 <literal># If you have a multicore machine, all cores will be used. 158 # The option below may cause parts of the build to only use one core 159 # if you want to use a smaller number of jobs: 160 160 #mk_add_options MOZ_MAKE_FLAGS="-j1" 161 161 162 162 163 # If you have installed dbus-glib, comment out this line:
Note:
See TracChangeset
for help on using the changeset viewer.