Changeset 5e8edab5


Ignore:
Timestamp:
05/24/2019 02:26:17 AM (5 years ago)
Author:
DJ Lucas <dj@…>
Branches:
elogind
Children:
8eebfaa5
Parents:
215c728b
Message:

Merge to HEAD 21618.

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

Files:
43 edited
1 moved

Legend:

Unmodified
Added
Removed

  • archive/x7driver-vmmouse.xml

    r215c728b r5e8edab5  
    5353      &lfs84_checked;
    5454      <!-- I used this with both VMWare and QEMU. -->
     55      <!-- with Kernel 5.1, this package is now obsolete and will cause X to crash.-->
    5556
    5657      <bridgehead renderas="sect4">Package Information</bridgehead>

  • general.ent

    r215c728b r5e8edab5  
    11<!-- $LastChangedBy$ $Date$ -->
    22
    3 <!ENTITY day          "18">                   <!-- Always 2 digits -->
     3<!ENTITY day          "21">                   <!-- Always 2 digits -->
    44<!ENTITY month        "05">                   <!-- Always 2 digits -->
    55<!ENTITY year         "2019">
    … …  
    77<!ENTITY copyholder   "The BLFS Development Team">
    88<!ENTITY version      "&year;-&month;-&day;">
    9 <!ENTITY releasedate  "May 18th, &year;">
     9<!ENTITY releasedate  "May 21st, &year;">
    1010<!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
    1111<!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->

  • general/genlib/gsl.xml

    r215c728b r5e8edab5  
    9999    installed, buid the documentation with:</para>
    100100
    101 <screen><userinput>make html</userinput></screen>
     101<screen remap="doc"><userinput>make html</userinput></screen>
    102102
    103103    <para>
    … …  
    113113    <para>If you built the documentation, install it (as root) with:</para>
    114114
    115 <screen role="root"><userinput>mkdir                   /usr/share/doc/gsl-&gsl-version; &amp;&amp;
     115<screen role="root"
     116        remap="doc"><userinput>mkdir                   /usr/share/doc/gsl-&gsl-version; &amp;&amp;
    116117cp -R doc/_build/html/* /usr/share/doc/gsl-&gsl-version;</userinput></screen>
    117118

  • general/genlib/js60.xml

    r215c728b r5e8edab5  
    8080      <xref linkend="python2"/>,
    8181      <xref linkend="xorg7-lib"/>,
    82       <xref linkend="yasm"/>, and
     82      <!--<xref linkend="yasm"/>,--> and
    8383      <xref linkend="zip"/>
    8484    </para>

  • general/genlib/libassuan.xml

    r215c728b r5e8edab5  
    115115
    116116<screen><userinput>./configure --prefix=/usr &amp;&amp;
    117 make</userinput></screen>
    118 
    119     <para>
    120       If you wish to build documentation, you must have
    121       <xref linkend="texlive"/> installed and issue the following commands:
     117make                      &amp;&amp;
     118
     119make -C doc html                                                       &amp;&amp;
     120makeinfo --html --no-split -o doc/assuan_nochunks.html doc/assuan.texi &amp;&amp;
     121makeinfo --plaintext       -o doc/assuan.txt           doc/assuan.texi
     122</userinput></screen>
     123
     124    <para>
     125      The above commands build the documentation in html and plaintext formats.
     126      If you wish to build alternate formats of the documentation, you must
     127      have <xref linkend="texlive"/> installed and issue the following commands:
    122128    </para>
    123129
    124130<!--<screen><userinput>patch -Np1 -i ../libassuan-&libassuan-version;-fix_doc_build-1.patch &amp;&amp;-->
    125 <screen><userinput>make -C doc pdf ps</userinput></screen>
     131<screen remap="doc"><userinput>make -C doc pdf ps</userinput></screen>
    126132
    127133    <para>
    … …  
    133139    </para>
    134140
    135 <screen role="root"><userinput>make install</userinput></screen>
    136 
    137     <para>
    138       If you built the documentation, install it by running the
    139       following commands as the
     141<screen role="root"><userinput>make install &amp;&amp;
     142
     143install -v -dm755   /usr/share/doc/libassuan-1.8.4/html &amp;&amp;
     144install -v -m644 doc/assuan.html/* \
     145                    /usr/share/doc/libassuan-1.8.4/html &amp;&amp;
     146install -v -m644 doc/assuan_nochunks.html \
     147                    /usr/share/doc/libassuan-1.8.4      &amp;&amp;
     148install -v -m644 doc/assuan.{txt,texi} \
     149                    /usr/share/doc/libassuan-1.8.4</userinput></screen>
     150
     151    <para>
     152      If you built alternate formats of the documentation, install them by
     153      running the following commands as the
    140154      <systemitem class="username">root</systemitem> user:
    141155    </para>
    142156
    143 <screen role="root"><userinput>install -v -dm755 /usr/share/doc/libassuan-&libassuan-version; &amp;&amp;
    144 install -v -m644  doc/assuan.{pdf,ps,dvi} \
     157<screen role="root"
     158        remap="doc"><userinput>install -v -m644  doc/assuan.{pdf,ps,dvi} \
    145159                  /usr/share/doc/libassuan-&libassuan-version;</userinput></screen>
    146160  </sect2>

  • general/genlib/libgcrypt.xml

    r215c728b r5e8edab5  
    103103
    104104<screen><userinput>./configure --prefix=/usr &amp;&amp;
    105 make</userinput></screen>
    106 
    107     <para>
    108       Only <command>info</command> documentation is shipped in the package
    109       tarball. If you wish to build alternate formats of the documentation,
    110       (you must have <xref linkend="texlive"/> installed to build the PDF
    111       and PostScript documentation), then issue the following commands:
    112     </para>
    113 
    114 <screen><userinput>make -C doc pdf ps html &amp;&amp;
     105make                      &amp;&amp;
     106
     107make -C doc html                                                       &amp;&amp;
    115108makeinfo --html --no-split -o doc/gcrypt_nochunks.html doc/gcrypt.texi &amp;&amp;
    116109makeinfo --plaintext       -o doc/gcrypt.txt           doc/gcrypt.texi</userinput></screen>
     110
     111    <para>
     112      The above commands build the documentation in html and plaintext
     113      formats. If you wish to build alternate formats of the documentation, you
     114      need <xref linkend="texlive"/> (or <xref linkend="tl-installer"/>). Issue
     115      the following command:
     116    </para>
     117
     118<screen remap="doc"><userinput>make -C doc pdf ps</userinput></screen>
    117119
    118120    <para>
    … …  
    127129install -v -dm755   /usr/share/doc/libgcrypt-&libgcrypt-version; &amp;&amp;
    128130install -v -m644    README doc/{README.apichanges,fips*,libgcrypt*} \
    129                     /usr/share/doc/libgcrypt-&libgcrypt-version;</userinput></screen>
    130 
    131     <para>
    132       If you built the additional documentation, install it by issuing the
    133       following commands as the <systemitem class="username">root</systemitem>
    134       user:
    135     </para>
    136 
    137 <screen role="root"><userinput>install -v -dm755   /usr/share/doc/libgcrypt-&libgcrypt-version;/html &amp;&amp;
     131                    /usr/share/doc/libgcrypt-&libgcrypt-version; &amp;&amp;
     132
     133install -v -dm755   /usr/share/doc/libgcrypt-&libgcrypt-version;/html &amp;&amp;
    138134install -v -m644 doc/gcrypt.html/* \
    139135                    /usr/share/doc/libgcrypt-&libgcrypt-version;/html &amp;&amp;
    140136install -v -m644 doc/gcrypt_nochunks.html \
    141                     /usr/share/doc/libgcrypt-&libgcrypt-version; &amp;&amp;
    142 install -v -m644 doc/gcrypt.{pdf,ps,dvi,txt,texi} \
     137                    /usr/share/doc/libgcrypt-&libgcrypt-version;      &amp;&amp;
     138install -v -m644 doc/gcrypt.{txt,texi} \
     139                    /usr/share/doc/libgcrypt-&libgcrypt-version;</userinput></screen>
     140
     141    <para>
     142      If you built alternate formats of the documentation, install them by
     143      issuing the following command as the
     144      <systemitem class="username">root</systemitem> user:
     145    </para>
     146
     147<screen role="root"
     148        remap="doc"><userinput>install -v -m644 doc/gcrypt.{pdf,ps,dvi} \
    143149                    /usr/share/doc/libgcrypt-&libgcrypt-version;</userinput></screen>
    144150

  • general/genlib/libical.xml

    r215c728b r5e8edab5  
    117117    </para>
    118118
    119 <screen><userinput>make docs</userinput></screen>
     119<screen remap="doc"><userinput>make docs</userinput></screen>
    120120-->
    121121    <para>
    … …  
    137137    </para>
    138138
    139 <screen role="root"><userinput>install -vdm755 /usr/share/doc/libical-&libical-version;/html &amp;&amp;
     139<screen role="root"
     140        remap="doc"><userinput>install -vdm755 /usr/share/doc/libical-&libical-version;/html &amp;&amp;
    140141cp -vr apidocs/html/* /usr/share/doc/libical-&libical-version;/html</userinput></screen>
    141142-->

  • general/genlib/libusb.xml

    r215c728b r5e8edab5  
    107107    </para>
    108108
    109 <screen><userinput>make -C doc docs</userinput></screen>
     109<screen remap="doc"><userinput>make -C doc docs</userinput></screen>
    110110
    111111    <para>
    … …  
    124124    </para>
    125125
    126 <screen role="root"><userinput>install -v -d -m755 /usr/share/doc/libusb-&libusb-version;/apidocs &amp;&amp;
     126<screen role="root"
     127        remap="doc"><userinput>install -v -d -m755 /usr/share/doc/libusb-&libusb-version;/apidocs &amp;&amp;
    127128install -v -m644    doc/html/* \
    128129                    /usr/share/doc/libusb-&libusb-version;/apidocs</userinput></screen>

  • general/genlib/popt.xml

    r215c728b r5e8edab5  
    7373
    7474    <para>If you have <xref linkend="doxygen"/> installed and wish to build
    75     the API documentation, issue <command>doxygen</command>.</para>
     75    the API documentation, issue:</para>
     76
     77<screen remap="doc"><userinput>doxygen</userinput></screen>
    7678
    7779    <para>To test the results, issue: <command>make check</command>.</para>
    … …  
    8587    user:</para>
    8688
    87 <screen role="root"><userinput>install -v -m755 -d /usr/share/doc/popt-&popt-version; &amp;&amp;
     89<screen role="root"
     90        remap="doc"><userinput>install -v -m755 -d /usr/share/doc/popt-&popt-version; &amp;&amp;
    8891install -v -m644 doxygen/html/* /usr/share/doc/popt-&popt-version;</userinput></screen>
    8992

  • general/graphlib/graphite2.xml

    r215c728b r5e8edab5  
    151151    </para>
    152152
    153 <screen><userinput>make docs</userinput></screen>
     153<screen remap="doc"><userinput>make docs</userinput></screen>
    154154
    155155    <para>
    … …  
    168168    </para>
    169169
    170 <screen role="root"><userinput>install -v -d -m755 /usr/share/doc/graphite2-&graphite2-version; &amp;&amp;
     170<screen role="root"
     171        remap="doc"><userinput>install -v -d -m755 /usr/share/doc/graphite2-&graphite2-version; &amp;&amp;
    171172<!-- doc/doxygen seems to have gone, so I removed the api dir, but now both html
    172173and pdf for the GTF and the manual

  • general/graphlib/qpdf.xml

    r215c728b r5e8edab5  
    77  <!ENTITY qpdf-download-http "https://github.com/qpdf/qpdf/releases/download/release-qpdf-&qpdf-version;/qpdf-&qpdf-version;.tar.gz">
    88  <!ENTITY qpdf-download-ftp  " ">
    9   <!ENTITY qpdf-md5sum        "aeec36aaa33d9ded8fd466ae67b9c4bd">
     9  <!ENTITY qpdf-md5sum        "41160fbd4450d4988f0705d394069ad4">
    1010  <!ENTITY qpdf-size          "16 MB">
    11   <!ENTITY qpdf-buildsize     "206 MB (add 4 MB for tests)">
     11  <!ENTITY qpdf-buildsize     "197 MB (add 4 MB for tests)">
    1212  <!ENTITY qpdf-time          "0.4 SBU (using parallelism=4; add 0.9 SBU for tests)">
    1313]>

  • general/prog/dbus-python.xml

    r215c728b r5e8edab5  
    118118<screen><userinput>mkdir python2 &amp;&amp;
    119119pushd python2 &amp;&amp;
    120 PYTHON=/usr/bin/python     \
     120PYTHON=/usr/bin/python2     \
    121121../configure --prefix=/usr --docdir=/usr/share/doc/dbus-python-&dbus-python-version; &amp;&amp;
    122122make &amp;&amp;

  • general/prog/doxygen.xml

    r215c728b r5e8edab5  
    150150    </para>
    151151
    152 <screen><userinput>cmake -DDOC_INSTALL_DIR=share/doc/doxygen-&doxygen-version; -Dbuild_doc=ON .. &amp;&amp;
     152<screen remap="doc"><userinput>cmake -DDOC_INSTALL_DIR=share/doc/doxygen-&doxygen-version; -Dbuild_doc=ON .. &amp;&amp;
    153153
    154154make docs</userinput></screen>

  • general/prog/gdb.xml

    r215c728b r5e8edab5  
    120120    </para>
    121121
    122 <screen><userinput>make -C gdb/doc doxy</userinput></screen>
     122<screen remap="doc"><userinput>make -C gdb/doc doxy</userinput></screen>
    123123
    124124    <para>
    … …  
    126126    </para>
    127127
    128 <screen><userinput>pushd gdb/testsuite &amp;&amp;
     128<screen remap="test"><userinput>pushd gdb/testsuite &amp;&amp;
    129129make  site.exp      &amp;&amp;
    130130echo  "set gdb_test_timeout 120" &gt;&gt; site.exp &amp;&amp;
    … …  
    205205    </para>
    206206
    207 <screen role="root"><userinput>install -d /usr/share/doc/gdb-&gdb-version; &amp;&amp;
     207<screen role="root"
     208        remap="doc"><userinput>install -d /usr/share/doc/gdb-&gdb-version; &amp;&amp;
    208209rm -rf gdb/doc/doxy/xml &amp;&amp;
    209210cp -Rv gdb/doc/doxy /usr/share/doc/gdb-&gdb-version;</userinput></screen>

  • general/prog/git.xml

    r215c728b r5e8edab5  
    165165    </para>
    166166
    167 <screen><userinput>make html</userinput></screen>
     167<screen remap="doc"><userinput>make html</userinput></screen>
    168168
    169169    <para>
    … …  
    172172    </para>
    173173
    174 <screen><userinput>make man</userinput></screen>
     174<screen remap="doc"><userinput>make man</userinput></screen>
    175175
    176176    <para>
    … …  
    195195    </para>
    196196
    197 <screen role="root"><userinput>make install-man</userinput></screen>
     197<screen role="root" remap="doc"><userinput>make install-man</userinput></screen>
    198198
    199199    <para>
    … …  
    202202    </para>
    203203
    204 <screen role="root"><userinput>make htmldir=/usr/share/doc/git-&git-version; install-html</userinput></screen>
     204<screen role="root" remap="doc"><userinput>make htmldir=/usr/share/doc/git-&git-version; install-html</userinput></screen>
    205205
    206206<!-- ==== Method 2 for docs ====== -->

  • general/prog/jinja2.xml

    r215c728b r5e8edab5  
    9797      </para>
    9898
    99 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
     99<screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen>
    100100
    101101      <para>

  • general/prog/libxml2py2.xml

    r215c728b r5e8edab5  
    9999
    100100<screen><userinput>cd python             &amp;&amp;
    101 python setup.py build</userinput></screen>
     101python2 setup.py build</userinput></screen>
    102102
    103103      <para>
    … …  
    107107      </para>
    108108
    109 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
     109<screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen>
    110110
    111111    </sect3>

  • general/prog/llvm.xml

    r215c728b r5e8edab5  
    211211
    212212    <para>
     213      If you have installed <application>Sphinx</application> and
     214      <application>recommonmark</application> and wish
     215      to generate the html documentation and manual pages, issue the following
     216      commands:
     217    </para>
     218
     219<screen remap="doc"><userinput>cmake -DLLVM_ENABLE_SPHINX=ON         \
     220      -DSPHINX_WARNINGS_AS_ERRORS=OFF \
     221      -Wno-dev -G Ninja ..            &amp;&amp;
     222ninja docs-llvm-html  docs-llvm-man</userinput></screen>
     223
     224    <para>
     225      If you have downloaded the optional packages, the clang documentation
     226      can be built too:
     227    </para>
     228
     229<screen remap="doc"><userinput>ninja docs-clang-html docs-clang-man</userinput></screen>
     230
     231    <para>
    213232      <!-- EDITORS - if you have more than 4 cores, take some offline to measure
    214233      the elapsed time for the tests.  Also, libstdc++.a and perhaps libstdc++fs.a
    … …  
    234253
    235254    <para>
    236       If you have installed <application>Sphinx</application> and
    237       <application>recommonmark</application> and wish
    238       to generate the html documentation and manual pages, issue the following
    239       commands:
    240     </para>
    241 <screen><userinput>cmake -DLLVM_ENABLE_SPHINX=ON         \
    242       -DSPHINX_WARNINGS_AS_ERRORS=OFF \
    243       -Wno-dev -G Ninja ..            &amp;&amp;
    244 ninja docs-llvm-html  docs-llvm-man</userinput></screen>
    245     <para>
    246       If you have downloaded the optional packages, the clang documentation
    247       can be built too:
    248     </para>
    249 <screen><userinput>ninja docs-clang-html docs-clang-man</userinput></screen>
    250 
    251     <para>
    252       Install the llvm documentation by running the following command as the
    253       <systemitem class="username">root</systemitem> user:
    254     </para>
    255 
    256 <screen role="root"><userinput>install -v -m644 docs/man/* /usr/share/man/man1             &amp;&amp;
     255      If you have built the the llvm documentation, install it by running the
     256      following commands as the <systemitem class="username">root</systemitem>
     257      user:
     258    </para>
     259
     260<screen role="root"
     261        remap="doc"><userinput>install -v -m644 docs/man/* /usr/share/man/man1             &amp;&amp;
    257262install -v -d -m755 /usr/share/doc/llvm-&llvm-version;/llvm-html     &amp;&amp;
    258263cp -Rv docs/html/* /usr/share/doc/llvm-&llvm-version;/llvm-html</userinput></screen>
    259264
    260265    <para>
    261       The clang documentation can be installed in the same way (again as the
     266      If you have built the clang documentation, it can be installed in the
     267      same way (again as the
    262268      <systemitem class="username">root</systemitem> user):
    263269    </para>
    264270
    265 <screen role="root"><userinput>install -v -m644 tools/clang/docs/man/* /usr/share/man/man1 &amp;&amp;
     271<screen role="root"
     272        remap="doc"><userinput>install -v -m644 tools/clang/docs/man/* /usr/share/man/man1 &amp;&amp;
    266273install -v -d -m755 /usr/share/doc/llvm-&llvm-version;/clang-html    &amp;&amp;
    267274cp -Rv tools/clang/docs/html/* /usr/share/doc/llvm-&llvm-version;/clang-html</userinput></screen>

  • general/prog/lxml.xml

    r215c728b r5e8edab5  
    105105
    106106      <para>
    107         To build the <application>Python 2</application> module, run:
     107        To build both <application>Python 2</application> and
     108        <application>Python 3</application> modules, run:
    108109      </para>
    109110
    110 <screen><userinput>python setup.py build</userinput></screen>
     111<screen><userinput>python2 setup.py build &amp;&amp;
     112python3 setup.py build</userinput></screen>
    111113
    112114     <para>
    113        If you wish to run the tests, enter: <command>make test</command>.
     115       If you wish to run the tests, enter:
     116       <command>make PYTHON=python2 test</command> and
     117       <command>make PYTHON=python3 test</command>.
    114118       This will rebuild the package for inplace use before running the tests.
    115119       One or more tests sometimes fail.
    … …  
    117121
    118122      <para>
    119         To install the <application>Python 2</application> module,
    120         as the
    121         <systemitem class="username">root</systemitem> user run:
     123        To install both modules, issue the following commands as the
     124        <systemitem class="username">root</systemitem> user:
    122125      </para>
    123126
    124 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
    125 
    126       <para>
    127         To build the <application>Python 3</application> module, run:
    128       </para>
    129 
    130 <screen><userinput>python3 setup.py clean &amp;&amp;
    131 python3 setup.py build</userinput></screen>
    132 
    133      <para>
    134        If you wish to run the tests, enter: <command>make PYTHON=python3
    135        test</command>. This will rebuild the package for inplace use before
    136        running the tests. One or more tests sometimes fail.
    137      </para>
    138 
    139       <para>
    140         To install the <application>Python 3</application> module,
    141         as the
    142         <systemitem class="username">root</systemitem> user run:
    143       </para>
    144 
    145 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
     127<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     128python3 setup.py install --optimize=1</userinput></screen>
    146129
    147130    </sect3>

  • general/prog/mako.xml

    r215c728b r5e8edab5  
    9999      </para>
    100100
    101 <screen role="root"><userinput>python setup.py install - -optimize=1</userinput></screen>
     101<screen role="root"><userinput>python2 setup.py install - -optimize=1</userinput></screen>
    102102-->
    103103      <para>

  • general/prog/mercurial.xml

    r215c728b r5e8edab5  
    100100    issue:</para>
    101101
    102 <screen><userinput>sed -i '/runrst/s/N)/N)3/' doc/Makefile &amp;&amp;
     102<screen remap="doc"><userinput>sed -i '/runrst/s/N)/N)3/' doc/Makefile &amp;&amp;
    1031032to3-3.7 -w doc/hgmanpage.py            &amp;&amp;
    104104make doc</userinput></screen>
    … …  
    111111    issue:</para>
    112112
    113 <screen><userinput>cat &gt; tests/blacklists/failed-tests &lt;&lt; "EOF"
     113<screen remap="test"><userinput>cat &gt; tests/blacklists/failed-tests &lt;&lt; "EOF"
    114114<literal># Test Failures
    115115  test-gpg.t</literal>
    … …  
    119119      To run the test suite, issue:
    120120    </para>
    121 <screen><userinput>rm -rf tests/tmp &amp;&amp;
     121<screen remap="test"><userinput>rm -rf tests/tmp &amp;&amp;
    122122TESTFLAGS="-j<replaceable>&lt;N&gt;</replaceable> --tmpdir tmp --blacklist blacklists/failed-tests" make check</userinput></screen>
    123123
    … …  
    130130    the tests that failed before:</para>
    131131
    132 <screen><userinput>pushd tests  &amp;&amp;
     132<screen remap="test"><userinput>pushd tests  &amp;&amp;
    133133  rm -rf tmp &amp;&amp;
    134134  ./run-tests.py --tmpdir tmp test-gpg.t
    … …  
    142142    or not. One test, test-https.t, is known to fail.</para>
    143143
    144     <para>An interesting switch is "- -time", which will generate at the end of
     144    <para>An interesting switch is "--time", which will generate at the end of
    145145    the test suite execution, a table with all executed tests and respective
    146146    start, end, user, system and real times. Notice that the switches may be
    … …  
    156156    command (as <systemitem class="username">root</systemitem>):</para>
    157157
    158 <screen role="root"><userinput>make PREFIX=/usr install-doc</userinput></screen>
     158<screen role="root"
     159        remap="doc"><userinput>make PREFIX=/usr install-doc</userinput></screen>
    159160
    160161    <para>After installed, two very quick and simple tests should run correctly.

  • general/prog/pycairo.xml

    r215c728b r5e8edab5  
    9595
    9696      <para>
    97         Install <application>PyCairo</application> for Python2 by running
    98         the following commands:
     97        Install <application>PyCairo</application> for Python2  and Python3 by
     98        running the following commands:
    9999      </para>
    100100
    101 <screen><userinput>python2 setup.py build</userinput></screen>
     101<screen><userinput>python2 setup.py build &amp;&amp;
     102python3 setup.py build</userinput></screen>
    102103
    103104      <para>
    … …  
    109110      </para>
    110111
    111 <screen role="root"><userinput>python2 setup.py install --optimize=1   &amp;&amp;
     112<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     113python3 setup.py install --optimize=1</userinput></screen>
     114<!-- Seems that install does the following too
    112115python2 setup.py install_pycairo_header &amp;&amp;
    113 python2 setup.py install_pkgconfig</userinput></screen>
    114 
    115       <para>
    116         Install <application>PyCairo</application> for Python3 by running
    117         the following commands:
    118       </para>
    119 
    120 <screen><userinput>python3 setup.py build</userinput></screen>
    121 
    122       <para>
    123         This package does not come with a test suite.
    124       </para>
    125 
    126       <para>
    127         Now, as the <systemitem class="username">root</systemitem> user:
    128       </para>
    129 
    130 <screen role="root"><userinput>python3 setup.py install --optimize=1   &amp;&amp;
    131 python3 setup.py install_pycairo_header &amp;&amp;
    132 python3 setup.py install_pkgconfig</userinput></screen>
     116python2 setup.py install_pkgconfig</userinput></screen>-->
    133117
    134118    </sect3>

  • general/prog/pycrypto.xml

    r215c728b r5e8edab5  
    9393
    9494      <para>
    95         To build the <application>Python 2</application> module,
    96         run the following command:
     95        To build the <application>Python 2</application> and
     96        <application>Python 3</application> modules, run the following commands:
    9797      </para>
    9898
    99 <screen><userinput>python setup.py build</userinput></screen>
     99<screen><userinput>python2 setup.py build &amp;&amp;
     100python3 setup.py build</userinput></screen>
    100101
    101102      <para>
    102         To install the <application>Python 2</application> module,
    103         run the following command as the
     103        To install both modules, run the following commands as the
    104104        <systemitem class="username">root</systemitem> user:
    105105      </para>
    106106
    107 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
    108 
    109       <para>
    110         To build the <application>Python 3</application> module,
    111         run the following command:
    112       </para>
    113 
    114 <screen><userinput>python3 setup.py build</userinput></screen>
    115 
    116       <para>
    117         To install the <application>Python 3</application> module,
    118         run the following command as the
    119         <systemitem class="username">root</systemitem> user:
    120       </para>
    121 
    122 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
     107<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     108python3 setup.py install --optimize=1</userinput></screen>
    123109
    124110    </sect3>
    … …  
    137123          </seg>
    138124          <seg>
    139             pycrypto-&pycrypto-version;-py2.7.egg-info and/or
    140             pycrypto-&pycrypto-version;-py3.6.egg-info
     125            pycrypto-&pycrypto-version;-py&python2-majorver;.egg-info and/or
     126            pycrypto-&pycrypto-version;-py&python3-majorver;.egg-info
    141127          </seg>
    142128          <seg>

  • general/prog/pyyaml.xml

    r215c728b r5e8edab5  
    9797
    9898      <para>
    99         To build the <application>Python 2</application> module,
    100         run the following command:
     99        To build both <application>Python 2</application> and
     100        <application>Python 3</application> modules,
     101        run the following commands:
    101102      </para>
    102103
    103 <screen><userinput>python setup.py build</userinput></screen>
     104<screen><userinput>python2 setup.py build &amp;&amp;
     105python3 setup.py build</userinput></screen>
    104106
    105107      <para>
    106         To install the <application>Python 2</application> module,
    107         run the following command as the
     108        To install both modules, run the following commands as the
    108109        <systemitem class="username">root</systemitem> user:
    109110      </para>
    110111
    111 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
    112 
    113       <para>
    114         To build the <application>Python 3</application> module,
    115         run the following command:
    116       </para>
    117 
    118 <screen><userinput>python3 setup.py build</userinput></screen>
    119 
    120       <para>
    121         To install the <application>Python 3</application> module,
    122         run the following command as the
    123         <systemitem class="username">root</systemitem> user:
    124       </para>
    125 
    126 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
     112<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     113python3 setup.py install --optimize=1</userinput></screen>
    127114
    128115    </sect3>

  • general/prog/rust.xml

    r215c728b r5e8edab5  
    185185    <para role="optional">
    186186      <xref linkend="gdb"/> (used by the testsuite if it is present) and
    187       <xref linkend="python2"/> (if gdb is present, it must have been built
    188       with Python 2 support to prevent some tests failing. Furthermore, another
    189       test fails if Python 2 is not present)
     187      <xref linkend="python2"/> (one test fails if Python 2 is not present)
    190188    </para>
    191189
    … …  
    301299      which need Thumb (ARM) compilers will fail, all in <filename
    302300      class="directory">ui/issues</filename> for issues 37131, 49851 and 50993.
    303       Occasionally a fourth test,
     301      If <xref linkend="python2"/> is not installed, a fourth test,
    304302      <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename>
    305303      fails. If gdb has been installed, in some circumstances three tests in

  • general/prog/scour.xml

    r215c728b r5e8edab5  
    107107
    108108      <para>
    109         To build the <application>Python 2</application> module,
    110         run the following command:
     109        To build both <application>Python 2</application> and
     110        <application>Python 3</application> modules,
     111        run the following commands:
    111112      </para>
    112113
    113 <screen><userinput>python setup.py build</userinput></screen>
     114<screen><userinput>python2 setup.py build &amp;&amp;
     115python3 setup.py build</userinput></screen>
    114116
    115117      <para>
    116         To partially test the results, issue: <command>python testcss.py</command>.
     118        To partially test the results, issue: <command>python2 testcss.py</command>.
    117119        If you have installed <application>Six</application> you can run the main
    118         tests by issuing: <command>python testscour.py</command>.
     120        tests by issuing: <command>python2 testscour.py</command>.
    119121      </para>
    120122
    121123      <para>
    122         To install the <application>Python 2</application> module
    123         run the following command as the
     124        To install both modules, run the following command as the
    124125        <systemitem class="username">root</systemitem> user:
    125126      </para>
    126127
    127 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
    128 
    129       <para>
    130         To build the <application>Python 3</application> module,
    131         run the following command:
    132       </para>
    133 
    134 <screen><userinput>python3 setup.py build</userinput></screen>
    135 
    136       <para>
    137         To install the <application>Python 3</application> module,
    138         run the following command as the
    139         <systemitem class="username">root</systemitem> user:
    140       </para>
    141 
    142 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
     128<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     129python3 setup.py install --optimize=1</userinput></screen>
    143130
    144131    </sect3>

  • general/prog/six.xml

    r215c728b r5e8edab5  
    9090
    9191      <para>
    92         Install <application>six</application> for Python2 by running
    93         the following commands:
     92        Install <application>six</application> for Python 2 and Python 3
     93        by running the following commands:
    9494      </para>
    9595
    96 <screen><userinput>python2 setup.py build</userinput></screen>
     96<screen><userinput>python2 setup.py build &amp;&amp;
     97python3 setup.py build</userinput></screen>
    9798
    9899      <para>
    … …  
    104105      </para>
    105106
    106 <screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen>
    107 
    108       <para>
    109         Install <application>six</application> for Python3 by running
    110         the following commands:
    111       </para>
    112 
    113 <screen><userinput>python3 setup.py build</userinput></screen>
    114 
    115       <para>
    116         This package does not come with a test suite.
    117       </para>
    118 
    119       <para>
    120         Now, as the <systemitem class="username">root</systemitem> user:
    121       </para>
    122 
    123 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
     107<screen role="root"><userinput>python2 setup.py install --optimize=1 &amp;&amp;
     108python3 setup.py install --optimize=1</userinput></screen>
    124109
    125110    </sect3>

  • general/sysutils/cpio.xml

    r215c728b r5e8edab5  
    8888    both of the following commands:</para>
    8989
    90 <screen><userinput>make -C doc pdf &amp;&amp;
     90<screen remap="doc"><userinput>make -C doc pdf &amp;&amp;
    9191make -C doc ps</userinput></screen>
    9292
    … …  
    106106    <systemitem class="username">root</systemitem> user:</para>
    107107
    108 <screen role="root"><userinput>install -v -m644 doc/cpio.{pdf,ps,dvi} \
     108<screen role="root"
     109        remap="doc"><userinput>install -v -m644 doc/cpio.{pdf,ps,dvi} \
    109110                 /usr/share/doc/cpio-&cpio-version;</userinput></screen>
    110111

  • general/sysutils/systemd.xml

    r215c728b r5e8edab5  
    147147cd    build &amp;&amp;
    148148
     149CFLAGS+="-Wno-format-overflow" \
    149150meson --prefix=/usr         \
    150151      --sysconfdir=/etc     \
    … …  
    160161      -Dsplit-usr=true      \
    161162      -Dsysusers=false      \
     163      -Drpmmacrosdir=no     \
    162164      -Db_lto=false         \
    163165      ..                    &amp;&amp;
    … …  
    199201
    200202<screen role="root"><userinput>ninja install</userinput></screen>
    201 
     203<!--
    202204    <para>
    203205      If <application>RPM</application> is not installed, remove an
    … …  
    207209
    208210<screen role="root"><userinput>rm -rfv /usr/lib/rpm</userinput></screen>
    209 
     211-->
    210212  </sect2>
    211213

  • introduction/welcome/changelog.xml

    r215c728b r5e8edab5  
    7676    </listitem>
    7777    -->
    78 
     78    <listitem>
     79      <para>May 21st, 2019</para>
     80      <itemizedlist>
     81        <listitem>
     82          <para>[ken] - Firefox-67.0 (includes security fixes). Use gcc in
     83          preference to LLVM, disable debug symbols, and stop using the gold
     84          linker. The result is a much smaller build. Please note that both nasm
     85          and yasm are now used. Fixes <ulink
     86          url="&blfs-ticket-root;12082">#12082</ulink>. Please be aware that you
     87          may need to create a new profile when running this version, and
     88          reapply your customizations, extensions, and perhaps bookmarks.</para>
     89        </listitem>
     90      </itemizedlist>
     91    </listitem>
     92
     93    <listitem revision="systemd">
     94      <para>May 20th, 2019</para>
     95      <itemizedlist>
     96        <listitem>
     97          <para>[renodr] - Do minor tweaks to the systemd page in BLFS
     98          to permit building with GCC-9, and remove instructions for
     99          removing the RPM directory by passing a meson flag instead.
     100          This is a temporary stopgap measure until 242 is implemented.</para>
     101        </listitem>
     102      </itemizedlist>
     103    </listitem>
     104
     105    <listitem>
     106      <para>May 19th, 2019</para>
     107      <itemizedlist>
     108        <listitem>
     109          <para>[renodr] - Archive xf86-input-vmmouse. With kernel 5.1 and
     110          later, VMWare made this driver obsolete by mapping VMMouse's
     111          events into the evdev subsystem. Therefore,
     112          xf86-input-evdev now works with it and this package can be archived.
     113          Installing it on a VMWare or Qemu system with 5.1+ will cause
     114          instability and other problems.</para>
     115        </listitem>
     116        <listitem>
     117          <para>[ken] - Update details of Intel microcode. Fixes
     118          <ulink url="&blfs-ticket-root;12061">#12061</ulink>.</para>
     119        </listitem>
     120        <listitem>
     121          <para>[bdubbs] - Update to thunderbird-60.7.0. Fixes
     122          <ulink url="&blfs-ticket-root;12080">#12080</ulink>.</para>
     123        </listitem>
     124        <listitem>
     125          <para>[bdubbs] - Update to Thunar-1.8.6. Fixes
     126          <ulink url="&blfs-ticket-root;12081">#12081</ulink>.</para>
     127        </listitem>
     128        <listitem>
     129          <para>[bdubbs] - Update to qpdf-8.4.2. Fixes
     130          <ulink url="&blfs-ticket-root;12077">#12077</ulink>.</para>
     131        </listitem>
     132      </itemizedlist>
     133    </listitem>
     134   
    79135    <listitem>
    80136      <para>May 18th, 2019</para>

  • multimedia/videoutils/ffmpeg.xml

    r215c728b r5e8edab5  
    194194<!-- sed -i '$s/$/\n\n@bye/' doc/{git-howto,nut,fate}.texi             &amp;&amp;
    195195sed -i '/machine:i386/ s/\\/@backslashchar{}/g' doc/platform.texi &amp;&amp; -->
    196 <screen><userinput>pushd doc &amp;&amp;
     196<screen remap="doc"><userinput>pushd doc &amp;&amp;
    197197for DOCNAME in `basename -s .html *.html`
    198198do
    … …  
    209209      If you have <xref linkend="doxygen"/> installed
    210210      and you wish to build (if --disable-doc was
    211       used) or rebuild the html documentation, issue the command
    212       <command>doxygen doc/Doxyfile</command>.
    213     </para>
     211      used) or rebuild the html documentation, issue:
     212    </para>
     213
     214<screen remap="doc"><userinput>doxygen doc/Doxyfile</userinput></screen>
    214215
    215216    <para>
    … …  
    235236    </para>
    236237
    237 <screen role="root"><userinput>install -v -m644 doc/*.pdf /usr/share/doc/ffmpeg-&ffmpeg-version; &amp;&amp;
     238<screen role="root"
     239        remap="doc"><userinput>install -v -m644 doc/*.pdf /usr/share/doc/ffmpeg-&ffmpeg-version; &amp;&amp;
    238240install -v -m644 doc/*.ps  /usr/share/doc/ffmpeg-&ffmpeg-version;</userinput></screen>
    239241
    … …  
    244246    </para>
    245247
    246 <screen role="root"><userinput>install -v -m755 -d /usr/share/doc/ffmpeg-&ffmpeg-version;/api                     &amp;&amp;
     248<screen role="root"
     249        remap="doc"><userinput>install -v -m755 -d /usr/share/doc/ffmpeg-&ffmpeg-version;/api                     &amp;&amp;
    247250cp -vr doc/doxy/html/* /usr/share/doc/ffmpeg-&ffmpeg-version;/api                  &amp;&amp;
    248251find /usr/share/doc/ffmpeg-&ffmpeg-version;/api -type f -exec chmod -c 0644 \{} \; &amp;&amp;
    … …  
    257260    </para>
    258261
    259 <screen><userinput>make fate-rsync SAMPLES=fate-suite/</userinput></screen>
     262<screen remap="test"><userinput>make fate-rsync SAMPLES=fate-suite/</userinput></screen>
    260263
    261264    <para>
    … …  
    274277    </para>
    275278
    276 <screen><userinput><command>rsync -vrltLW  --delete --timeout=60 --contimeout=60 \
     279<screen role="nodump"><userinput><command>rsync -vrltLW  --delete --timeout=60 --contimeout=60 \
    277280      rsync://fate-suite.ffmpeg.org/fate-suite/ fate-suite/</command></userinput></screen>
    278281
    … …  
    282285    </para>
    283286
    284 <screen><userinput>make fate THREADS=<replaceable>N</replaceable> SAMPLES=fate-suite/ | tee ../fate.log &amp;&amp;
     287<screen remap="test"><userinput>make fate THREADS=<replaceable>N</replaceable> SAMPLES=fate-suite/ | tee ../fate.log &amp;&amp;
    285288grep ^TEST ../fate.log | wc -l</userinput></screen>
    286289

  • networking/netlibs/libevent.xml

    r215c728b r5e8edab5  
    107107    <para>
    108108      If you have <xref linkend="doxygen"/> installed and wish to build API
    109       documentation, issue <command>doxygen Doxyfile</command>.
    110     </para>
     109      documentation, issue :
     110    </para>
     111
     112<screen remap="doc"><userinput>doxygen Doxyfile</userinput></screen>
    111113
    112114    <para>
    … …  
    125127    </para>
    126128
    127 <screen role="root"><userinput>install -v -m755 -d /usr/share/doc/libevent-&libevent-version;/api &amp;&amp;
     129<screen role="root"
     130        remap="doc"><userinput>install -v -m755 -d /usr/share/doc/libevent-&libevent-version;/api &amp;&amp;
    128131cp      -v -R       doxygen/html/* \
    129132                    /usr/share/doc/libevent-&libevent-version;/api</userinput></screen>

  • networking/netprogs/rsync.xml

    r215c728b r5e8edab5  
    9191
    9292    <para>If you have <xref linkend="doxygen"/> installed and wish to
    93     build HTML API documentation, issue <command>doxygen</command>.</para>
     93    build HTML API documentation, issue:</para>
     94
     95<screen remap="doc"><userinput>doxygen</userinput></screen>
    9496
    9597    <para>To test the results, issue: <command>make check</command>.</para>
    … …  
    102104    commands as the <systemitem class="username">root</systemitem> user:</para>
    103105
    104 <screen role='root'><userinput>install -v -m755 -d          /usr/share/doc/rsync-&rsync-version;/api &amp;&amp;
     106<screen role='root'
     107        remap="doc"><userinput>install -v -m755 -d          /usr/share/doc/rsync-&rsync-version;/api &amp;&amp;
    105108install -v -m644 dox/html/*  /usr/share/doc/rsync-&rsync-version;/api</userinput></screen>
    106109
    … …  
    202205        <systemitem class="username">root</systemitem> user:</para>
    203206
    204 <screen role="root"><userinput>systemctl stop rsyncd &amp;&amp;
     207<screen role="nodump"><userinput>systemctl stop rsyncd &amp;&amp;
    205208systemctl disable rsyncd &amp;&amp;
    206209systemctl enable rsyncd.socket &amp;&amp;

  • packages.ent

    r215c728b r5e8edab5  
    227227<!ENTITY poppler-version              "0.76.1">
    228228<!ENTITY potrace-version              "1.15">
    229 <!ENTITY qpdf-version                 "8.4.1">
     229<!ENTITY qpdf-version                 "8.4.2">
    230230<!ENTITY libsass-version              "3.5.5">
    231231<!ENTITY sassc-version                "3.5.0">
    … …  
    784784<!ENTITY xfce4-panel-version          "4.12.2">
    785785<!ENTITY xfce4-xkb-plugin-version     "0.7.1">
    786 <!ENTITY thunar-version               "1.8.4">
     786<!ENTITY thunar-version               "1.8.6">
    787787<!ENTITY thunar-volman-version        "0.8.1">
    788788<!ENTITY tumbler-version              "0.2.4">
    … …  
    868868<!ENTITY epiphany-version             "3.30.3">
    869869<!ENTITY falkon-version               "3.0.1">
    870 <!ENTITY firefox-version              "66.0.5">
     870<!ENTITY firefox-version              "67.0">
    871871<!ENTITY flashplayer-version          "27.0.0.187">
    872872<!ENTITY qupzilla-version             "2.2.6">
    … …  
    889889<!ENTITY rox-filer-version            "2.11">
    890890<!ENTITY rxvt-unicode-version         "9.22">
    891 <!ENTITY thunderbird-version          "60.6.1">
     891<!ENTITY thunderbird-version          "60.7.0">
    892892<!ENTITY tigervnc-version             "1.9.0">
    893893<!ENTITY transmission-version         "2.94">

  • postlfs/config/firmware.xml

    r215c728b r5e8edab5  
    101101    need to be applied on every boot.</para>
    102102
    103     <para>Intel provide frequent updates of their microcode. It is not uncommon
    104     to find a newer version of microcode for an Intel processor even two years
    105     after its release. New versions of AMD firmware are rare and usually only
    106     apply to a few models, although motherboard manufacturers get extra updates
    107     which maybe update microcode along with the changes to support newer CPUs
    108     and faster memory.</para>
    109 
    110     <para>There used to be two ways of loading the microcode, described as 'early'
     103    <para>Intel provide updates of their microcode for SandyBridge and later
     104    processors as new vulnerabilities come to light. New versions of AMD
     105    firmware are rare and usually only apply to a few models, although
     106    motherboard manufacturers get extra updates which maybe update microcode
     107    along with the changes to support newer CPUs and faster memory.</para>
     108
     109    <para>There are two ways of loading the microcode, described as 'early'
    111110    and 'late'. Early loading happens before userspace has been started, late
    112111    loading happens after userspace has started. Not surprisingly, early loading
    113     was preferred, (see e.g. an explanatory comment in a kernel commit noted at
     112    is preferred, (see e.g. an explanatory comment in a kernel commit noted at
    114113    <ulink url="https://lwn.net/Articles/530346/">x86/microcode: Early load
    115114    microcode </ulink> on LWN.)  Indeed, it is needed to work around one
    … …  
    121120    uncommon situations. </para>
    122121
    123     <para>As a result, early loading is now expected, although for the moment
    124     (4.18 kernels) it is still possible to manually force late loading of
    125     microcode for testing. You will need to reconfigure your kernel for either
    126     method. The instructions here will create a kernel
    127     <filename>.config</filename> to suite early loading, before forcing late
    128     loading to see if there is any microcode. If there is, the instructions
    129     then show you how to create an initrd for early loading.</para>
     122    <para>It is still possible to manually force late loading of microcode,
     123    either for testing or to prevent having to reboot. You will need to
     124    reconfigure your kernel for either method. The instructions here will
     125    create a kernel <filename>.config</filename> to suite early loading, before
     126    forcing late loading to see if there is any microcode. If there is, the
     127    instructions then show you how to create an initrd for early loading.</para>
    130128
    131129    <para>To confirm what processor(s) you have (if more than one, they will be
    … …  
    136134
    137135     <para>The first step is to get the most recent version of the Intel
    138      microcode.  This must be done by navigating to
    139      <ulink url='https://downloadcenter.intel.com/download/28087/Linux-Processor-Microcode-Data-File'/>
    140      and following the instructions there.  As of this writing the most recent
    141      version of the microcode is <filename>microcode-20180807.tgz</filename>.
    142      Extract this file in the normal way to create an <filename>intel-ucode</filename>
     136     microcode.  This must be done by navigating to <ulink
     137     url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/'/>
     138     and downloading the latest file there.  As of this writing the most recent
     139     version of the microcode is microcode-20190514a.
     140     Extract this file in the normal way, the microcode is in the <filename>intel-ucode</filename>
    143141     directory, containing various blobs with names in the form XX-YY-ZZ.
    144      This tarball does not contain a top-level directory, two files
    145      (microcode.dat which is the old-style of updates, still used by some
    146      linux distros, and releasenote) will be extracted into the current
    147      directory.</para>
    148 
    149      <note><para>The above URL may not be the latest page.  If it is not,
    150      a line at the top of the page will direct you to the latest page.
    151      </para></note>
     142     There are also various other files, and a releasenote.</para>
     143
     144     <para>In the past, intel did not provide any details of which blobs had
     145     changed versions, but now the releasenote details this.</para>
     146
     147     <para>The recent firmware for older processors is provided to deal with
     148     vulnerabilities which have now been made public, and for some of these such
     149     as Microarchitectural Data Sampling (MDS) you might wish to increase the
     150     protection by disabling hyperthreading, or alternatively to disable the
     151     kernel's default mitigation because of its impact on compile times. Please
     152     read the online documentation at <ulink
     153     url='https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/index.html'/>.
     154     </para>
     155
     156     <para>To be able to use the microcode which addresses MDS, the kernel must
     157     be one of the following stable versions: 5.1.2, 5.0.16, 4.19.43, 4.14.119,
     158     4.9.176 or a later version of those series, or a later kernel series such
     159     as 5.2.</para>
    152160
    153161     <para>Now you need to determine your processor's identity to see if there
    … …  
    189197<screen><userinput>dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'</userinput></screen>
    190198
    191       <para>This example from the Haswell i7 which was released in Q2 2014 and is
     199      <para>This old example (from before Intel provided details of the latest
     200      versions) from the Haswell i7 which was released in Q2 2014 and is
    192201      not affected by the TSX errata shows it has been updated from revision 0x19
    193202      in the BIOS/UEFI (which this version of the kernel now complains about) to
    … …  
    313322<screen><userinput>dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'</userinput></screen>
    314323
     324      <para>If you updated to address vulnerabilities, you can look at <filename
     325      class="directory">/sys/devices/system/cpu/vulnerabilities/</filename> to
     326      see what is now reported.</para>
     327
    315328      <para>The places and times where early loading happens are very different
    316329      in AMD and Intel machines. First, an Intel example from an updated
    … …  
    318331      is mentioned:</para>
    319332
    320 <screen><literal>[    0.000000] microcode: microcode updated early to revision 0x25, date = 2018-04-02
    321 [    0.000000] Linux version 4.18.1-rc1 (ken@plexi) (gcc version 8.2.0 (GCC))
    322                #2 SMP PREEMPT Tue Aug 14 20:22:35 BST 2018
    323 [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.1-rc1-sda5 root=/dev/sda5 ro resume=/dev/sdb1
    324 [    0.275864] microcode: sig=0x306c3, pf=0x2, revision=0x25
     333<screen><literal>[    0.000000] microcode: microcode updated early to revision 0x27, date = 2019-02-26
     334[    0.000000] Linux version 5.0.16 (lfs@plexi) (gcc version 9.1.0 (GCC))
     335               #2 SMP PREEMPT Sat May 18 23:10:29 BST 2019
     336[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.0.16-sda5 root=/dev/sda5 ro resume=/dev/sdb1
     337[    0.275864] microcode: sig=0x306c3, pf=0x2, revision=0x27
    325338[    0.275911] microcode: Microcode Update Driver: v2.2.</literal></screen>
    326339

  • postlfs/security/gnupg2.xml

    r215c728b r5e8edab5  
    132132
    133133makeinfo --html --no-split -o doc/gnupg_nochunks.html doc/gnupg.texi &amp;&amp;
    134 makeinfo --plaintext       -o doc/gnupg.txt           doc/gnupg.texi</userinput></screen>
     134makeinfo --plaintext       -o doc/gnupg.txt           doc/gnupg.texi &amp;&amp;
     135make -C doc html</userinput></screen>
    135136
    136137    <para>If you have <xref linkend="texlive"/>
    … …  
    140141    the ps format):</para>
    141142
    142 <screen><userinput>make -C doc pdf ps html</userinput></screen>
     143<screen remap="doc"><userinput>make -C doc pdf ps</userinput></screen>
    143144
    144145    <para>To test the results, issue: <command>make check</command>.</para>
    … …  
    155156                    /usr/share/doc/gnupg-&gnupg2-version;/html/gnupg.html &amp;&amp;
    156157install -v -m644    doc/*.texi doc/gnupg.txt \
    157                     /usr/share/doc/gnupg-&gnupg2-version;</userinput></screen>
     158                    /usr/share/doc/gnupg-&gnupg2-version; &amp;&amp;
     159install -v -m644    doc/gnupg.html/* \
     160                    /usr/share/doc/gnupg-&gnupg2-version;/html</userinput></screen>
    158161<!-- Now intalls as gpg, not gpg2.  This should be no longer needed.
    159162    <para>The BLFS editors recommend the creation of symlinks for compatibility
    … …  
    168171unset f</userinput></screen>
    169172-->
    170     <para>If you created alternate formats of the documentation, install it
     173    <para>If you created alternate formats of the documentation, install them
    171174    using the following command as the
    172175    <systemitem class="username">root</systemitem> user:</para>
    173176
    174 <screen role="root"><userinput>install -v -m644 doc/gnupg.html/* \
    175                  /usr/share/doc/gnupg-&gnupg2-version;/html &amp;&amp;
    176 install -v -m644 doc/gnupg.{pdf,dvi,ps} \
     177<screen role="root"
     178        remap="doc"><userinput>install -v -m644 doc/gnupg.{pdf,dvi,ps} \
    177179                 /usr/share/doc/gnupg-&gnupg2-version;</userinput></screen>
    178180

  • postlfs/security/liboauth.xml

    r215c728b r5e8edab5  
    119119
    120120    <para>
    121       If you have installed <xref linkend="doxygen"/>, issue
    122       <command>make dox</command> to build the documentation.
    123     </para>
     121      If you wish to build the documentation (needs <xref linkend="doxygen"/>),
     122      issue:
     123    </para>
     124
     125<screen remap="doc"><userinput>make dox</userinput></screen>
    124126
    125127    <para>
    … …  
    139141    </para>
    140142
    141 <screen role="root"><userinput>install -v -dm755 /usr/share/doc/liboauth-&liboauth-version; &amp;&amp;
     143<screen role="root"
     144        remap="doc"><userinput>install -v -dm755 /usr/share/doc/liboauth-&liboauth-version; &amp;&amp;
    142145cp -rv doc/html/* /usr/share/doc/liboauth-&liboauth-version;</userinput></screen>
    143146

  • x/installing/libinput.xml

    r215c728b r5e8edab5  
    129129      during the testsuite from interfering with your desktop.  Copy the
    130130      file <filename>test/50-litest.conf</filename> into
    131       <filename class="directory"> ${XORG_PREFIX}/share/X11/xorg.conf.d</filename>
     131      <filename class="directory">${XORG_PREFIX}/share/X11/xorg.conf.d</filename>
    132132      and restart X. For further information see
    133133      <ulink url="https://wayland.freedesktop.org/libinput/doc/&libinput-version;/test-suite.html">libinput test suite</ulink>.
    … …  
    187187    </para>
    188188
    189 <screen role="root"><userinput>install -v -dm755      /usr/share/doc/libinput-&libinput-version;/{html,api} &amp;&amp;
     189<screen role="root"
     190        remap="doc"><userinput>install -v -dm755      /usr/share/doc/libinput-&libinput-version;/{html,api} &amp;&amp;
    190191cp -rv Documentation/* /usr/share/doc/libinput-&libinput-version;/html &amp;&amp;
    191192cp -rv api/*           /usr/share/doc/libinput-&libinput-version;/api</userinput></screen>

  • x/installing/x7driver.xml

    r215c728b r5e8edab5  
    9393          </para>
    9494        </listitem>
     95        <!-- With Kernel 5.1, VMMouse is now entirely unusable/obsolete.
     96        VMWare has a replacement in the kernel that works for both Qemu and
     97        VMWare, that allows the VMMouse instruction set to run through
     98        EVDEV events.
     99        I archived it on 2019-05-19 as a result. - renodr
    95100        <listitem>
    96101          <para>
    … …  
    98103          </para>
    99104        </listitem>
     105        -->
    100106        <listitem>
    101107          <para>
    … …  
    185191    href="x7driver-synaptics.xml"/>
    186192
    187   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    188     href="x7driver-vmmouse.xml"/>
     193 <!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     194    href="x7driver-vmmouse.xml"/> -->
    189195
    190196  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"

  • xfce/core/thunar.xml

    r215c728b r5e8edab5  
    88           "http://archive.xfce.org/src/xfce/thunar/1.8/Thunar-&thunar-version;.tar.bz2">
    99  <!ENTITY thunar-download-ftp  " ">
    10   <!ENTITY thunar-md5sum        "6a5d0f4ddcc653c4791e555f0dc63828">
     10  <!ENTITY thunar-md5sum        "3cb40548d7c642176eab8b97a5ba6d29">
    1111  <!ENTITY thunar-size          "2.2 MB">
    12   <!ENTITY thunar-buildsize     "65 MB">
    13   <!ENTITY thunar-time          "0.6 SBU">
     12  <!ENTITY thunar-buildsize     "53 MB">
     13  <!ENTITY thunar-time          "0.5 SBU">
    1414]>
    1515

  • xsoft/graphweb/firefox.xml

    r215c728b r5e8edab5  
    77  <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;/source/firefox-&firefox-version;.source.tar.xz">
    88  <!ENTITY firefox-download-ftp  " ">
    9   <!ENTITY firefox-md5sum        "a3d00fb4e950558135f08a5155745d4e">
    10   <!ENTITY firefox-size          "269 MB">
     9  <!ENTITY firefox-md5sum        "41a5d504deaed12ebf0e25bb1420f08a">
     10  <!ENTITY firefox-size          "270 MB">
    1111  <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
    1212    But the extra cached cargo files, if any, seem to be minimal -->
    13   <!ENTITY firefox-buildsize     "11.8 GB (156 MB installed) without tests">
     13  <!ENTITY firefox-buildsize     "3.8 GB (154 MB installed) without tests">
    1414  <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
    1515   most practical way to get a timing on a machine with more cores, if taking
    1616   cores offline is not practical. If in doubt, round up -->
    17   <!ENTITY firefox-time          "25 SBU (with parallelism=4) without tests">
     17  <!ENTITY firefox-time          "28 SBU (with parallelism=4) without tests">
    1818]>
    1919
    … …  
    139139      <xref linkend="autoconf213"/>,
    140140      <xref linkend="cbindgen"/>,
    141       <application>Clang</application> (from <xref linkend="llvm"/>),
    142141      both <xref linkend="gtk3"/> and
    143142      <xref linkend="gtk2"/>,
    … …  
    162161<!-- fails to build in 65.0 (headers changed)
    163162      <xref linkend="libvpx"/>, -->
    164       <xref linkend="libwebp"/>, and
     163      <xref linkend="libwebp"/>,
     164      <xref linkend="nasm"/>, and
    165165      <xref linkend="sqlite"/>
    166166    </para>
    … …  
    257257ac_add_options --with-system-icu
    258258
    259 # The gold linker is no-longer the default
    260 ac_add_options --enable-linker=gold
    261 
    262 # The shipped libdavid (av1 decoder) is not built by default,
    263 # at least on linux, but if nasm is not present libxul tries to
    264 # link to one of libdavid's objects and fails.  It is thought
    265 # libdavid will be enabled in firefox-67, at which point nasm
    266 # might be required.
    267 ac_add_options --disable-av1
     259# Do not specify the gold linker which is not the default. It will take
     260# longer and use more disk space when debug symbols are disabled.
     261
     262# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
     263# has not been installed.
     264#ac_add_options --disable-av1
    268265
    269266# You cannot distribute the binary if you do this
    … …  
    279276#ac_add_options --disable-strip
    280277#ac_add_options --disable-install-strip
     278
     279# Disabling debug symbols makes the build much smaller and a little
     280# faster. Comment this if you need to run a debugger.
     281ac_add_options --disable-debug-symbols
    281282
    282283# The BLFS editors recommend not changing anything below this line:
    … …  
    290291ac_add_options --disable-tests
    291292
    292 # With clang, unlike gcc-7 and later, the default level
    293 # of optimization produces a working build.
     293# The default level of optimization again produces a working build with gcc.
    294294ac_add_options --enable-optimize
    295295
    … …  
    362362
    363363    <para>
    364 <!--  Invoke the Python script to compile the package: -->
    365       To use the system version of ICU, run a sed to avoid a conflict between
     364      If you are still using ICU-63, run a sed to avoid a conflict between
    366365      upstream ICU's use of <literal>CheckImpl()</literal> in their public headers
    367366      and firefox's internal use of a different <literal>CheckImpl()</literal>.
    368       Then invoke the Python2 script to compile the package.
    369     </para>
    370 
    371 <screen><userinput>sed -e 's/checkImpl/checkFFImpl/g' -i js/src/vm/JSContext*.h &amp;&amp;
    372 export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib &amp;&amp;
     367    </para>
     368
     369<screen role="nodump"><userinput>sed -e 's/checkImpl/checkFFImpl/g' -i js/src/vm/JSContext*.h</userinput></screen>
     370
     371    <para>
     372      Invoke the Python2 script to compile the package.
     373    </para>
     374
     375<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
    373376export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
    374377./mach build</userinput></screen>
    … …  
    398401    </para>
    399402
    400 <screen><userinput>unset CC CXX AR NM RANLIB MOZBUILD_STATE_PATH</userinput></screen>
     403<screen><userinput>unset CC CXX MOZBUILD_STATE_PATH</userinput></screen>
    401404
    402405  </sect2>
    … …  
    407410    <para>
    408411      <command>sed -e 's/checkImpl/checkFFImpl/g' ...</command>: Although the
    409       package ships with a modified version of <application>ICU-59</application>
    410       and only tests that the system version, if requested, is at least 59,
    411       changes in <emphasis>some</emphasis> versions cause builds with the system
    412       version to fail with error messages of the form <literal>no void
    413       JSContext::checkImpl_NN member function</literal> where NN is the system
    414       <application>ICU</application> version. The sed renames the local function.
    415     </para>
    416 
    417     <para>
    418       <command>export CC=clang CXX=clang++ ...</command>: Upstream now use
    419       <application>clang</application> and building with any recent version
    420       saves a lot of space.
     412      package ships with a modified version of <application>ICU-63</application>
     413      and only tests that the system version, if used, is at least 63, changes
     414      from upstream 63 cause builds with the system version to fail with an error
     415      message <literal>no void JSContext::checkImpl_63 member function</literal>.
     416      The sed renames the local function. Upstream ICU-64 works around this.
     417    </para>
     418
     419    <para>
     420      <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
     421      <application>clang</application>, but gcc is a more secure compiler and
     422      now produces reasonably-sized builds.
    421423    </para>
    422424
    … …  
    454456      of cores, e.g. -j4 for 4 cores: First, if using all the cores causes
    455457      the build to swap because you have insufficient memory (e.g. for 4 cores
    456       a build without system graphite2 and harfbuzz now uses slightly over 8GB
     458      a build without system graphite2 and harfbuzz now uses towards 8GB
    457459      of RAM). In such cases, using fewer cores can be faster. Second, on some
    458460      machines the middle part of the build can drag on as if only one core is
    … …  
    474476      class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
    475477      symbolic link is made to keep all the plugins installed in one folder.
     478    </para>
     479
     480    <para>
     481      <option>export CC=clang CXX=clang++ AR=llvm-ar NM=llvm-nm RANLIB=llvm-ranlib</option>:
     482      Use this as an alternative to building with gcc and g++ if you wish to use
     483      the clang toolchain. Remember to unset these variables after the build.
    476484    </para>
    477485

  • xsoft/graphweb/seamonkey.xml

    r215c728b r5e8edab5  
    264264
    265265    <para>
     266      <application>GCC-9</application> generates some false positives with
     267      <command>--Werror=fromat</command>, which prevent building
     268      <application>SeaMonkey</application>. Remove this flag with the
     269      following command:
     270    </para>
     271
     272<screen><userinput>grep -rl -- '-Werror=format' |
     273    xargs sed -i 's/error=format/no-&amp;/'</userinput></screen>
     274
     275    <para>
    266276      Compile <application>SeaMonkey</application> by running the following
    267277      commands:
    268278    </para>
    269279
    270 <!-- Seems to still be needed for 2.49.2 -->
     280<!-- Seems to still be needed for 2.49.2
     281     but not in 2.49.4
    271282<screen><userinput>CFLAGS_HOLD=$CFLAGS           &amp;&amp;
    272283CXXFLAGS_HOLD=$CXXFLAGS       &amp;&amp;
    … …  
    275286export CXXFLAGS+=$EXTRA_FLAGS &amp;&amp;
    276287unset EXTRA_FLAGS             &amp;&amp;
    277 
    278 CC=gcc CXX=g++ make -f client.mk</userinput></screen>
    279 
    280     <note><para>The CC and CXX variables above are only needed if
    281     <xref linkend="llvm"/> is installed.  If using clang is desired,
    282     do not use the CFLAGS or CXXFLAGS above.</para></note>
     288-->
     289<screen><userinput>CC=gcc CXX=g++ make -f client.mk</userinput></screen>
     290
     291    <note>
     292      <para>
     293        The CC and CXX variables above are only needed if
     294        <xref linkend="llvm"/> is installed and you do not want to use clang.
     295      </para>
     296    </note>
    283297
    284298    <para>
    … …  
    296310
    297311cp -v $(find -name seamonkey.1 | head -n1) /usr/share/man/man1</userinput></screen>
    298 
     312<!-- Not needed: see above
    299313    <para>
    300314      Set the compilation flags back to their original values:
    … …  
    304318export CXXFLAGS=$CXXFLAGS_HOLD &amp;&amp;
    305319unset CFLAGS_HOLD CXXFLAGS_HOLD</userinput></screen>
    306 
     320-->
    307321    <bridgehead renderas="sect3" id="devel-seamonkey" xreflabel="SeaMonkey">
    308322      All the Development Libraries and Headers

  • xsoft/office/libreoffice.xml

    r215c728b r5e8edab5  
    389389             --with-system-lcms2         \
    390390             --with-system-libatomic_ops \
    391              --with-system-libgpgmepp    \
    392391             --with-system-libpng        \
    393392             --with-system-libxml        \

  • xsoft/other/thunderbird.xml

    r215c728b r5e8edab5  
    77  <!ENTITY thunderbird-download-http "&mozilla-http;/thunderbird/releases/&thunderbird-version;/source/thunderbird-&thunderbird-version;.source.tar.xz">
    88  <!ENTITY thunderbird-download-ftp  " ">
    9   <!ENTITY thunderbird-md5sum        "ce761c4d0f4d85c0c5ad5d1a22aa9e50">
    10   <!ENTITY thunderbird-size          "276 MB">
    11   <!ENTITY thunderbird-buildsize     "6.6 GB (134 MB installed)">
    12   <!ENTITY thunderbird-time          "27 SBU (with -j4, estimated 75 SBU with -j1)">
     9  <!ENTITY thunderbird-md5sum        "d5e1f8e084a56b5591506b619c6e3a2e">
     10  <!ENTITY thunderbird-size          "272 MB">
     11  <!ENTITY thunderbird-buildsize     "8.1 GB (142 MB installed)">
     12  <!ENTITY thunderbird-time          "28 SBU (with -j4, estimated 75 SBU with -j1)">
    1313  <!-- Verified the time at -j1 on another system for posterity's sake. -->
    1414]>
Note: See TracChangeset for help on using the changeset viewer.