linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-01-23 22:42:14 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'trunk' into lxqt

Browse Source
This commit is contained in:
Bruce Dubbs 2023-07-18 16:51:51 +00:00
commit e77c478989
132 changed files with 2499 additions and 1237 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
networking/connect/dhcp.xml → archive/dhcp.xml
View File

0
general/prog/python-modules/jinja2.xml → archive/jinja2.xml
View File

0
general/prog/python-modules/markupsafe.xml → archive/markupsafe.xml
View File

0
x/installing/x7driver-amdgpu.xml → archive/x7driver-amdgpu.xml
View File

0
x/installing/x7driver-ati.xml → archive/x7driver-ati.xml
View File

0
x/installing/x7driver-fbdev.xml → archive/x7driver-fbdev.xml
View File

0
x/installing/x7driver-intel.xml → archive/x7driver-intel.xml
View File

0
x/installing/x7driver-nouveau.xml → archive/x7driver-nouveau.xml
View File

0
x/installing/x7driver-vmware.xml → archive/x7driver-vmware.xml
View File

6
general.ent
View File

@ -114,7 +114,7 @@
<!-- End LFS versions -->
<!ENTITY blfs-bootscripts-version "20230101">
<!ENTITY blfs-bootscripts-version "20230714">
<!ENTITY systemd-units-version "20230627">
<!ENTITY blfs-wiki "https://wiki.&lfs-domainname;/blfs/wiki">
@ -123,8 +123,8 @@
relates to the version of LFS it will build/work against -->
<!ENTITY lfs113_checked "<note><para>Development versions of BLFS may not build or run
some packages properly if dependencies have been updated
since the most recent stable versions of the book.</para></note>">
some packages properly if LFS or dependencies have been updated
since the most recent stable versions of the books.</para></note>">
<!--
<!ENTITY lfs113_checked "<para>This package is known to build and work properly

6
general/genlib/exempi.xml
View File

@ -6,10 +6,10 @@
<!ENTITY exempi-download-http "https://libopenraw.freedesktop.org/download/exempi-&exempi-version;.tar.xz">
<!ENTITY exempi-download-ftp " ">
<!ENTITY exempi-md5sum "27a7d9566d2335785c03ce9e66096f2a">
<!ENTITY exempi-md5sum "c2bd12b5773f35c3832dcd1169fac3dc">
<!ENTITY exempi-size "2.7 MB">
<!ENTITY exempi-buildsize "288 MB (add 241 MB for tests)">
<!ENTITY exempi-time "0.4 SBU (using parallelism=4; add 1.9 SBU for tests)">
<!ENTITY exempi-buildsize "288 MB (add 236 MB for tests)">
<!ENTITY exempi-time "0.4 SBU (add 0.6 SBU for tests; both using parallelism=4)">
]>
<sect1 id="exempi" xreflabel="Exempi-&exempi-version;">

1
general/genlib/genlib.xml
View File

@ -144,6 +144,7 @@
<!-- systemd only -->
<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libzeitgeist.xml"/> -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="log4cplus.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="lzo.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mtdev.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="nodejs.xml"/>

8
general/genlib/glib2.xml
View File

@ -6,10 +6,10 @@
<!ENTITY glib2-download-http "&gnome-download-http;/glib/&glib2-minor;/glib-&glib2-version;.tar.xz">
<!ENTITY glib2-download-ftp "&gnome-download-ftp;/glib/&glib2-minor;/glib-&glib2-version;.tar.xz">
<!ENTITY glib2-md5sum "9e8f5c00f0cdf71c7e47e554bfbf9dcb">
<!ENTITY glib2-md5sum "b0df5864ec08248e79c13f71a717aa03">
<!ENTITY glib2-size "5.0 MB">
<!ENTITY glib2-buildsize "127 MB (add 10 MB for tests)">
<!ENTITY glib2-time "0.4 SBU (add 0.3 SBU for tests; both using parallelism=4)">
<!ENTITY glib2-buildsize "147 MB (add 10 MB for tests)">
<!ENTITY glib2-time "0.7 SBU (add 0.4 SBU for tests; both using parallelism=4)">
]>
<sect1 id="glib2" xreflabel="GLib-&glib2-version;">
@ -273,7 +273,7 @@ cp -r ../docs/reference/{gio,glib,gobject} /usr/share/doc/glib-&glib2-version;</
/usr/lib/gio,
/usr/lib/glib-2.0,
/usr/share/glib-2.0,
/usr/share/doc/glib-&glib2-version;, and
/usr/share/doc/{glib-2.0,glib-&glib2-version;}, and
/usr/share/gtk-doc/html/{gio,glib,gobject} (optional)
</seg>
</seglistitem>

35
general/genlib/inih.xml
View File

@ -7,9 +7,9 @@
<!ENTITY inih-download-http
"https://github.com/benhoyt/inih/archive/r&inih-version;/inih-r&inih-version;.tar.gz">
<!ENTITY inih-download-ftp " ">
<!ENTITY inih-md5sum "e27e394554d9f339b728035a5766d8f3">
<!ENTITY inih-size "20 KB">
<!ENTITY inih-buildsize "704 KB">
<!ENTITY inih-md5sum "07aa33593487633519fb3a0e55546c09">
<!ENTITY inih-size "19 KB">
<!ENTITY inih-buildsize "808 KB">
<!ENTITY inih-time "less than 0.1 SBU">
]>
@ -120,6 +120,35 @@ The tests seem to be run, but there is no output or log.
</seglistitem>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
<varlistentry id="libinih">
<term><filename class="libraryfile">libinih.so</filename></term>
<listitem>
<para>
is the inih main library
</para>
<indexterm zone="inih libinih">
<primary sortas="c-libinih">libinih.so</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="libINIReader">
<term><filename class="libraryfile">libINIReader.so</filename></term>
<listitem>
<para>
is the inih parser library
</para>
<indexterm zone="inih libINIReader">
<primary sortas="c-libINIReader">libINIReader.so</primary>
</indexterm>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>

3
general/genlib/intel-gmmlib.xml
View File

@ -102,7 +102,8 @@ cmake -DCMAKE_INSTALL_PREFIX=/usr \
make</userinput></screen>
<para>
This package does not come with a test suite.
The test suite is normally run by <command>make</command> unless
-DRUN_TEST_SUITE=NO is passed to cmake.
</para>
<para>

9
general/genlib/js102.xml
View File

@ -10,13 +10,14 @@
we have moved to next firefox-esr (ff-91) and JS has not moved
<!ENTITY ff91-version "&JS91-version;"> -->
<!ENTITY ff102-version "&firefox-version;">
<!--<!ENTITY ff102-version "&firefox-version;">-->
<!ENTITY js102-download-http "&mozilla-http;/firefox/releases/&JS102-version;esr/source/firefox-&JS102-version;esr.source.tar.xz">
<!ENTITY js102-download-ftp " ">
<!ENTITY js102-md5sum "2d23d6194f285fea5693b2550851720c">
<!ENTITY js102-size "461 MB">
<!ENTITY js102-md5sum "42b9a73626ed8281b86222f6f0a96c73">
<!ENTITY js102-md5sum "">
<!ENTITY js102-size "464 MB">
<!ENTITY js102-buildsize "3.3 GB (38 MB installed after removing 34MB static lib)">
<!ENTITY js102-time "1.8 SBU (with parallelism=4)">
<!ENTITY js102-time "1.7 SBU (with parallelism=4)">
]>
<sect1 id="js102" xreflabel="JS-&JS102-version;">

7
general/genlib/libaio.xml
View File

@ -89,13 +89,6 @@
<screen><userinput>make</userinput></screen>
<para>
If you want to run the test suite, fix an issue with Glibc-2.34 or
later:
</para>
<screen><userinput>sed 's/-Werror//' -i harness/Makefile</userinput></screen>
<para>
To test the results, issue: <command>make partcheck</command>.
</para>

13
general/genlib/libblockdev.xml
View File

@ -7,9 +7,9 @@
<!ENTITY libblockdev-download-http
"https://github.com/storaged-project/libblockdev/releases/download/&libblockdev-version;-1/libblockdev-&libblockdev-version;.tar.gz">
<!ENTITY libblockdev-download-ftp " ">
<!ENTITY libblockdev-md5sum "ef5dd9a42ac7d31d88842222773ded70">
<!ENTITY libblockdev-md5sum "5907ac23f6ed0d235c24a520f4226fc7">
<!ENTITY libblockdev-size "1.0 MB">
<!ENTITY libblockdev-buildsize "16 MB">
<!ENTITY libblockdev-buildsize "13 MB">
<!ENTITY libblockdev-time "0.1 SBU">
]>
@ -95,8 +95,10 @@
<xref linkend="parted"/>,
<xref linkend="volume_key"/>,
<ulink url="https://people.redhat.com/~heinzm/sw/dmraid/">dmraid</ulink>,
<ulink url="https://bcachefs.org/">bcachefs</ulink>, and
<ulink url="https://github.com/pmem/ndctl">ndctl</ulink>
<ulink url="https://bcachefs.org/">bcachefs</ulink>,
<ulink url="https://github.com/pmem/ndctl">ndctl</ulink>, and
<ulink url="https://github.com/Datera/targetcli">targetcli</ulink>
(for tests)
</para>
</sect2>
@ -129,7 +131,8 @@
make</userinput></screen>
<para>
This package does not come with a working test suite.
The test suite requires <application>targetcli</application>, which
is not a part of BLFS.
</para>
<para>

2
general/genlib/libbytesize.xml
View File

@ -6,7 +6,7 @@
<!ENTITY libbytesize-download-http "https://github.com/storaged-project/libbytesize/releases/download/&libbytesize-version;/libbytesize-&libbytesize-version;.tar.gz">
<!ENTITY libbytesize-download-ftp " ">
<!ENTITY libbytesize-md5sum "ae3a3b3a88398a83737bea9628820256">
<!ENTITY libbytesize-md5sum "ba30fedcc832d9e0ae6cdc7a5602efbb">
<!ENTITY libbytesize-size "448 KB">
<!ENTITY libbytesize-buildsize "3.5 MB">
<!ENTITY libbytesize-time "less than 0.1 SBU (including tests)">

4
general/genlib/libgudev.xml
View File

@ -8,9 +8,9 @@
"&gnome-download-http;/libgudev/&libgudev-version;/libgudev-&libgudev-version;.tar.xz">
<!ENTITY libgudev-download-ftp
"&gnome-download-ftp;/libgudev/&libgudev-version;/libgudev-&libgudev-version;.tar.xz">
<!ENTITY libgudev-md5sum "a7783083cd74957d3a727ddc4737ee84">
<!ENTITY libgudev-md5sum "46da30a1c69101c3a13fa660d9ab7b73">
<!ENTITY libgudev-size "32 KB">
<!ENTITY libgudev-buildsize "1.8 MB">
<!ENTITY libgudev-buildsize "2.0 MB">
<!ENTITY libgudev-time "less than 0.1 SBU">
]>

2
general/genlib/liblinear.xml
View File

@ -6,7 +6,7 @@
<!ENTITY liblinear-download-http "https://github.com/cjlin1/liblinear/archive/v&liblinear-version;/liblinear-&liblinear-version;.tar.gz">
<!ENTITY liblinear-download-ftp " ">
<!ENTITY liblinear-md5sum "b52a3e80fc5664c41249d65b23f50546">
<!ENTITY liblinear-md5sum "0c81dd2b2cabc4fba85f61b9dc51c4a3">
<!ENTITY liblinear-size "560 KB">
<!ENTITY liblinear-buildsize "1.6 MB">
<!ENTITY liblinear-time "less than 0.1 SBU">

8
general/genlib/libnvme.xml
View File

@ -29,7 +29,7 @@
provides type definitions for NVMe specification structures,
enumerations, and bit fields, helper functions to construct, dispatch,
and decode commands and payloads, and utilities to connect, scan, and
manage nvme devices on a Linux system.
manage NVMe devices on a Linux system.
</para>
&lfs113_checked;
@ -101,6 +101,10 @@ cd build &amp;&amp;
meson setup --prefix=/usr --buildtype=release -Dlibdbus=auto .. &amp;&amp;
ninja</userinput></screen>
<para>
To run the tests, issue: <command>ninja test</command>.
</para>
<para>
Now, as the <systemitem class="username">root</systemitem> user:
</para>
@ -142,7 +146,7 @@ ninja</userinput></screen>
<listitem>
<para>
contains functions used to handle operations
related to nvme devices.
relating to NVMe devices.
</para>
<indexterm zone="libnvme libnvme-lib">
<primary sortas="c-libnvme">libnvme.so</primary>

2
general/genlib/libpaper.xml
View File

@ -6,7 +6,7 @@
<!ENTITY libpaper-download-http "https://github.com/rrthomas/libpaper/releases/download/v&libpaper-version;/libpaper-&libpaper-version;.tar.gz">
<!ENTITY libpaper-download-ftp " ">
<!ENTITY libpaper-md5sum "c9136c0d483b868818637ec54200c975">
<!ENTITY libpaper-md5sum "3ee7420ed7afae14a3387a4a0e68c60f">
<!ENTITY libpaper-size "1.2 MB">
<!ENTITY libpaper-buildsize "11 MB (with tests)">
<!ENTITY libpaper-time "0.1 SBU (with tests)">

4
general/genlib/libqalculate.xml
View File

@ -7,10 +7,10 @@
<!-- Normally, the "a" after version shouldn't be needed except for 4.5.0 -->
<!ENTITY libqalculate-download-http "https://github.com/Qalculate/libqalculate/releases/download/v&libqalculate-version;/libqalculate-&libqalculate-version;.tar.gz">
<!ENTITY libqalculate-download-ftp " ">
<!ENTITY libqalculate-md5sum "ff001e18c3507cdb536f8374b3508b3e">
<!ENTITY libqalculate-md5sum "7fcad72cb9779afc14fecdf0a0dcc9f1">
<!ENTITY libqalculate-size "2.5 MB">
<!ENTITY libqalculate-buildsize "140 MB (with tests)">
<!ENTITY libqalculate-time "0.8 SBU (With tests; both using parallelism=4)">
<!ENTITY libqalculate-time "0.7 SBU (With tests; both using parallelism=4)">
]>
<sect1 id="libqalculate" xreflabel="libqalculate-&libqalculate-version;">

2
general/genlib/libuv.xml
View File

@ -6,7 +6,7 @@
<!ENTITY libuv-download-http "https://dist.libuv.org/dist/v&libuv-version;/libuv-v&libuv-version;.tar.gz">
<!ENTITY libuv-download-ftp " ">
<!ENTITY libuv-md5sum "b4d51391102818e238597e3ee919f577">
<!ENTITY libuv-md5sum "fa56dafe664d21f9568adebc428d2d64">
<!ENTITY libuv-size "1.2 MB">
<!ENTITY libuv-buildsize "14 MB (add 14 MB for tests)">
<!ENTITY libuv-time "less than 0.1 SBU (add 0.5 SBU for tests)">

161
general/genlib/log4cplus.xml Normal file
View File

@ -0,0 +1,161 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY log4cplus-download-http "https://github.com/log4cplus/log4cplus/releases/download/REL_&log4cplus-release;/log4cplus-&log4cplus-version;.tar.xz">
<!ENTITY log4cplus-download-ftp " ">
<!ENTITY log4cplus-md5sum "62928d480ebec1476fe74b900f2a1672">
<!ENTITY log4cplus-size "919 KB">
<!ENTITY log4cplus-buildsize "72.4 MB">
<!ENTITY log4cplus-time "0.5 SBU">
]>
<sect1 id="log4cplus" xreflabel="log4cplus-&log4cplus-version;">
<?dbhtml filename="log4cplus.html"?>
<title>log4cplus-&log4cplus-version;</title>
<indexterm zone="log4cplus">
<primary sortas="a-log4cplus">log4cplus</primary>
</indexterm>
<sect2 role="package">
<title>Introduction to log4cplus</title>
<para>
<application>log4cplus</application> is a simple to use C++20
logging API providing thread--safe, flexible, and arbitrarily
granular control over log management and configuration. It is
modeled after the Java log4j API.
</para>
&lfs113_checked;
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
Download (HTTP): <ulink url="&log4cplus-download-http;"/>
</para>
</listitem>
<listitem>
<para>
Download (FTP): <ulink url="&log4cplus-download-ftp;"/>
</para>
</listitem>
<listitem>
<para>
Download MD5 sum: &log4cplus-md5sum;
</para>
</listitem>
<listitem>
<para>
Download size: &log4cplus-size;
</para>
</listitem>
<listitem>
<para>
Estimated disk space required: &log4cplus-buildsize;
</para>
</listitem>
<listitem>
<para>
Estimated build time: &log4cplus-time;
</para>
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">log4cplus Dependencies</bridgehead>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="qt5"/>
</para>
<para condition="html" role="usernotes">User Notes:
<ulink url="&blfs-wiki;/log4cplus"/>
</para>
</sect2>
<sect2 role="installation">
<title>Installation of log4cplus</title>
<para>
Build <application>log4cplus</application> by running the following
command:
</para>
<screen><userinput>./configure --prefix=/usr &amp;&amp;
make</userinput></screen>
<para>
To test the results, issue: <command>make check</command>.
</para>
<para>
Now, install the package as the
<systemitem class="username">root</systemitem> user:
</para>
<screen role="root"><userinput>make install</userinput></screen>
</sect2>
<sect2 role="commands">
<title>Command Explanations</title>
<para>
<parameter>--with-qt5</parameter>: This option enables
compilation of a separate shared library (liblog4cplusqt5debugappender)
that implements Qt5DebugAppender. It requires Qt5 and pkg-config
to be available.
</para>
</sect2>
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
<segtitle>Installed Programs</segtitle>
<segtitle>Installed Library</segtitle>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>
None
</seg>
<seg>
log4cplus.so
</seg>
<seg>
None
</seg>
</seglistitem>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
<varlistentry id="log4cplus-lib">
<term><filename class="libraryfile">log4cplus.so</filename></term>
<listitem>
<para>
is the log4cplus library
</para>
<indexterm zone="log4cplus log4cplus-lib">
<primary sortas="c-log4cplus">log4cplus.so</primary>
</indexterm>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>

6
general/genlib/wayland-protocols.xml
View File

@ -6,9 +6,9 @@
<!ENTITY wayland-protocols-download-http "https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/&wayland-protocols-version;/downloads/wayland-protocols-&wayland-protocols-version;.tar.xz">
<!ENTITY wayland-protocols-download-ftp " ">
<!ENTITY wayland-protocols-md5sum "1584de13eb30a4d1f2cd06c08ee24354">
<!ENTITY wayland-protocols-size "84 KB">
<!ENTITY wayland-protocols-buildsize "7.8 MB (with tests)">
<!ENTITY wayland-protocols-md5sum "00c2cedb0d2df714a0965a00c19385c6">
<!ENTITY wayland-protocols-size "92 KB">
<!ENTITY wayland-protocols-buildsize "7.4 MB (with tests)">
<!ENTITY wayland-protocols-time "less than 0.1 SBU (with tests)">
]>

6
general/genlib/xapian.xml
View File

@ -7,10 +7,10 @@
<!ENTITY xapian-download-http
"https://oligarchy.co.uk/xapian/&xapian-version;/xapian-core-&xapian-version;.tar.xz">
<!ENTITY xapian-download-ftp " ">
<!ENTITY xapian-md5sum "18412be5f8b62044f139937c3d7069d7">
<!ENTITY xapian-md5sum "241273b1fcde4c3fd12f0d0586e6bb6c">
<!ENTITY xapian-size "2.9 MB">
<!ENTITY xapian-buildsize "147 MB (add 154 MB for tests)">
<!ENTITY xapian-time "0.5 SBU (using parallelism=4; add 12 SBU for tests)">
<!ENTITY xapian-buildsize "144 MB (add 163 MB for tests)">
<!ENTITY xapian-time "0.4 SBU (using parallelism=4; add 11 SBU for tests)">
]>
<sect1 id="xapian" xreflabel="xapian-&xapian-version;">

6
general/genutils/graphviz.xml
View File

@ -6,10 +6,10 @@
<!ENTITY graphviz-download-http "https://gitlab.com/graphviz/graphviz/-/archive/&graphviz-version;/graphviz-&graphviz-version;.tar.bz2">
<!ENTITY graphviz-download-ftp " ">
<!ENTITY graphviz-md5sum "ed97ac0f4a45ee0578ef8216503105a7">
<!ENTITY graphviz-md5sum "e6a45773e84d3f83fed87cb6290563e6">
<!ENTITY graphviz-size "26 MB">
<!ENTITY graphviz-buildsize "213 MB">
<!ENTITY graphviz-time "0.6 SBU (using parallelism=4)">
<!ENTITY graphviz-buildsize "262 MB">
<!ENTITY graphviz-time "0.7 SBU (using parallelism=4)">
]>
<sect1 id="graphviz" xreflabel="Graphviz-&graphviz-version;">

20
general/genutils/imagemagick.xml
View File

@ -4,16 +4,16 @@
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY imagemagick-patch-version "61">
<!ENTITY imagemagick-patch-version "12">
<!ENTITY imagemagick-download-http "https://www.imagemagick.org/archive/releases/ImageMagick-&imagemagick-version;-&imagemagick-patch-version;.tar.xz">
<!-- 2021-01-14 : ftp.imagemagick.org hangs, assume no longer usable
<!ENTITY imagemagick-download-ftp "ftp://ftp.imagemagick.org/pub/ImageMagick/releases/ImageMagick-&imagemagick-version;-&imagemagick-patch-version;.tar.xz"> -->
<!ENTITY imagemagick-download-ftp " ">
<!ENTITY imagemagick-md5sum "f9973657738b5c970325e97f198b9977">
<!ENTITY imagemagick-size "9.9 MB">
<!ENTITY imagemagick-buildsize "192 MB (with typical dependencies; add 20 MB for checks)">
<!ENTITY imagemagick-time "0.8 SBU (with typical dependencies; add 1.9 SBU for checks, both using parallelism=4)">
<!ENTITY imagemagick-md5sum "7d04ecc28b035922697630c92cdfbfb8">
<!ENTITY imagemagick-size "9.8 MB">
<!ENTITY imagemagick-buildsize "207 MB (with typical dependencies; add 31 MB for checks)">
<!ENTITY imagemagick-time "0.8 SBU (with typical dependencies; add 0.8 SBU for checks, both using parallelism=4)">
]>
<!-- Editors: It is highly unlikely that the buildsize (disk space used) will
@ -48,7 +48,8 @@
For those of us who touch this infrequently:
DPS/dpsXclient is from apple so not relevant to linux builds
GVC is part of Graphviz and documented in the explanations
LQR is Liquid Rescale -->
iLQR is Liquid Rescale
ufraw-batch (ufraw) is unmaintained and does not build with current exiv2 -->
<sect1 id="imagemagick" xreflabel="ImageMagick-&imagemagick-version;-&imagemagick-patch-version;">
<?dbhtml filename="imagemagick.html"?>
@ -166,7 +167,7 @@
<xref linkend="libgxps"/>,
<xref linkend="libjpeg"/>,
<xref linkend="libpng"/>,
<xref linkend="libraw"/> (RAW_R),
<xref linkend="libraw"/> (for dng files, needs the thread-safe libraw_r),
<xref linkend="librsvg"/>,
<xref linkend="libtiff"/>,
<xref linkend="libwebp"/>,
@ -219,10 +220,15 @@
<ulink url="https://wvware.sourceforge.net/">libwmf</ulink>,
<ulink url="https://sk1project.net/uc2/">
UniConvertor</ulink>,
<!-- ufraw-batch was a delegate program, the delegate library coders/dng.so
is used if librar_r is present, ufraw now ftbfs with exiv2-0.28, and IM-7.1.1
in any case (if no libraw) invokes it to ask for a temp png file, but then
tries to open the temp file using a ppm suffix, which of course fails.
<ulink url="https://ufraw.sourceforge.net/">ufraw</ulink> (for dng files,
see
<ulink url="https://imagemagick.org/script/formats.php">
https://imagemagick.org/script/formats.php</ulink> for some special switches)
-->
and
<ulink url="https://www.cs.utah.edu/gdc/projects/urt/">Utah Raster Toolkit</ulink>
(or <ulink url="http://www.mcmurchy.com/urt/urt-3.1b.tar.gz">URT-3.1b</ulink>)

3
general/graphlib/freetype2.xml
View File

@ -155,8 +155,7 @@ make</userinput></screen>
<systemitem class="username">root</systemitem> user:
</para>
<screen role="root"><userinput>install -v -m755 -d /usr/share/doc/freetype-&freetype2-version; &amp;&amp;
cp -v -R docs/* /usr/share/doc/freetype-&freetype2-version; &amp;&amp;
<screen role="root"><userinput>cp -v -R docs -T /usr/share/doc/freetype-&freetype2-version; &amp;&amp;
rm -v /usr/share/doc/freetype-&freetype2-version;/freetype-config.1</userinput></screen>
</sect2>

1
general/graphlib/graphite2.xml
View File

@ -148,6 +148,7 @@ make</userinput></screen>
<para>
To test the results, issue: <command>make test</command>.
One test named <filename>nametabletest</filename> is known to fail.
</para>
<para>

9
general/graphlib/harfbuzz.xml
View File

@ -7,9 +7,9 @@
<!ENTITY harfbuzz-download-http
"https://github.com/harfbuzz/harfbuzz/releases/download/&harfbuzz-version;/harfbuzz-&harfbuzz-version;.tar.xz">
<!ENTITY harfbuzz-download-ftp " ">
<!ENTITY harfbuzz-md5sum "b6cbea4577691c2b65aa21a8515a0136">
<!ENTITY harfbuzz-md5sum "6d4c01cb9611b7c68b805655096670ca">
<!ENTITY harfbuzz-size "18 MB">
<!ENTITY harfbuzz-buildsize "149 MB (with tests)">
<!ENTITY harfbuzz-buildsize "151 MB (with tests)">
<!ENTITY harfbuzz-time "0.7 SBU (Using parallelism=4; with tests)">
]>
@ -90,8 +90,9 @@
<xref linkend="git"/>,
<xref linkend="gtk-doc"/>,
<ulink url="https://pypi.org/project/FontTools/">FontTools</ulink>
(Python 3 module, for the test suite), and
<ulink url="https://www.colm.net/open-source/ragel/">ragel</ulink>
(Python 3 module, for the test suite),
<ulink url="https://www.colm.net/open-source/ragel/">ragel</ulink>,
and <ulink url="https://github.com/bytecodealliance/wasm-micro-runtime">wasm-micro-runtime</ulink>
</para>
<warning>

8
general/graphlib/libjpeg-turbo.xml
View File

@ -6,10 +6,10 @@
<!ENTITY libjpeg-download-http "&sourceforge-dl;/libjpeg-turbo/libjpeg-turbo-&libjpeg-turbo-version;.tar.gz">
<!ENTITY libjpeg-download-ftp " ">
<!ENTITY libjpeg-md5sum "aed60d4d776dd5cf00b5a01c609d50f7">
<!ENTITY libjpeg-size "2.2 MB">
<!ENTITY libjpeg-buildsize "17 MB (add 17 MB for tests)">
<!ENTITY libjpeg-time "0.1 SBU (using parallelism=4; add 0.2 SBU for tests)">
<!ENTITY libjpeg-md5sum "aa1f0a1c72cb6772e34d9d5136267f56">
<!ENTITY libjpeg-size "2.7 MB">
<!ENTITY libjpeg-buildsize "55 MB (with tests)">
<!ENTITY libjpeg-time "0.5 SBU (with tests; both using parallelism=4)">
]>
<sect1 id="libjpeg" xreflabel="libjpeg-turbo-&libjpeg-turbo-version;">

10
general/graphlib/librsvg.xml
View File

@ -6,7 +6,7 @@
<!ENTITY librsvg-download-http "&gnome-download-http;/librsvg/&librsvg-minor;/librsvg-&librsvg-version;.tar.xz">
<!ENTITY librsvg-download-ftp "&gnome-download-ftp;/librsvg/&librsvg-minor;/librsvg-&librsvg-version;.tar.xz">
<!ENTITY librsvg-md5sum "023e34798503c964ad982d130ee369c9">
<!ENTITY librsvg-md5sum "3a73cf8b41be9c231885801f2ad49cd6">
<!ENTITY librsvg-size "5.4 MB">
<!ENTITY librsvg-buildsize "747 MB (25 MB installed), add 378 MB for tests">
<!ENTITY librsvg-time "0.7 SBU (Add 0.8 SBU for tests; both using parallelism=4)">
@ -109,12 +109,12 @@
make</userinput></screen>
<para>
To test the results, issue: <command>make -k check</command>. During
testing some binaries are rebuilt with a different debug level, so you
should run <command>make</command> again after the tests are complete
to ensure everything is ready to be installed.
To test the results, issue:
</para>
<screen remap='test'><userinput>sed 's/-Z unstable-options//' -i Makefile &amp;&amp;
make check</userinput></screen>
<para>
Now, as the <systemitem class="username">root</systemitem> user:
</para>

9
general/graphlib/opencv.xml
View File

@ -6,11 +6,10 @@
<!ENTITY opencv-download-http "https://github.com/opencv/opencv/archive/&opencv-version;/opencv-&opencv-version;.tar.gz">
<!ENTITY opencv-download-ftp " ">
<!ENTITY opencv-md5sum "13e13244cb0cc6ec4f01eacd38d05d17">
<!ENTITY opencv-size "87 MB">
<!ENTITY opencv-buildsize "675 MB">
<!ENTITY opencv-time "3.3 SBU (using parallelism=4)">
<!ENTITY opencv-md5sum "c2225e737ce7f671b839a687f2dc7ab9">
<!ENTITY opencv-size "88 MB">
<!ENTITY opencv-buildsize "783 MB">
<!ENTITY opencv-time "4.1 SBU (using parallelism=4)">
<!ENTITY opencv-contrib-download "https://github.com/opencv/opencv_contrib/archive/&opencv-version;/opencv_contrib-&opencv-contrib-version;.tar.gz">
]>

13
general/graphlib/poppler.xml
View File

@ -6,7 +6,7 @@
<!ENTITY poppler-download-http "https://poppler.freedesktop.org/poppler-&poppler-version;.tar.xz">
<!ENTITY poppler-download-ftp " ">
<!ENTITY poppler-md5sum "088f9f2c6730f93a62aa6b46a6f0a6bf">
<!ENTITY poppler-md5sum "c85c6640ac0b0e974887c41df9639e2e">
<!ENTITY poppler-size "1.8 MB">
<!ENTITY poppler-buildsize "91 MB (with Qt5 library and tests)">
<!ENTITY poppler-time "0.7 SBU (with parallelism=4, Qt5 library, and tests)">
@ -155,17 +155,6 @@
<sect2 role="installation">
<title>Installation of Poppler</title>
<!-- remove when version is gtr 23.06.0 -->
<!-- missing incl is fixed upstream already -->
<para>
First add a missing include statement which will break compilation
on 32-bit systems:
</para>
<screen><userinput>sed -e '/#include "GPGMECryptoSignBackend.h"/i#include &lt;config.h&gt;' \
-i poppler/GPGMECryptoSignBackend.cc</userinput></screen>
<!-- /remove -->
<para>
Install <application>Poppler</application> by running the following
commands:

6
general/graphlib/qpdf.xml
View File

@ -6,10 +6,10 @@
<!ENTITY qpdf-download-http "https://github.com/qpdf/qpdf/releases/download/v&qpdf-version;/qpdf-&qpdf-version;.tar.gz">
<!ENTITY qpdf-download-ftp " ">
<!ENTITY qpdf-md5sum "6806fb6d150d7abf426e191a4718f659">
<!ENTITY qpdf-md5sum "d916ac26b7f30a5cf3827c708c455ec9">
<!ENTITY qpdf-size "18 MB">
<!ENTITY qpdf-buildsize "258 MB (add 1 MB for tests)">
<!ENTITY qpdf-time "0.6 SBU (using parallelism=4; add 0.5 SBU for tests)">
<!ENTITY qpdf-buildsize "253 MB (add 1 MB for tests)">
<!ENTITY qpdf-time "0.4 SBU (using parallelism=4; add 0.5 SBU for tests)">
]>
<sect1 id="qpdf" xreflabel="Qpdf-&qpdf-version;">

10
general/prog/java.xml
View File

@ -8,18 +8,18 @@
the directory: this saves more than 70 MB. -->
<!ENTITY anduin-download "&sources-anduin-http;/OpenJDK/OpenJDK-&openjdk-version;">
<!ENTITY openjdk-download-binary-x86 "&sources-anduin-http;/OpenJDK/OpenJDK-&openjdk-version;/OpenJDK-&openjdk-version;+&openjdk-build;-i686-bin.tar.xz">
<!ENTITY openjdk-bin-md5sum-x86 "e5a9566e3d3a667b9098908b72855da8">
<!ENTITY openjdk-bin-md5sum-x86 "1896a32b13637961b4fbd88dfc47c07b">
<!ENTITY openjdk-bin-size-x86 "159 MB">
<!ENTITY openjdk-bin-buildsize-x86 "307 MB">
<!ENTITY openjdk-bin-buildsize-x86 "310 MB">
<!-- Not uploaded to anduin, since this file is now available under GNU GPLv2
licence.-->
<!-- Reuploaded to anduin due to the complexity of the download URL, per Bruce's
request. - Doug -->
<!ENTITY openjdk-download-binary-x64 "&sources-anduin-http;/OpenJDK/OpenJDK-&openjdk-version;/OpenJDK-&openjdk-version;+&openjdk-build;-x86_64-bin.tar.xz">
<!ENTITY openjdk-bin-md5sum-x64 "1fccb8cd903f395ba1a80c678ba2a2e0">
<!ENTITY openjdk-bin-size-x64 "160 MB">
<!ENTITY openjdk-bin-buildsize-x64 "324 MB">
<!ENTITY openjdk-bin-md5sum-x64 "f655a50ff1a476db482e0a224344417b">
<!ENTITY openjdk-bin-size-x64 "166 MB">
<!ENTITY openjdk-bin-buildsize-x64 "337 MB">
]>
<sect1 id="java" xreflabel="Java-&openjdk-version;">

10
general/prog/llvm.xml
View File

@ -347,7 +347,10 @@ ninja docs-llvm-html docs-llvm-man</userinput></screen>
requires echoing 0 to <filename
class="directory">/sys/devices/system/cpu/cpu&lt;N&gt;/online</filename>
by the <systemitem class="username">root</systemitem> user and makes them
temporarily unusable by all jobs on the machine.)
temporarily unusable by all jobs on the machine.) One test named
<filename>Linux/clone_setns.cpp</filename> will fail if
<option>CONFIG_USER_NS</option> is not enabled in kernel
configuration.
<!-- 16.0.3: 67327 Passed, 23510 Unsupported, 85 Skipped,
124 Expectedly Failed
16.0.4 67327 Passed, 23507 Unsupported, 85 Skipped,
@ -361,6 +364,11 @@ ninja docs-llvm-html docs-llvm-man</userinput></screen>
ThreadSanitizer-x86_64 :: Linux/clone_setns.cpp
16.0.5 had the same test failures as 16.0.4. - bdubbs
16.0.5 in LFS r11.3-141 with a minimal kernel configuration:
67330 Passed, 23512 Unsupported, 85 Skipped,
124 Expectedly Failed, 1 Failed
FAIL: ThreadSanitizer-x86_64 :: Linux/clone_setns.cpp - xry111
-->
<!-- To editors: it seems there is a more thorough test suite named

9
general/prog/mercurial.xml
View File

@ -6,10 +6,10 @@
<!ENTITY mercurial-download-http "https://www.mercurial-scm.org/release/mercurial-&mercurial-version;.tar.gz">
<!ENTITY mercurial-download-ftp " ">
<!ENTITY mercurial-md5sum "4fb37e70718f5c026a3a9298e7bb8170">
<!ENTITY mercurial-size "7.8 MB">
<!ENTITY mercurial-buildsize "80 MB (with docs, add 2.3 GB for tests)">
<!ENTITY mercurial-time "0.3 SBU (with docs; add 14 SBU for tests; both using parallelism=4)">
<!ENTITY mercurial-md5sum "54307af52ba5e948d9d26c3bead0eb60">
<!ENTITY mercurial-size "7.9 MB">
<!ENTITY mercurial-buildsize "115 MB (with docs, add 1.5 GB for tests)">
<!ENTITY mercurial-time "0.3 SBU (with docs; add 27 SBU for tests; both using parallelism=4)">
]>
<sect1 id="mercurial" xreflabel="Mercurial-&mercurial-version;">
@ -140,6 +140,7 @@
# Ran 938 tests, 64 skipped, 8 failed. real 32m13.014s -bdubbs 17 Apr 23.
# Ran 935 tests, 69 skipped, 8 failed. real 26m15.875s -bdubbs 10 Jun 23.
# Ran 940 tests, 64 skipped, 8 failed. real omitted -bdubbs 26 Jun 23.
# Ran 948 tests, 66 skipped, 0 failed. -pierre 12 Jul 23 (mercurial-6.5).
-->
In order to
investigate any apparently failing tests, you may use the

23
general/prog/openjdk.xml
View File

@ -5,21 +5,21 @@
%general-entities;
<!ENTITY ojdk-tarball "jdk-&openjdk-version;-ga.tar.gz">
<!ENTITY ojdk-repo "https://github.com/openjdk/jdk19u">
<!ENTITY ojdk-repo "https://github.com/openjdk/jdk20u">
<!ENTITY ojdk-download "&ojdk-repo;/archive/&ojdk-tarball;">
<!ENTITY anduin-download "&sources-anduin-http;/OpenJDK/OpenJDK-&openjdk-version;">
<!ENTITY ojdk-md5sum "2c5489f4830bce40240dc4f76f890156">
<!ENTITY ojdk-size "103 MB">
<!ENTITY ojdk-md5sum "2a85b13d3d6ef6abfe8d7775481b89a9">
<!ENTITY ojdk-size "104 MB">
<!ENTITY jtreg-version "6.1+1">
<!ENTITY jtreg-version "7.2+1">
<!ENTITY jtreg-download "&anduin-download;/jtreg-&jtreg-version;.tar.gz">
<!ENTITY jtreg-md5sum "49e6bfa2506e96f461a01f9421a0961c">
<!ENTITY jtreg-size "8.0 MB">
<!ENTITY jtreg-md5sum "530eb67155e0a399d1a68b2f8584613a">
<!ENTITY jtreg-size "8.9 MB">
<!ENTITY ojdk-bdsize "5.1 GB (add 595 MB for tests)">
<!ENTITY ojdk-time "3.8 SBU with 4 jobs (add 41 SBU for tests with 4 jobs)">
<!ENTITY ojdk-bdsize "3.5 GB (add 789 MB for tests)">
<!ENTITY ojdk-time "6.1 SBU with 4 jobs (add 40 SBU for tests with 4 jobs)">
]>
<sect1 id="openjdk" xreflabel="OpenJDK-&openjdk-version;">
@ -194,7 +194,9 @@
<xref linkend="mercurial"/>,
<!-- not needed now, it seems
an X Window manager such as <xref linkend="twm"/> (for the tests), and
--> <ulink url="https://pandoc.org/">pandoc</ulink>, and
-->
<ulink url="https://ccache.dev/">ccache</ulink>,
<ulink url="https://pandoc.org/">pandoc</ulink>, and
<ulink url="https://zlib.net/pigz">pigz</ulink>
</para>
@ -303,6 +305,9 @@ unset JT_JAVA</userinput></screen>
19.0.2+7:
for x86_64: passed: 6,426; failed: 61; error: 14
for i686: passed: 6,377; failed: 34; error: 11
20.0.1+9:
for x86_64: passed: 6,515; failed: 65; error: 13
for i686: passed: 6,520; failed: 60; error: 13
-->
<para>

6
general/prog/perl-modules/perl-lwp-protocol-https.xml
View File

@ -5,7 +5,7 @@
%general-entities;
<!ENTITY my-download-http "&perl_authors;/id/O/OA/OALDERS/LWP-Protocol-https-&LWP-Protocol-https-version;.tar.gz">
<!ENTITY my-md5sum "cf64e4bc57a9266ac4343cdf0808c5c8">
<!ENTITY my-md5sum "6615a250c8963a2333ea6d0fbbec306b">
]>
@ -43,6 +43,7 @@
</listitem>
</itemizedlist>
<!--
<bridgehead renderas="sect4">Additional Download</bridgehead>
<itemizedlist spacing="compact">
<listitem>
@ -52,6 +53,7 @@
</para>
</listitem>
</itemizedlist>
-->
<bridgehead renderas="sect4">LWP::Protocol::https Dependencies</bridgehead>
@ -70,6 +72,7 @@
<sect3 role="installation">
<title>Installation of LWP::Protocol::https</title>
<!-- Applied upstream in 6.11
<para>
First, apply a patch to use the system certificates (using the CPAN
automated install will instead use <ulink
@ -78,6 +81,7 @@
</para>
<screen><userinput>patch -Np1 -i ../LWP-Protocol-https-&LWP-Protocol-https-version;-system_certs-2.patch</userinput></screen>
-->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../../xincludes/perl-standard-install.xml"/>

4
general/prog/perl-modules/perl-test-differences.xml
View File

@ -5,7 +5,7 @@
%general-entities;
<!ENTITY my-download-http "&perl_authors;/id/D/DC/DCANTRELL/Test-Differences-&Test-Differences-version;.tar.gz">
<!ENTITY my-md5sum "53aa66b927e7ffe612118bec05f8343d">
<!ENTITY my-md5sum "1afd5ddab3d70575bdff206edacc4425">
]>
<!-- Begin Test::Differences -->
@ -45,7 +45,7 @@
<bridgehead renderas="sect5">Required</bridgehead>
<para role="required">
<xref linkend="perl-text-diff"/>,
<xref linkend="perl-text-diff"/>
</para>
<bridgehead renderas="sect5">Recommended (required for the test suite)</bridgehead>

4
general/prog/php.xml
View File

@ -6,8 +6,8 @@
<!ENTITY php-download-http "https://www.php.net/distributions/php-&php-version;.tar.xz">
<!ENTITY php-download-ftp " ">
<!ENTITY php-md5sum "e0b4a8b8e3c4d0891520424359c33127">
<!ENTITY php-size "11 MB">
<!ENTITY php-md5sum "6c28be716abf829779f009bc020a44fe">
<!ENTITY php-size "11.4 MB">
<!ENTITY php-buildsize "503 MB (with documentation)">
<!ENTITY php-time "1.5 SBU (with parallelism=4; add 1.6 SBU for tests)">
<!-- Tests were run for 8.0.1 at -j4, had two timeouts as well.

16
general/prog/python-modules.xml
View File

@ -114,11 +114,6 @@
<xref linkend="gi-docgen"/>
</para>
</listitem>
<listitem revision="sysv">
<para>
<xref linkend="Jinja2"/>
</para>
</listitem>
<listitem>
<para>
<xref linkend="libxml2py2"/>
@ -134,11 +129,6 @@
<xref linkend="Mako"/>
</para>
</listitem>
<listitem revision="sysv">
<para>
<xref linkend="MarkupSafe"/>
</para>
</listitem>
<listitem>
<para>
<xref linkend="numpy"/>
@ -286,9 +276,6 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/gi-docgen.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/jinja2.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/libxml2py2.xml"/>
@ -298,9 +285,6 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/mako.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/markupsafe.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="python-modules/numpy.xml"/>

8
general/prog/python-modules/cython.xml
View File

@ -7,7 +7,7 @@
<!ENTITY cython-download-http "https://github.com/cython/cython/releases/download/&cython-version;/Cython-&cython-version;.tar.gz">
<!ENTITY cython-download-ftp " ">
<!ENTITY cython-md5sum "&cython-md5sum;">
<!ENTITY cython-size "2.0 MB">
<!ENTITY cython-size "2.1 MB">
<!ENTITY cython-buildsize "67 MB">
<!ENTITY cython-time "0.5 SBU">
]>
@ -99,7 +99,11 @@
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>cygdb cython cythonize</seg>
<seg>
cygdb,
cython, and
cythonize
</seg>
<seg>None</seg>
<seg>
/usr/lib/python&python3-majorver;/site-packages/Cython,

2
general/prog/python-modules/gi-docgen.xml
View File

@ -72,9 +72,7 @@
<bridgehead renderas="sect5">Required</bridgehead>
<para role="required">
<xref linkend="markdown"/>,
<phrase revision="sysv"><xref linkend="MarkupSafe"/>,</phrase>
<xref linkend="pygments"/>,
<phrase revision="sysv"><xref linkend="Jinja2"/>,</phrase>
and <xref linkend="typogrify"/>
</para>

5
general/prog/python-modules/mako.xml
View File

@ -68,11 +68,6 @@
<bridgehead renderas="sect4">Mako Dependencies</bridgehead>
<bridgehead renderas="sect5" revision="sysv">Required</bridgehead>
<para role="required" revision="sysv">
<xref linkend="MarkupSafe"/>
</para>
<bridgehead renderas="sect5">Optional (for Testing)</bridgehead>
<para role="optional">
<xref linkend="pytest"/>

4
general/prog/python-modules/pyparsing.xml
View File

@ -71,7 +71,6 @@
<bridgehead renderas="sect5">Optional</bridgehead>
<para role="optional">
<phrase revision="sysv"><xref linkend="Jinja2"/> and</phrase>
<ulink url="https://pypi.org/project/railroad-diagrams/">
railroad-diagrams
</ulink> (also needed for tests)
@ -98,8 +97,7 @@
<screen role="root"><userinput>pip3 install --no-index --find-links dist --no-cache-dir --no-user pyparsing</userinput></screen>
<para>
Assuming <xref linkend="pytest"/> <phrase revision="systemd">is</phrase>
<phrase revision="sysv">and <xref linkend="Jinja2"/> are</phrase>
Assuming <xref linkend="pytest"/> is
installed, but the other optional dependency is not, the installation
can be tested with the following commands:
</para>

1
general/prog/python-modules/sphinx.xml
View File

@ -73,7 +73,6 @@
<xref linkend="babel"/>,
<xref linkend="docutils"/>,
<xref linkend="imagesize"/>,
<phrase revision="sysv"><xref linkend="Jinja2"/>,</phrase>
<xref linkend="packaging"/>,
<xref linkend="pygments"/>,
<xref linkend="requests"/>,

10
general/prog/python3.xml
View File

@ -73,13 +73,9 @@
<para>
The Python modules from LFS will also have to be reinstalled:
<ulink url="&lfs-root;/chapter08/flit-core.html">flit-core</ulink>,
<ulink url="&lfs-root;/chapter08/wheel.html">wheel</ulink>, and
<ulink url="&lfs-root;/chapter08/meson.html">meson</ulink>.
</para>
<para revision="systemd">
On systemd systems, it is also necessary to reinstall
<ulink url="&lfs-root;/chapter08/markupsafe.html">MarkupSafe</ulink>
<ulink url="&lfs-root;/chapter08/wheel.html">wheel</ulink>,
<ulink url="&lfs-root;/chapter08/meson.html">meson</ulink>,
<ulink url="&lfs-root;/chapter08/markupsafe.html">MarkupSafe</ulink>,
and <ulink url="&lfs-root;/chapter08/jinja2.html">Jinja2</ulink>.
</para>
</important>

8
general/prog/rust.xml
View File

@ -6,8 +6,8 @@
<!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.xz">
<!ENTITY rust-download-ftp " ">
<!ENTITY rust-md5sum "165792a4266021589b2d6061f208755f">
<!ENTITY rust-size "134 MB">
<!ENTITY rust-md5sum "81ae525767680c1680bad985ecc35bff">
<!ENTITY rust-size "145 MB">
<!ENTITY rust-buildsize "8.9 GB (289 MB installed); add 6.4 GB if running the tests">
<!ENTITY rust-time "6.7 SBU (including download time; add 6.2 SBU for tests, both using parallelism=8)">
]>
@ -356,7 +356,7 @@ python3 ./x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></sc
<!-- https://github.com/rust-lang/rust/issues/112209 -->
<para>
Three <literal>ui</literal> tests may fail (depending on the length
Two <literal>ui</literal> tests may fail (depending on the length
of absolute path of the
<filename class='directory'>rustc-&rust-version;-src</filename>
directory).
@ -398,8 +398,6 @@ python3 ./x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></sc
<screen remap="test"><userinput>grep '^test result:' rustc-testlog |
awk '{sum1 += $4; sum2 += $6} END { print sum1 " passed; " sum2 " failed" }'</userinput></screen>
<!-- For rustc-1.70.0, I got: 28494 passed; 14 failed. -bdubbs -->
<para>
The other available fields are $8 for those which were ignored
(i.e. skipped), $10 for 'measured' and $12 for 'filtered out' but both

6
general/prog/vala.xml
View File

@ -6,10 +6,10 @@
<!ENTITY vala-download-http "&gnome-download-http;/vala/&vala-major-version;/vala-&vala-version;.tar.xz">
<!ENTITY vala-download-ftp "&gnome-download-ftp;/vala/&vala-major-version;/vala-&vala-version;.tar.xz">
<!ENTITY vala-md5sum "73f8b53fd6f1282a903d38213811f6a0">
<!ENTITY vala-md5sum "fc0390c053cec6cd18bde18be8ade296">
<!ENTITY vala-size "3.8 MB">
<!ENTITY vala-buildsize "199 MB (add 18 MB for tests)">
<!ENTITY vala-time "0.5 SBU (add 1.1 SBU for tests; using parallelism=4)">
<!ENTITY vala-buildsize "156 MB (add 19 MB for tests)">
<!ENTITY vala-time "0.4 SBU (add 0.7 SBU for tests; both using parallelism=4)">
]>
<sect1 id="vala" xreflabel="Vala-&vala-version;">

4
general/sysutils/bluez.xml
View File

@ -6,9 +6,9 @@
<!ENTITY bluez-download-http "&kernel-dl;/linux/bluetooth/bluez-&bluez-version;.tar.xz">
<!ENTITY bluez-download-ftp " ">
<!ENTITY bluez-md5sum "3f9496fedf878fba985e56713ed7752e">
<!ENTITY bluez-md5sum "00a72fed12e706b2d8bb40786154d3aa">
<!ENTITY bluez-size "2.2 MB">
<!ENTITY bluez-buildsize "149 MB (with tests)">
<!ENTITY bluez-buildsize "158 MB (with tests)">
<!ENTITY bluez-time "0.4 SBU (using parallelism=4; with tests)">
]>

10
general/sysutils/dbus.xml
View File

@ -433,6 +433,16 @@ EOF</userinput></screen>
<screen role="root" revision="sysv"><userinput>make install-dbus</userinput></screen>
<para revision="sysv">
If this is the first time to install
<application>D-Bus</application> on the system and you are not
operating in a chroot environment, you can immediately start
<command>dbus-daemon</command> without rebooting the system:
</para>
<!-- nodump because maybe the user is building in chroot -->
<screen role="nodump" revision="sysv"><userinput>/etc/init.d/dbus start</userinput></screen>
<para revision="sysv">
Note that this boot script only starts the system-wide
<application>D-Bus</application> daemon. Each user requiring access to

20
general/sysutils/elogind.xml
View File

@ -75,11 +75,6 @@
<bridgehead renderas="sect3">elogind Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="Jinja2"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
<xref role="runtime" linkend="dbus"/> (runtime),
@ -170,7 +165,11 @@ ninja</userinput></screen>
<para>
To test the results, issue: <command>ninja test</command>. A few tests
are skipped if not run with <systemitem class="username">root</systemitem>
privileges.
privileges. Two tests named <filename>test-fs-util</filename> and
<filename>test-id128</filename> require the
<filename>/etc/machine-id</filename> symlink, so they will fail if
this symlink is not created following the instruction in
<xref linkend='dbus'/> yet.
</para>
<para>
@ -205,9 +204,12 @@ ln -sfvn elogind /usr/include/systemd</userinput></screen>
</para>
<para>
<parameter>-Dcgroup-controller=elogind</parameter>: This switch ensures
that <application>elogind</application> is selected as the cgroup
controller, even if booted with another running cgroup controller.
<parameter>-Dcgroup-controller=elogind</parameter>: This switch is
necessary to build this package when the kernel is not built with
<option>CONFIG_CGROUPS</option> enabled. Note that
<application>elogind</application> strictly needs
a kernel with <option>CONFIG_CGROUPS</option> enabled at runtime,
but this switch will allow building the package first.
</para>
<para>

12
general/sysutils/systemd.xml
View File

@ -224,12 +224,12 @@ ninja</userinput></screen>
</note>
<para>
To test the results, issue:
<command>PATH+=:/usr/sbin ninja test</command>.
<!-- One test named test-repart needs sfdisk, which is in /usr/sbin. -->
The test named <filename>test-stat-util</filename> is known to fail
if the support for some namespaces is not enabled in the kernel
configuration. If the test suite is ran as the &root; user, some
To test the results, issue: <command>ninja test</command>.
<!-- test-netlink: https://github.com/systemd/systemd/issues/27969 -->
The test named <filename>test-stat-util</filename> and
<filename>test-netlink</filename> are known to fail
if some kernel features are not enabled.
If the test suite is ran as the &root; user, some
other tests may fail because they depend on various kernel
configuration options.
</para>

20
general/sysutils/udisks2.xml
View File

@ -78,16 +78,6 @@
<xref linkend="polkit"/>
</para>
<bridgehead renderas="sect4">Required at runtime</bridgehead>
<para role="required">
<xref role="runtime" linkend="btrfs-progs"/>,
<phrase revision="sysv"><xref role="runtime" linkend="dbus"/>,</phrase>
<xref role="runtime" linkend="dosfstools"/>,
<xref role="runtime" linkend="gptfdisk"/>,
<xref role="runtime" linkend="mdadm"/>, and
<xref role="runtime" linkend="xfsprogs"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
<phrase revision="systemd"><xref role='runtime' linkend="systemd"/>
@ -111,6 +101,16 @@
<ulink url="https://github.com/sahlberg/libiscsi">libiscsi</ulink>
</para>
<bridgehead renderas="sect4">Optional Runtime Dependencies</bridgehead>
<para role="runtime">
<xref linkend="btrfs-progs"/>,
<phrase revision="sysv"><xref linkend="dbus"/>,</phrase>
<xref linkend="dosfstools"/>,
<xref linkend="gptfdisk"/>,
<xref linkend="mdadm"/>, and
<xref linkend="xfsprogs"/>
</para>
</sect2>
<sect2 role="installation">

13
general/sysutils/upower.xml
View File

@ -6,9 +6,9 @@
<!ENTITY upower-download-http "https://gitlab.freedesktop.org/upower/upower/-/archive/v&upower-version;/upower-v&upower-version;.tar.bz2">
<!ENTITY upower-download-ftp " ">
<!ENTITY upower-md5sum "4fba71838a9ba0db6f140418eddbe2b7">
<!ENTITY upower-size "128 KB">
<!ENTITY upower-buildsize "4.9 MB (add 1.3 MB for tests)">
<!ENTITY upower-md5sum "bfd6e3275e61d7e097b53eb2b216fffa">
<!ENTITY upower-size "136 KB">
<!ENTITY upower-buildsize "6.5 MB (add 1.1 MB for tests)">
<!ENTITY upower-time "less than 0.1 SBU (using parallelism=4, add 0.6 SBU for tests)">
]>
@ -153,10 +153,15 @@ ninja</userinput></screen>
<!-- On my system with LANG=zh_CN.UTF-8, one test attempted to compare
Chinese error message with English references and failed.
LC_ALL=C fixes the problem. -->
<!-- Headphone hotplug (bluetooth and AUX) was tested and seems to work
okay even with the test faliures. Maybe it's wants headphones plugged
in during the test? Regardless, it can be safely ignored. -->
<para>
To test the results, issue: <command>LC_ALL=C ninja test</command>. Some
checks may not pass due to missing files. Test suite should be run from
a local GUI session started with dbus-launch.
a local GUI session started with dbus-launch. 2 tests relating to the
headphone hotplug feature are known to fail, these can be safely ignored
as the headphone functionality does still work.
</para>
<para>

22
gnome.ent
View File

@ -49,9 +49,9 @@
<!ENTITY libgweather-minor "4.2">
<!ENTITY libgweather-version "&libgweather-minor;.0">
<!ENTITY libpeas-version "1.36.0">
<!ENTITY libshumate-version "1.0.3">
<!ENTITY libshumate-version "1.0.4">
<!ENTITY libwnck-version "43.0">
<!ENTITY evolution-data-server-version "3.48.3">
<!ENTITY evolution-data-server-version "3.48.4">
<!--<!ENTITY folks-version "0.15.5">-->
<!--<!ENTITY gfbgraph-version "0.2.5">-->
<!ENTITY tracker3-version "3.5.3">
@ -63,7 +63,7 @@
<!ENTITY dconf-version "0.40.0">
<!ENTITY dconf-editor-version "43.0">
<!ENTITY gnome-backgrounds-version "44.0">
<!ENTITY gvfs-version "1.50.4">
<!ENTITY gvfs-version "1.50.5">
<!ENTITY gexiv2-minor "0.14">
<!ENTITY gexiv2-version "&gexiv2-minor;.1">
<!ENTITY nautilus-version "44.2.1">
@ -71,14 +71,14 @@
<!ENTITY gnome-bluetooth-version "42.5">
<!ENTITY gnome-keyring-version "42.1">
<!ENTITY gnome-settings-daemon-version "44.1">
<!ENTITY gnome-control-center-version "44.2">
<!ENTITY mutter-version "44.2">
<!ENTITY gnome-shell-version "44.2">
<!ENTITY gnome-control-center-version "44.3">
<!ENTITY mutter-version "44.3">
<!ENTITY gnome-shell-version "44.3">
<!ENTITY gnome-shell-extensions-version "44.0">
<!ENTITY gnome-session-version "44.0">
<!-- GDM Moved to display managers -->
<!--<!ENTITY gdm-version "43.0">-->
<!ENTITY gnome-user-docs-version "44.1">
<!ENTITY gnome-user-docs-version "44.3">
<!-- Icons moved to packages.ent, since they're now in the Icons chapter.-->
<!ENTITY yelp-version "42.2">
<!-- notification-daemon moved to System Utilites, so it's now in packages.ent -->
@ -89,16 +89,16 @@
<!ENTITY baobab-version "44.0">
<!ENTITY brasero-version "3.12.3">
<!ENTITY cheese-version "44.0.1">
<!ENTITY eog-version "44.2">
<!ENTITY evince-version "44.2">
<!ENTITY evolution-version "3.48.3">
<!ENTITY eog-version "44.3">
<!ENTITY evince-version "44.3">
<!ENTITY evolution-version "3.48.4">
<!ENTITY file-roller-version "43.0">
<!-- gedit moved to Editors, so it's now in packages.ent -->
<!ENTITY gnome-calculator-version "44.0">
<!ENTITY gnome-color-manager-version "3.36.0">
<!ENTITY gnome-disk-utility-version "44.0">
<!ENTITY gnome-logs-version "43.0">
<!ENTITY gnome-maps-version "44.2">
<!ENTITY gnome-maps-version "44.3">
<!ENTITY gnome-nettool-version "42.0">
<!ENTITY gnome-power-manager-version "43.0">
<!ENTITY gnome-screenshot-version "41.0">

4
gnome/applications/eog.xml
View File

@ -6,9 +6,9 @@
<!ENTITY eog-download-http "&gnome-download-http;/eog/&gnome-44;/eog-&eog-version;.tar.xz">
<!ENTITY eog-download-ftp "&gnome-download-ftp;/eog/&gnome-44;/eog-&eog-version;.tar.xz">
<!ENTITY eog-md5sum "ed3b0c1da047ad96a14cb355de4a760a">
<!ENTITY eog-md5sum "1302bdb59bd4bfcceda2cbe8292b5fb6">
<!ENTITY eog-size "4.4 MB">
<!ENTITY eog-buildsize "31 MB">
<!ENTITY eog-buildsize "32 MB">
<!ENTITY eog-time "0.3 SBU">
]>

2
gnome/applications/evince.xml
View File

@ -8,7 +8,7 @@
"&gnome-download-http;/evince/&gnome-44;/evince-&evince-version;.tar.xz">
<!ENTITY evince-download-ftp
"&gnome-download-ftp;/evince/&gnome-44;/evince-&evince-version;.tar.xz">
<!ENTITY evince-md5sum "efba23224fba7f42bd9f1dc46a3b3652">
<!ENTITY evince-md5sum "a5ea6d19f083f41086ee363caefaa14f">
<!ENTITY evince-size "2.8 MB">
<!ENTITY evince-buildsize "59 MB">
<!ENTITY evince-time "0.4 SBU (Using parallelism=4)">

4
gnome/applications/evolution.xml
View File

@ -8,9 +8,9 @@
<!ENTITY evolution-download-http "&gnome-download-http;/evolution/&gnome-minor-48;/evolution-&evolution-version;.tar.xz">
<!ENTITY evolution-download-ftp "&gnome-download-ftp;/evolution/&gnome-minor-48;/evolution-&evolution-version;.tar.xz">
<!ENTITY evolution-md5sum "648c2049182c1d23d01fe423619692e4">
<!ENTITY evolution-md5sum "a41d0fdd6e818f7902a90d3b2e1777c0">
<!ENTITY evolution-size "13 MB">
<!ENTITY evolution-buildsize "372 MB">
<!ENTITY evolution-buildsize "291 MB">
<!ENTITY evolution-time "1.1 SBU (Using parallelism=4)">
]>

4
gnome/applications/gnome-maps.xml
View File

@ -8,9 +8,9 @@
"&gnome-download-http;/gnome-maps/&gnome-44;/gnome-maps-&gnome-maps-version;.tar.xz">
<!ENTITY gnome-maps-download-ftp
"&gnome-download-ftp;/gnome-maps/&gnome-44;/gnome-maps-&gnome-maps-version;.tar.xz">
<!ENTITY gnome-maps-md5sum "d15facc2bf4f2ed47d4775a79dadf03c">
<!ENTITY gnome-maps-md5sum "e08e44c46458b07eb7985176af162228">
<!ENTITY gnome-maps-size "2.2 MB">
<!ENTITY gnome-maps-buildsize "25 MB">
<!ENTITY gnome-maps-buildsize "15 MB">
<!ENTITY gnome-maps-time "less than 0.1 SBU">
]>

10
gnome/applications/seahorse.xml
View File

@ -85,7 +85,7 @@
<para role="recommended">
<xref linkend="libsoup3"/>,
<xref linkend="p11-kit"/>,
<xref linkend="openldap"/>,
<!-- <xref linkend="openldap"/>, picked up from gnupg2 -->
<xref linkend="openssh"/> (for managing SSH keys) and
<xref linkend="vala"/>
</para>
@ -147,14 +147,12 @@ ninja</userinput></screen>
<command>sed ... meson.build</command>: This command fixes building
with GnuPG-2.4 installed.
</para>
<!-- gnupg2 needs ldap anyway
<para>
<option>-Dldap-support=false</option>: Add this switch if you have not
installed openldap. <!--Note that you will have to use the following 'sed'
command to fix the build:
sed -i "448 s/g_list/if (ssrc) &amp;/" pgp/seahorse-pgp-backend.c-->
installed openldap.
</para>
-->
</sect2>
<sect2 role="content">

4
gnome/platform/evolution-data-server.xml
View File

@ -8,9 +8,9 @@
"&gnome-download-http;/evolution-data-server/&gnome-minor-48;/evolution-data-server-&evolution-data-server-version;.tar.xz">
<!ENTITY evolution-data-server-download-ftp
"&gnome-download-ftp;/evolution-data-server/&gnome-minor-48;/evolution-data-server-&evolution-data-server-version;.tar.xz">
<!ENTITY evolution-data-server-md5sum "f36517d8ec0bfdd925b820bb550042ff">
<!ENTITY evolution-data-server-md5sum "b387f584adf2318e958d7928925d1e37">
<!ENTITY evolution-data-server-size "4.7 MB">
<!ENTITY evolution-data-server-buildsize "174 MB (with tests)">
<!ENTITY evolution-data-server-buildsize "147 MB (with tests)">
<!ENTITY evolution-data-server-time "0.6 SBU (using parallelism=4, add 0.1 SBU for tests)">
]>

3
gnome/platform/gcr4.xml
View File

@ -101,7 +101,8 @@
<note>
<para>Both gcr-3 and gcr-4 are coinstallable. This version of the package is
used to support GTK-4 applications, such as
<xref linkend="gnome-shell" role="nodep"/>.</para>
<xref linkend="gnome-shell" role="nodep"/> and
<xref linkend="epiphany" role="nodep"/>.</para>
</note>
<para>

4
gnome/platform/gnome-control-center.xml
View File

@ -8,9 +8,9 @@
"&gnome-download-http;/gnome-control-center/&gnome-44;/gnome-control-center-&gnome-control-center-version;.tar.xz">
<!ENTITY gnome-control-center-download-ftp
"&gnome-download-ftp;/gnome-control-center/&gnome-44;/gnome-control-center-&gnome-control-center-version;.tar.xz">
<!ENTITY gnome-control-center-md5sum "90ec1d318853e0d34ac3b1e4919c8bc9">
<!ENTITY gnome-control-center-md5sum "a31987664414838a40b45ac485ee0375">
<!ENTITY gnome-control-center-size "7.3 MB">
<!ENTITY gnome-control-center-buildsize "116 MB (with tests)">
<!ENTITY gnome-control-center-buildsize "123 MB (with tests)">
<!ENTITY gnome-control-center-time "0.5 SBU (Using parallelism=4; with tests)">
]>

67
gnome/platform/gnome-shell.xml
View File

@ -8,12 +8,10 @@
"&gnome-download-http;/gnome-shell/&gnome-44;/gnome-shell-&gnome-shell-version;.tar.xz">
<!ENTITY gnome-shell-download-ftp
"&gnome-download-ftp;/gnome-shell/&gnome-44;/gnome-shell-&gnome-shell-version;.tar.xz">
<!ENTITY gnome-shell-md5sum "67e658e2d6ea77da6ebb62e33235b4dc">
<!ENTITY gnome-shell-md5sum "a73a7ba82782ad46378127a9a3acdec8">
<!ENTITY gnome-shell-size "1.9 MB">
<!ENTITY gnome-shell-buildsize "53 MB">
<!ENTITY gnome-shell-time "0.2 SBU (Using parallelism=4)">
<!ENTITY gnome-shell-buildsize-systemd "53 MB (with tests)">
<!ENTITY gnome-shell-time-systemd "0.2 SBU (Using parallelism=4; with tests)">
<!ENTITY gnome-shell-buildsize "61 MB (with tests)">
<!ENTITY gnome-shell-time "0.2 SBU (Using parallelism=4; with tests)">
]>
<sect1 id="gnome-shell" xreflabel="gnome-shell-&gnome-shell-version;">
@ -58,26 +56,16 @@
Download size: &gnome-shell-size;
</para>
</listitem>
<listitem revision='sysv'>
<listitem>
<para>
Estimated disk space required: &gnome-shell-buildsize;
</para>
</listitem>
<listitem revision='sysv'>
<listitem>
<para>
Estimated build time: &gnome-shell-time;
</para>
</listitem>
<listitem revision='systemd'>
<para>
Estimated disk space required: &gnome-shell-buildsize-systemd;
</para>
</listitem>
<listitem revision='systemd'>
<para>
Estimated build time: &gnome-shell-time-systemd;
</para>
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">GNOME Shell Dependencies</bridgehead>
@ -87,18 +75,12 @@
<xref linkend="evolution-data-server"/>,
<xref linkend="gcr4"/>,
<xref linkend="gjs"/>,
<xref role="runtime" linkend="gnome-control-center"/> (runtime),
<xref linkend="gnome-desktop"/>,
<xref linkend="ibus"/>,
<xref role="runtime" linkend="libgweather"/> (runtime),
<xref linkend="mutter"/>,
<xref linkend="polkit"/>,
<xref linkend="sassc"/>,
<xref linkend="startup-notification"/>, and
<phrase revision="sysv"><xref role='runtime' linkend="elogind"/>
(runtime)</phrase>
<phrase revision="systemd"><xref role='runtime' linkend="systemd"/>
(runtime)</phrase>
<xref linkend="sassc"/>, and
<xref linkend="startup-notification"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
@ -110,27 +92,36 @@
<xref linkend="NetworkManager"/>
</para>
<bridgehead renderas="sect4"
revision="sysv">Recommended (Runtime)</bridgehead>
<para role="recommended" revision="sysv">
<xref linkend="blocaled" role="runtime"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="gtk-doc"/> and
<ulink url="https://github.com/scop/bash-completion">bash-completion</ulink>
</para>
<bridgehead renderas="sect4">Runtime Dependencies</bridgehead>
<bridgehead renderas="sect4">Required Runtime Dependencies</bridgehead>
<para role="required">
<xref role="runtime" linkend="adwaita-icon-theme"/>,
<xref role="runtime" linkend="dconf"/>,
<phrase revision="sysv">
<xref role='runtime' linkend="elogind"/>,
</phrase>
<xref role="runtime" linkend="gdm"/>,
<xref role="runtime" linkend="gnome-backgrounds"/>, and
<xref role="runtime" linkend="gnome-backgrounds"/>,
<xref role="runtime" linkend="gnome-control-center"/>,
<xref role="runtime" linkend="libgweather"/>,
<phrase revision="sysv">and</phrase>
<phrase revision="systemd">
<xref role='runtime' linkend="systemd"/>, and
</phrase>
<xref role="runtime" linkend="telepathy-mission-control"/>
</para>
<bridgehead renderas="sect4"
revision="sysv">Recommended Runtime Dependency</bridgehead>
<para role="recommended" revision="sysv">
<xref linkend="blocaled" role="runtime"/>
</para>
</sect2>
<sect2 role="installation">
@ -160,19 +151,15 @@ meson setup --prefix=/usr \
.. &amp;&amp;
ninja</userinput></screen>
<para revision='sysv'>
This package does not come with a working test suite in a
SystemV environment.
</para>
<para revision='systemd'>
<para>
To test the results, you need to remove the
<parameter>-Dtests=false</parameter> switch, and to have <xref
linkend="mutter"/> compiled and installed with tests also.
To run the tests, issue: <command>ninja test</command>. You must be
running an X session to run the tests. Some will fail if <xref
linkend="gdm"/> is not installed.
linkend="gdm"/> is not installed. <phrase revision="sysv">Several
more tests may fail in the Sysv environment.</phrase>
</para>
<para>

6
gnome/platform/gnome-user-docs.xml
View File

@ -8,9 +8,9 @@
"&gnome-download-http;/gnome-user-docs/&gnome-44;/gnome-user-docs-&gnome-user-docs-version;.tar.xz">
<!ENTITY gnome-user-docs-download-ftp
"&gnome-download-ftp;/gnome-user-docs/&gnome-44;/gnome-user-docs-&gnome-user-docs-version;.tar.xz">
<!ENTITY gnome-user-docs-md5sum "0469b3fae941723634a42de407e82c38">
<!ENTITY gnome-user-docs-size "12 MB">
<!ENTITY gnome-user-docs-buildsize "250 MB">
<!ENTITY gnome-user-docs-md5sum "3ce76844f36edb364a4287218c85186a">
<!ENTITY gnome-user-docs-size "13 MB">
<!ENTITY gnome-user-docs-buildsize "161 MB">
<!ENTITY gnome-user-docs-time "0.5 SBU (using parallelism=4)">
]>

10
gnome/platform/gvfs.xml
View File

@ -6,9 +6,9 @@
<!ENTITY gvfs-download-http "&gnome-download-http;/gvfs/1.50/gvfs-&gvfs-version;.tar.xz">
<!ENTITY gvfs-download-ftp "&gnome-download-ftp;/gvfs/1.50/gvfs-&gvfs-version;.tar.xz">
<!ENTITY gvfs-md5sum "2a070704958ba5dab6098d51dda6a2ba">
<!ENTITY gvfs-md5sum "d0724181d20985a23c61d88e3a36a56e">
<!ENTITY gvfs-size "1.2 MB">
<!ENTITY gvfs-buildsize "42 MB">
<!ENTITY gvfs-buildsize "44 MB">
<!ENTITY gvfs-time "0.4 SBU (using parallelism=4)">
]>
@ -92,7 +92,6 @@
<xref linkend="gcr"/>,
<xref linkend="gtk3"/>,
<xref linkend="libcdio"/>,
<xref linkend="libgdata"/>,
<xref linkend="libgudev"/>,
<xref linkend="libsoup3"/>,
<phrase revision="sysv"><xref linkend="elogind"/>,</phrase>
@ -111,10 +110,12 @@
<xref linkend="gtk-doc"/>,
<xref linkend="libarchive"/>,
<xref linkend="libgcrypt"/>,
<xref linkend="libgdata"/>,
<xref linkend="libxml2"/>,
<xref linkend="libxslt"/>,
<xref linkend="openssh"/>,
<xref linkend="samba"/>,
<ulink url="&gnome-download-http;/gnome-desktop-testing/">gnome-desktop-testing</ulink> (for tests),
<ulink url="https://www.videolan.org/developers/libbluray.html">libbluray</ulink>,
<ulink url="http://www.gphoto.org/">libgphoto2</ulink>,
<ulink url="https://www.libimobiledevice.org/">libimobiledevice</ulink>,
@ -173,7 +174,8 @@ meson setup \
ninja</userinput></screen>
<para>
This package does not come with a test suite.
The test suite requires <application>gnome-desktop-testing</application>,
which is beyond the scope of BLFS.
</para>
<para>

32
gnome/platform/libshumate.xml
View File

@ -6,9 +6,9 @@
<!ENTITY libshumate-download-http "&gnome-download-http;/libshumate/1.0/libshumate-&libshumate-version;.tar.xz">
<!ENTITY libshumate-download-ftp "&gnome-download-ftp;/libshumate/1.0/libshumate-&libshumate-version;.tar.xz">
<!ENTITY libshumate-md5sum "965866eb1b2d0237d71294c68bf8ae05">
<!ENTITY libshumate-md5sum "3dd25880afc387163e1d50e575259ab3">
<!ENTITY libshumate-size "112 KB">
<!ENTITY libshumate-buildsize "5.3 MB">
<!ENTITY libshumate-buildsize "5.4 MB">
<!ENTITY libshumate-time "0.1 SBU">
]>
@ -73,10 +73,15 @@
<xref linkend="libsoup3"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
<xref linkend='gobject-introspection'/> (required for gnome-maps)
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="gi-docgen"/> and
<xref linkend="gtk-doc"/>
<xref linkend="gi-docgen"/>
<!-- and <xref linkend="gtk-doc"/> check but never used -->
</para>
</sect2>
@ -98,6 +103,15 @@ meson setup --prefix=/usr \
.. &amp;&amp;
ninja</userinput></screen>
<para>
If you have <xref linkend='gi-docgen'/> installed and wish to build
the API documentation for this package, issue:
</para>
<screen remap='doc'><userinput>sed 's/lib_version/version/' -i ../docs/meson.build &amp;&amp;
meson configure -Dgtk_doc=true &amp;&amp;
ninja</userinput></screen>
<para>
To test the results, issue: <command>ninja test</command>.
</para>
@ -114,13 +128,6 @@ ninja</userinput></screen>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../xincludes/meson-buildtype-release.xml"/>
<para>
<parameter>-Dgtk_doc=false</parameter>: This switch disables documentation
generation. Remove this if you have both <xref linkend="gtk-doc"/> and
<xref linkend="gi-docgen"/> installed and wish to generate the API
documentation.
</para>
</sect2>
<sect2 role="content">
@ -139,7 +146,8 @@ ninja</userinput></screen>
libshumate-1.0.so
</seg>
<seg>
/usr/include/shumate-1.0
/usr/include/shumate-1.0 and
/usr/share/doc/libshumate-&libshumate-version; (optional)
</seg>
</seglistitem>
</segmentedlist>

28
gnome/platform/mutter.xml
View File

@ -6,11 +6,10 @@
<!ENTITY mutter-download-http "&gnome-download-http;/mutter/&gnome-44;/mutter-&mutter-version;.tar.xz">
<!ENTITY mutter-download-ftp "&gnome-download-ftp;/mutter/&gnome-44;/mutter-&mutter-version;.tar.xz">
<!ENTITY mutter-md5sum "3bb532d0c15fe21bb7ea7ba7203ddd8e">
<!ENTITY mutter-size "150 MB">
<!ENTITY mutter-buildsize "75 MB (without tests)">
<!ENTITY mutter-time "0.5 SBU (Using parallelism=4)">
<!ENTITY mutter-time-systemd "0.5 SBU (Using parallelism=4, add 1.0 SBU for tests)">
<!ENTITY mutter-md5sum "c9a692911a8ff849c6bbfb44eca7a92f">
<!ENTITY mutter-size "2.7 MB">
<!ENTITY mutter-buildsize "99 MB (with tests)">
<!ENTITY mutter-time "0.8 SBU (Using parallelism=4; add 1.4 SBU for tests)">
]>
<sect1 id="mutter" xreflabel="Mutter-&mutter-version;">
@ -62,16 +61,11 @@
Estimated disk space required: &mutter-buildsize;
</para>
</listitem>
<listitem revision='sysv'>
<listitem>
<para>
Estimated build time: &mutter-time;
</para>
</listitem>
<listitem revision='systemd'>
<para>
Estimated build time: &mutter-time-systemd;
</para>
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">Mutter Dependencies</bridgehead>
@ -115,11 +109,11 @@
</para>
<!-- NOTE: Mutter compiles shipped Cogl and Clutter for it's own
internal use. This is because the upstream has decided that Cogl and
internal use. This is because upstream have decided that Cogl and
Clutter should be only used by Mutter in the future, so the development
of Cogl and Clutter is now performed in the Mutter repository. The
"standalone" Cogl and Clutter are considered obsolete now and we should
try to archive them. -->
"standalone" Cogl and Clutter are considered obsolete now and we have
archived them. -->
</sect2>
@ -211,8 +205,8 @@ ninja</userinput></screen>
<para>
The tests require an active X or wayland session.
<!-- https://gitlab.gnome.org/GNOME/mutter/-/issues/2848 -->
The <filename>test_framebuffer_get_bits</filename> test is known to fail.
A lot of tests will fail if the opengl rendering is not done in hardware.
The <filename>cogl-test-framebuffer-get-bits-gl3</filename> test is
known to fail. A few other tests may fail depending on the configuration.
Don't make any mouse or keyboard input while the test suite is
running or some tests may fail.
</para>
@ -239,7 +233,7 @@ ninja</userinput></screen>
</para>
<para>
<option>-Dtests=true -Dclutter-tests=false</option>: Building all the
<option>-Dtests=true -Dclutter_tests=false</option>: Building all the
tests but the tests for the shipped <application>Clutter</application>
library. The <application>Clutter</application> tests are known to
fail with <option>--buildtype=release</option>.

353
introduction/important/building-notes.xml
View File

@ -23,9 +23,9 @@
<para>While you can keep the source files anywhere you like, we assume that
you have unpacked the package and changed into the directory created by the
unpacking process (the 'build' directory). We also assume you have
uncompressed any required patches and they are in the directory immediately
above the 'build' directory.</para>
unpacking process (the source directory). We also assume you have
uncompressed any required patches and they are in the directory
immediately above the source directory.</para>
<para>We can not emphasize strongly enough that you should start from a
<emphasis>clean source tree</emphasis> each time. This means that if
@ -74,15 +74,21 @@ tar -xvf filename.tar.bz2</userinput></screen>
<screen><userinput>bzcat filename.tar.bz2 | tar -xv</userinput></screen>
<para>Finally, you sometimes need to be able to unpack patches which are
generally not in <filename class='extension'>.tar</filename> format. The
best way to do this is to copy the patch file to the parent of the 'build'
directory and then run one of the following commands depending on whether
the file is a <filename class='extension'>.gz</filename> or <filename
class='extension'>.bz2</filename> file:</para>
<para>
Finally, sometimes we have a compressed patch file in
<filename class='extension'>.patch.gz</filename> or
<filename class='extension'>.patch.bz2</filename> format.
The best way to apply the patch is piping the output of the
decompressor to the <command>patch</command> utility. For example:
</para>
<screen><userinput>gunzip -v patchname.gz
bunzip2 -v patchname.bz2</userinput></screen>
<screen><userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput></screen>
<para>
Or for a patch compressed with <command>bzip2</command>:
</para>
<screen><userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput></screen>
</sect2>
@ -217,18 +223,19 @@ bunzip2 -v patchname.bz2</userinput></screen>
<screen><userinput>ninja -j2</userinput></screen>
<para>
but for ninja, the default number of jobs is &lt;N&gt;+2, where &lt;N&gt;
is the number of processors available, so that using the above commands
is rather for limiting the number of jobs (see below for why this could
be necessary).
but for ninja, the default number of jobs is N + 2, if
the number of logical processors N is greater than 2; or N + 1 if
N is 1 or 2. The reason to use a number of jobs slightly greater
than the number of logical processors is keeping all logical
processors busy even if some jobs are performing I/O operatations.
</para>
<para>Generally the number of processes should not exceed the number of
cores supported by the CPU. To list the processors on your
cores supported by the CPU too much. To list the processors on your
system, issue: <userinput>grep processor /proc/cpuinfo</userinput>.
</para>
<para>In some cases, using multiple processes may result in a 'race'
<para>In some cases, using multiple processes may result in a race
condition where the success of the build depends on the order of the
commands run by the <command>make</command> program. For instance, if an
executable needs File A and File B, attempting to link the program before
@ -238,16 +245,16 @@ bunzip2 -v patchname.bz2</userinput></screen>
Makefile.</para>
<para>If this occurs, the best way to proceed is to drop back to a
single processor build. Adding '-j1' to a make command will override
the similar setting in the <envar>MAKEFLAGS</envar> environment
variable.</para>
single processor build. Adding <option>-j1</option> to a make command
will override the similar setting in the <envar>MAKEFLAGS</envar>
environment variable.</para>
<!-- outdated
<note><para>When running the package tests or the install portion of the
package build process, we do not recommend using an option greater than
'-j1' unless specified otherwise. The installation procedures or checks
have not been validated using parallel procedures and may fail with issues
that are difficult to debug.</para></note>
-->
<important>
<para>
Another problem may occur with modern CPU's, which have a lot of cores.
@ -292,7 +299,7 @@ bunzip2 -v patchname.bz2</userinput></screen>
scenario requires putting the desired responses in a file and using
redirection so that the program uses the data in the file as the answers to
the questions.</para>
<!-- outdated
<para>Building the <application>CUPS</application> package is a good
example of how redirecting a file as input to prompts can help you automate
the build. If you run the test suite, you are asked to respond to a series
@ -302,7 +309,7 @@ bunzip2 -v patchname.bz2</userinput></screen>
one shown below to automate running the test suite:</para>
<screen><userinput>make check &lt; ../cups-1.1.23-testsuite_parms</userinput></screen>
-->
<para>This effectively makes the test suite use the responses in the file
as the input to the questions. Occasionally you may end up doing a bit of
trial and error determining the exact format of your input file for some
@ -381,15 +388,15 @@ chmod 755 blfs-yes-test1</userinput></screen>
<para>Again, the easiest way to demonstrate the technique is to show an
example. First, issue the command:</para>
<screen><userinput>ls -l /usr/bin | more</userinput></screen>
<screen><userinput>ls -l /usr/bin | less</userinput></screen>
<para>Of course, you'll be required to view the output one page at a time
because the <command>more</command> filter was used. Now try the same
because the <command>less</command> filter was used. Now try the same
command, but this time redirect the output to a file. The special file
<filename>/dev/null</filename> can be used instead of the filename shown,
but you will have no log file to examine:</para>
<screen><userinput>ls -l /usr/bin | more &gt; redirect_test.log 2&gt;&amp;1</userinput></screen>
<screen><userinput>ls -l /usr/bin | less &gt; redirect_test.log 2&gt;&amp;1</userinput></screen>
<para>Notice that this time the command immediately returned to the shell
prompt without having to page through the output. You may now remove the
@ -406,7 +413,7 @@ chmod 755 blfs-yes-test1</userinput></screen>
<screen><userinput>cat &gt; blfs-yes-test2 &lt;&lt; "EOF"
<literal>#!/bin/bash
ls -l /usr/bin | more
ls -l /usr/bin | less
echo -n -e "\n\nDid you enjoy reading this? (y,n) "
@ -702,44 +709,55 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
options and their default values) differ. It may be easiest to understand
the issues caused by some choices (typically slow execution or
unexpected use of, or omission of, optimizatons) by starting with
the CFLAGS and CXXFLAGS environment variables. There are also some
programs which use rust.
the <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar>, and
<envar>LDFLAGS</envar> environment variables. There are also some
programs which use Rust.
</para>
<para>
Most LFS and BLFS builders are probably aware of the basics of CFLAGS
and CXXFLAGS for altering how a program is compiled. Typically, some
form of optimization is used by upstream developers (-O2 or -O3),
sometimes with the creation of debug symbols (-g), as defaults.
Most LFS and BLFS builders are probably aware of the basics of
<envar>CFLAGS</envar> and <envar>CXXFLAGS</envar> for altering how a
program is compiled. Typically, some form of optimization is used by
upstream developers (<option>-O2</option> or <option>-O3</option>),
sometimes with the creation of debug symbols (<option>-g</option>),
as defaults.
</para>
<para>
If there are contradictory flags (e.g. multiple different -O values),
If there are contradictory flags (e.g. multiple different
<option>-O</option> values),
the <emphasis>last</emphasis> value will be used. Sometimes this means
that flags specified in environment variables will be picked up before
values hardcoded in the Makefile, and therefore ignored. For example,
where a user specifies '-O2' and that is followed by '-O3' the build will
use '-O3'.
where a user specifies <option>-O2</option> and that is followed by
<option>-O3</option> the build will use <option>-O3</option>.
</para>
<para>
There are various other things which can be passed in CFLAGS or
CXXFLAGS, such as forcing compilation for a specific microarchitecture
(e.g. -march=amdfam10, -march=native) or specifying a specific standard
for C or C++ (-std=c++17 for example). But one thing which has now come
to light is that programmers might include debug assertions in their
code, expecting them to be disabled in releases by using -DNDEBUG.
Specifically, if <xref linkend="mesa"/> is built with these assertions
enabled, some activities such as loading levels of games can take
extremely long times, even on high-class video cards.
CXXFLAGS, such as allowing using the instruction set extensions
available with a specific microarchitecture (e.g.
<option>-march=amdfam10</option> or <option>-march=native</option>),
tune the generated code for a specific microarchitecture (e. g.
<option>-mtune=tigerlake</option> or <option>-mtune=native</option>,
if <option>-mtune=</option> is not used, the microarchitecture from
<option>-march=</option> setting will be used), or specifying a
specific standard for C or C++ (<option>-std=c++17</option> for
example). But one thing which has now come to light is that
programmers might include debug assertions in their code, expecting
them to be disabled in releases by using <option>-DNDEBUG</option>.
Specifically, if <xref linkend="mesa"/> is built with these
assertions enabled, some activities such as loading levels of games
can take extremely long times, even on high-class video cards.
</para>
<bridgehead renderas="sect3" id="autotools-info">Autotools with Make</bridgehead>
<para>
This combination is often described as 'CMMI' (configure, make, make
install) and is used here to also cover the few packages which have a
configure script that is not generated by autotools.
This combination is often described as <quote>CMMI</quote>
(configure, make, make install) and is used here to also cover
the few packages which have a configure script that is not
generated by autotools.
</para>
<para>
@ -759,23 +777,26 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
</para>
<para>
In most CMMI packages, running 'make' will list each command and run
it, interspersed with any warnings. But some packages try to be 'silent'
and only show which file they are compiling or linking instead of showing
the command line. If you need to inspect the command, either because of
an error, or just to see what options and flags are being used, adding
'V=1' to the make invocation may help.
In most CMMI packages, running <command>make</command> will list
each command and run it, interspersed with any warnings. But some
packages try to be <quote>silent</quote> and only show which file
they are compiling or linking instead of showing the command line.
If you need to inspect the command, either because of an error, or
just to see what options and flags are being used, adding
<option>V=1</option> to the make invocation may help.
</para>
<bridgehead renderas="sect3" id="cmake-info">CMake</bridgehead>
<para>
CMake works in a very different way, and it has two backends which can
be used on BLFS: 'make' and 'ninja'. The default backend is make, but
CMake works in a very different way, and it has two backends which
can be used on BLFS: <command>make</command> and
<command>ninja</command>. The default backend is make, but
ninja can be faster on large packages with multiple processors. To
use ninja, specify '-G Ninja' in the cmake command. However, there are
some packages which create fatal errors in their ninja files but build
successfully using the default of Unix Makefiles.
use ninja, specify <option>-G Ninja</option> in the cmake command.
However, there are some packages which create fatal errors in their
ninja files but build successfully using the default of Unix
Makefiles.
</para>
<para>
@ -788,12 +809,13 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
<para>
Perhaps the most-important thing about CMake is that it has a variety
of CMAKE_BUILD_TYPE values, and these affect the flags. The default
is that this is not set and no flags are generated. Any CFLAGS or
CXXFLAGS in the environment will be used. If the programmer has coded
any debug assertions, those will be enabled unless -DNDEBUG is used.
The following CMAKE_BUILD_TYPE values will generate the flags shown,
and these will come <emphasis>after</emphasis> any flags in the
environment and therefore take precedence.
is that this is not set and no flags are generated. Any
<envar>CFLAGS</envar> or <envar>CXXFLAGS</envar> in the environment
will be used. If the programmer has coded any debug assertions,
those will be enabled unless -DNDEBUG is used. The following
CMAKE_BUILD_TYPE values will generate the flags shown, and these
will come <emphasis>after</emphasis> any flags in the environment
and therefore take precedence.
</para>
<informaltable align="center">
@ -871,40 +893,42 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
<itemizedlist>
<listitem>
<para>plain : no added flags. This is for distributors to supply their
own CLFAGS, CXXFLAGS and LDFLAGS. There is no obvious reason to use
own <envar>CFLAGS</envar>, <envar>CXXFLAGS</envar> and
<envar>LDFLAGS</envar>. There is no obvious reason to use
this in BLFS.</para>
</listitem>
<listitem>
<para>debug : '-g' - this is the default if nothing is specified
in either <filename>meson.build</filename> or the command line.
However it results large and slow binaries, so we should override
it in BLFS.</para>
<para>debug : <option>-g</option> - this is the default if
nothing is specified in either <filename>meson.build</filename>
or the command line. However it results large and slow binaries,
so we should override it in BLFS.</para>
</listitem>
<listitem>
<para>debugoptimized : '-O2 -g' : this is the default specified in
<filename>meson.build</filename> of some packages.</para>
<para>debugoptimized : <option>-O2 -g</option> - this is the
default specified in <filename>meson.build</filename> of some
packages.</para>
</listitem>
<listitem>
<para>release : '-O3 -DNDEBUG' (but occasionally a package will force
-O2 here)</para>
<para>release : <option>-O3</option> (occasionally a package will
force <option>-O2</option> here) - this is the buildtype we use
for most packages with Meson build system in BLFS.</para>
</listitem>
</itemizedlist>
<!-- From https://mesonbuild.com/Builtin-options.html#core-options:
b_ndebug: Default value = false, Possible values are
true, false, if-release. Some packages sets it to if-release
so we mistakenly believed if-release had been the default. -->
<para>
Although the 'release' buildtype is described as enabling -DNDEBUG, and all
CMake Release builds pass that, it has so far only been observed (in
verbose builds) for <xref linkend="mesa"/>. That suggests that it might
only be used when there are debug assertions present.
</para>
<para>
The -DNDEBUG flag can also be provided by passing
<command>-Db_ndebug=true</command>.
The <option>-DNDEBUG</option> flag is implied by the release
buildtype for some packages (for example <xref linkend='mesa'/>).
It can also be provided explicitly by passing
<option>-Db_ndebug=true</option>.
</para>
<para>
To see the details of the commands which are being run in a package using
meson, use 'ninja -v'.
meson, use <command>ninja -v</command>.
</para>
<bridgehead renderas="sect3" id="rust-info">Rustc and Cargo</bridgehead>
@ -914,32 +938,43 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
which will query a server to check current versions of dependencies
and then download them as necessary. These packages are built using
<command>cargo --release</command>. In theory, you can manipulate the
RUSTFLAGS to change the optimize-level (default is 3, like -O3, e.g.
<literal>-Copt-level=3</literal>) or to force it to build for the
machine it is being compiled on, using
<literal>-Ctarget-cpu=native</literal> but in practice this seems to
RUSTFLAGS to change the optimize-level (default for
<option>--release</option> is 3, i. e.
<option>-Copt-level=3</option>, like <option>-O3</option>) or to
force it to build for the machine it is being compiled on, using
<option>-Ctarget-cpu=native</option> but in practice this seems to
make no significant difference.
</para>
<para>
If you find an interesting rustc program which is only provided as
unpackaged source, you should at least specify
<literal>RUSTFLAGS=-Copt-level=2</literal> otherwise it will do an
unoptimized compile with debug info and run <emphasis>much</emphasis>
slower.
If you are compiling a standalone Rust program (as an unpackaged
<filename class='extension'>.rs</filename> file) by running
<command>rustc</command> directly, you should specify
<option>-O</option> (the abbreviation of
<option>-Copt-level=2</option>) or <option>-Copt-level=3</option>
otherwise it will do an unoptimized compile and run
<emphasis>much</emphasis> slower. If are compiling the program
for debugging it, replace the <option>-O</option> or
<option>-Copt-level=</option> options with <option>-g</option> to
produce an unoptimized program with debug info.
</para>
<para>
The rust developers seem to assume that everyone will compile on a
machine dedicated to producing builds, so by default all CPUs are used.
This can often be worked around, either by exporting
CARGO_BUILD_JOBS=&lt;N&gt; or passing --jobs &lt;N&gt; to cargo. For
compiling rustc itself, specifying --jobs &lt;N&gt; on invocations of
x.py (together with the <envar>CARGO_BUILD_JOBS</envar> environment
variable, which looks like a "belt and braces" approach but seems to be
necessary) mostly works. The exception is running the tests when building
rustc, some of them will nevertheless use all online CPUs, at least as of
rustc-1.42.0.
Like <command>ninja</command>, by default <command>cargo</command>
uses all logical processors. This can often be worked around,
either by exporting
<envar>CARGO_BUILD_JOBS=<replaceable>&lt;N&gt;</replaceable></envar>
or passing
<option>--jobs <replaceable>&lt;N&gt;</replaceable></option> to
<command>cargo</command>.
For compiling rustc itself, specifying
<option>--jobs <replaceable>&lt;N&gt;</replaceable></option> for
invocations of <command>x.py</command>
(together with the <envar>CARGO_BUILD_JOBS</envar> environment
variable, which looks like a <quote>belt and braces</quote>
approach but seems to be necessary) mostly works. The exception is
running the tests when building rustc, some of them will
nevertheless use all online CPUs, at least as of rustc-1.42.0.
</para>
</sect2>
@ -949,38 +984,73 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
<para>
Many people will prefer to optimize compiles as they see fit, by providing
CFLAGS or CXXFLAGS. For an introduction to the options available with gcc
and g++ see <ulink
url="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html"/> and <ulink
url="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html"/>
and <command>info gcc</command>.
<envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>. For an
introduction to the options available with gcc and g++ see <ulink
url="https://gcc.gnu.org/onlinedocs/gcc-&gcc-version;/gcc/Optimize-Options.html"/>.
The same content can be also found in <command>info gcc</command>.
</para>
<para>
Some packages default to '-O2 -g', others to '-O3 -g', and if CFLAGS or
CXXFLAGS are supplied they might be added to the package's defaults,
replace the package's defaults, or even be ignored. There are details
on some desktop packages which were mostly current in April 2019 at
Some packages default to <option>-O2 -g</option>, others to
<option>-O3 -g</option>, and if <envar>CFLAGS</envar> or
<envar>CXXFLAGS</envar> are supplied they might be added to the
package's defaults, replace the package's defaults, or even be
ignored. There are details on some desktop packages which were
mostly current in April 2019 at
<ulink url="https://www.linuxfromscratch.org/~ken/tuning/"/> - in
particular, README.txt, tuning-1-packages-and-notes.txt, and
tuning-notes-2B.txt. The particular thing to remember is that if you
want to try some of the more interesting flags you may need to force
verbose builds to confirm what is being used.
particular, <filename>README.txt</filename>,
<filename>tuning-1-packages-and-notes.txt</filename>, and
<filename>tuning-notes-2B.txt</filename>. The particular thing to
remember is that if you want to try some of the more interesting
flags you may need to force verbose builds to confirm what is being
used.
</para>
<para>
Clearly, if you are optimizing your own program you can spend time to
profile it and perhaps recode some of it if it is too slow. But for
building a whole system that approach is impractical. In general,
-O3 usually produces faster programs than -O2. Specifying
-march=native is also beneficial, but means that you cannot move the
binaries to an incompatible machine - this can also apply to newer
machines, not just to older machines. For example programs compiled for
'amdfam10' run on old Phenoms, Kaveris, and Ryzens : but programs
compiled for a Kaveri will not run on a Ryzen because certain op-codes
are not present. Similarly, if you build for a Haswell not everything
will run on a SandyBridge.
<option>-O3</option> usually produces faster programs than
<option>-O2</option>. Specifying
<option>-march=native</option> is also beneficial, but means that
you cannot move the binaries to an incompatible machine - this can
also apply to newer machines, not just to older machines. For
example programs compiled for <literal>amdfam10</literal> run on
old Phenoms, Kaveris, and Ryzens : but programs compiled for a
Kaveri will not run on a Ryzen because certain op-codes are not
present. Similarly, if you build for a Haswell not everything will
run on a SandyBridge.
</para>
<note>
<para>
Be careful that the name of a <option>-march</option> setting
does not always match the baseline of the microarchitecture
with the same name. For example, the Skylake-based Intel Celeron
processors do not support AVX at all, but
<option>-march=skylake</option> assumes AVX and even AVX2.
</para>
</note>
<para>
When a shared library is built by GCC, a feature named
<quote>semantic interposition</quote> is enabled by default. When
the shared library refers to a symbol name with external linkage
and default visbility, if the symbol exists in both the shared
library and the main executable, semantic interposition guarantees
the symbol in the main executable is always used. This feature
was invented in an attempt to make the behavior of linking a shared
library and linking a static library as similar as possible. Today
only a small number of packages still depend on semantic
interposition, but the feature is still on by the default of GCC,
causing many optimizations disabled for shared libraries because
they conflict with semantic interposition. The
<option>-fno-semantic-interposition</option> option can be passed
to <command>gcc</command> or <command>g++</command> to disable
semantic interposition and enable more optimizations for shared
libraries. This option is used as the default of some packages
(for example <xref linkend='python3'/>), and it's also the default
of Clang.
</para>
<para>
@ -991,8 +1061,37 @@ chmod 744 /usr/sbin/strip-all.sh</userinput></screen>
<para>
If building Perl or Python modules, or Qt packages which use qmake,
in general the CFLAGS and CXXFLAGS used are those which were used by
those 'parent' packages.
in general the <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>
used are those which were used by those <quote>parent</quote>
packages.
</para>
<para>
For <envar>LDFLAGS</envar>, there are two options can be used
for optimization. With <option>-Wl,-O1</option>, the linker will
optimize the hash table to speed up the dynamic linking. And with
<option>-Wl,--as-needed</option>, the linker will disregard
unnecessary <option>-l<replaceable>foo</replaceable></option> options
from the command line, i. e. the shared library <systemitem
class='library'>lib<replaceable>foo</replaceable></systemitem>
will only be linked if a symbol in <systemitem
class='library'>lib<replaceable>foo</replaceable></systemitem> is
really referred from the executable or shared library being linked.
This can sometimes mitigate the <quote>excessive dependencies to
shared librarues</quote> issues caused by
<application>libtool</application>. Note that the
<option>-Wl,</option> prefix is necessary because despite the
variable is named <envar>LDFLAGS</envar>, its content is actually
passed to <command>gcc</command> (or <command>g++</command>,
<command>clang</command>, etc.) during the link stage, not directly
passed to <command>ld</command>.
</para>
<para>
Note that <option>-Wl,-O1</option> is completely unrelated to the
compiler optimization flag <option>-O1</option>. Some packages are
using <option>-Wl,-O1</option> and <option>-Wl,--as-needed</option>
as the default in their building systems.
</para>
</sect2>

337
introduction/welcome/changelog.xml
View File

@ -38,10 +38,347 @@
</itemizedlist>
</listitem>
-->
<listitem>
<para>July 17th, 2023</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Update to liblinear-247. Fixes
<ulink url="&blfs-ticket-root;18281">#18281</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libbytesize-2.9. Fixes
<ulink url="&blfs-ticket-root;18259">#18259</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libblockdev-3.0.1. Fixes
<ulink url="&blfs-ticket-root;18256">#18256</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to gnupg-2.4.3. Fixes
<ulink url="&blfs-ticket-root;18250">#18250</ulink>.</para>
</listitem>
<listitem>
<para>[xry111] - Archive xf86-video-*. Fixes
<ulink url="&blfs-ticket-root;18267">#18267</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to LMDB_0.9.31. Fixes
<ulink url="&blfs-ticket-root;18290">#18290</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to qpdf-11.5.0. Fixes
<ulink url="&blfs-ticket-root;18282">#18282</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to harfbuzz-8.0.1. Fixes
<ulink url="&blfs-ticket-root;18278">#18278</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to xapian-core-1.4.23. Fixes
<ulink url="&blfs-ticket-root;18270">#18270</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to exempi-2.6.4. Fixes
<ulink url="&blfs-ticket-root;18269">#18269</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 15th, 2023</para>
<itemizedlist>
<listitem>
<para>[xry111] - Update to rustc-1.71.0. Fixes
<ulink url="&blfs-ticket-root;18297">#18297</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 12th, 2023</para>
<itemizedlist>
<listitem>
<para>[timtas] - Update to thunderbird-115.0. Fixes
<ulink url="&blfs-ticket-root;18275">#18275</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to mercurial-6.5. Fixes
<ulink url="&blfs-ticket-root;18261">#18261</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to glib-2.76.4. Fixes
<ulink url="&blfs-ticket-root;18291">#18291</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to sudo-1.9.14p1. Fixes
<ulink url="&blfs-ticket-root;18289">#18289</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to graphviz-8.1.0. Fixes
<ulink url="&blfs-ticket-root;18271">#18271</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to gpgme-1.21.0. Fixes
<ulink url="&blfs-ticket-root;18268">#18268</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to pipewire-0.3.74. Fixes
<ulink url="&blfs-ticket-root;18264">#18264</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to inih-57. Fixes
<ulink url="&blfs-ticket-root;18260">#18260</ulink>.</para>
</listitem>
<listitem>
<para>[ken] - Update to firefox-115.0.2esr (Security fix). Fixes
<ulink url="&blfs-ticket-root;18276">#18276</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 11th, 2023</para>
<itemizedlist>
<listitem>
<para>[renodr] - Update to libgudev-238. Fixes
<ulink url="&blfs-ticket-root;18287">#18287</ulink>.</para>
</listitem>
<listitem>
<para>[rahul] - Update to upower-1.90.2. Fixes
<ulink url="&blfs-ticket-root;18251">#18251</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to qemu-8.0.3. Fixes
<ulink url="&blfs-ticket-root;18277">#18277</ulink>.</para>
</listitem>
<listitem>
<para>[rahul] - Update to libshumate-1.0.4. Fixes
<ulink url="&blfs-ticket-root;18284">#18284</ulink>.</para>
</listitem>
<listitem>
<para>[timtas] - Update to openldap-2.6.5. Fixes
<ulink url="&blfs-ticket-root;18285">#18285</ulink>.</para>
</listitem>
<listitem>
<para>[thomas] - Update to xterm-384. Fixes
<ulink url="&blfs-ticket-root;18286">#18286</ulink>.</para>
</listitem>
<listitem>
<para>[thomas] - Update to php-8.2.8. Fixes
<ulink url="&blfs-ticket-root;18262">#18262</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 10th, 2023</para>
<itemizedlist>
<listitem>
<para>[renodr] - Update to LWP-Protocol-https-6.11 (Perl Module,
Security Update). Fixes
<ulink url="&blfs-ticket-root;18283">#18283</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to Test-Differences-0.70 (Perl Module). Fixes
<ulink url="&blfs-ticket-root;18272">#18272</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to numpy-1.25.1 (Python Module). Fixes
<ulink url="&blfs-ticket-root;18279">#18279</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to lxml-4.9.3 (Python Module). Fixes
<ulink url="&blfs-ticket-root;18253">#18253</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to Cython-0.29.36 (Python Module). Fixes
<ulink url="&blfs-ticket-root;18252">#18252</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 9th, 2023</para>
<itemizedlist>
<listitem>
<para>[pierre] - Update to mutter-44.3. Fixes
<ulink url="&blfs-ticket-root;18274">#18274</ulink>.</para>
</listitem>
<listitem>
<para>[pierre] - Update to gnome-shell-44.3. Fixes
<ulink url="&blfs-ticket-root;18273">#18273</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 8th, 2023</para>
<itemizedlist>
<listitem>
<para>[thomas] - Add ISC-Kea DHCP Server 2.4.0 (and its dependency
log4cplus) which is the successor of the ISC dhcpd. Fixes
<ulink url="&blfs-ticket-root;18160">#18160</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 6th, 2023</para>
<itemizedlist>
<listitem>
<para>[renodr] - Update to gnome-maps-44.3. Fixes
<ulink url="&blfs-ticket-root;18239">#18239</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to evince-44.3. Fixes
<ulink url="&blfs-ticket-root;18238">#18238</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to eog-44.3. Fixes
<ulink url="&blfs-ticket-root;18237">#18237</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to gnome-user-docs-44.3. Fixes
<ulink url="&blfs-ticket-root;18236">#18236</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to gvfs-1.50.5. Fixes
<ulink url="&blfs-ticket-root;18235">#18235</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to evolution and evolution-data-server 3.48.4.
Fixes <ulink url="&blfs-ticket-root;18232">#18232</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to epiphany-44.4. Fixes
<ulink url="&blfs-ticket-root;18228">#18228</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to gnome-control-center-44.3. Fixes
<ulink url="&blfs-ticket-root;18227">#18227</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to tepl-6.6.0. Fixes
<ulink url="&blfs-ticket-root;18226">#18226</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to opencv-4.8.0. Fixes
<ulink url="&blfs-ticket-root;18213">#18213</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to gstreamer and plugins 1.22.4 (Security
Update). Fixes
<ulink url="&blfs-ticket-root;18190">#18190</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Update to jdk-20.0.1 (Security Update). Fixes
<ulink url="&blfs-ticket-root;18192">#18192</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 5th, 2023</para>
<itemizedlist>
<listitem>
<para>[renodr] - Update to intel-media-driver-23.2.4. Fixes
<ulink url="&blfs-ticket-root;18254">#18254</ulink>.</para>
</listitem>
<listitem>
<para>[ken] - Update to ImageMagick-7.1.1-12 (Security fix). Fixes
<ulink url="&blfs-ticket-root;18204">#18204</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 4th, 2023</para>
<itemizedlist>
<listitem>
<para>[ken] - Update to JS-102.13.0 (Security fix). Fixes
<ulink url="&blfs-ticket-root;18248">#18248</ulink>.</para>
</listitem>
<listitem>
<para>[ken] - Update to firefox-115.0esr (Security fix). Fixes
<ulink url="&blfs-ticket-root;18220">#18220</ulink>. Please
read that ticket or the Editor Notes for information on minimum
dependencies if updating older systems.</para>
</listitem>
<listitem>
<para>[timtas] - Update to xfce4-settings-4.18.3. Fixes
<ulink url="&blfs-ticket-root;18249">#18249</ulink>.</para>
</listitem>
<listitem>
<para>[renodr] - Fix building xfsprogs-6.3.0 with gettext-0.22.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to wayland-protocols-1.32. Fixes
<ulink url="&blfs-ticket-root;18247">#18247</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libqalculate-4.7.0. Fixes
<ulink url="&blfs-ticket-root;18246">#18246</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to vala-0.56.9. Fixes
<ulink url="&blfs-ticket-root;18245">#18245</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to poppler-23.07.0. Fixes
<ulink url="&blfs-ticket-root;18244">#18244</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libjpeg-turbo-3.0.0. Fixes
<ulink url="&blfs-ticket-root;18243">#18243</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 3rd, 2023</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Update to taglib-1.13.1. Fixes
<ulink url="&blfs-ticket-root;18234">#18234</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to SDL2-2.28.1. Fixes
<ulink url="&blfs-ticket-root;18233">#18233</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to bluez-5.68. Fixes
<ulink url="&blfs-ticket-root;18229">#18229</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libuv-v1.46.0. Fixes
<ulink url="&blfs-ticket-root;18225">#18225</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to libpaper-2.1.1. Fixes
<ulink url="&blfs-ticket-root;18224">#18224</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to p11-kit-0.25.0. Fixes
<ulink url="&blfs-ticket-root;18219">#18219</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to glib-networking-2.76.1. Fixes
<ulink url="&blfs-ticket-root;18217">#18217</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to NetworkManager-1.42.8. Fixes
<ulink url="&blfs-ticket-root;18215">#18215</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>July 1st, 2023</para>
<itemizedlist>
<listitem>
<para>[xry111] - Update to librsvg-2.56.2. Fixes
<ulink url="&blfs-ticket-root;18231">#18231</ulink>.</para>
</listitem>
<listitem>
<para>[timtas] - Update to nss-3.91. Fixes
<ulink url="&blfs-ticket-root;18218">#18218</ulink>.</para>

1
kde/kf5/kf5-frameworks.xml
View File

@ -127,7 +127,6 @@
<xref role="runtime" linkend="doxygen"/> (Run time),
<xref linkend="doxypypy"/>,
<xref linkend="doxyqml"/>,
<phrase revision="sysv"><xref linkend="Jinja2"/>,</phrase>
<xref linkend="PyYAML"/>, and
<xref linkend="requests"/>
</para>

6
multimedia/libdriv/alsa-tools.xml
View File

@ -413,7 +413,7 @@ unset tool tool_dir</userinput></screen>
is a helper program to load the firmware binaries onto the
Digigram's miXart board sound drivers. The following modules
require this program: snd-mixart. These drivers don't work
properly at all until the certain firmwares are loaded, i.e. no
properly at all until the certain firmware files are loaded, i.e. no
PCM nor mixer devices will appear
</para>
<indexterm zone="alsa-tools mixartloader">
@ -429,7 +429,7 @@ unset tool tool_dir</userinput></screen>
is a helper program to load the firmware binaries onto
Digigram's pcxhr compatible board sound drivers. The following
modules require this program: snd-pcxhr. These drivers don't work
properly at all until certain firmwares are loaded, i.e. no PCM
properly at all until certain firmware files are loaded, i.e. no PCM
nor mixer devices will appear
</para>
<indexterm zone="alsa-tools pcxhrloader">
@ -511,7 +511,7 @@ unset tool tool_dir</userinput></screen>
Digigram's VX-board sound drivers. The following modules require
this program:
snd-vx222, snd-vxpocket, snd-vxp440. These drivers don't work properly at all
until the certain firmwares are loaded, i.e. no PCM nor mixer devices will
until the certain firmware files are loaded, i.e. no PCM nor mixer devices will
appear
</para>
<indexterm zone="alsa-tools vxloader">

2
multimedia/libdriv/gst10-libav.xml
View File

@ -6,7 +6,7 @@
<!ENTITY gst10-libav-download-http "&gstreamer-dl;/gst-libav/gst-libav-&gst10-libav-version;.tar.xz">
<!ENTITY gst10-libav-download-ftp " ">
<!ENTITY gst10-libav-md5sum "966b30ec0c974d8c475fb0eac1e875d2">
<!ENTITY gst10-libav-md5sum "b6cdc8d1580df63f4dd3ac6dc1eb0e85">
<!ENTITY gst10-libav-size "196 KB">
<!ENTITY gst10-libav-buildsize "14 MB">
<!ENTITY gst10-libav-time "less than 0.1 SBU">

6
multimedia/libdriv/gst10-plugins-bad.xml
View File

@ -7,10 +7,10 @@
<!ENTITY gst10-plugins-bad-download-http
"&gstreamer-dl;/gst-plugins-bad/gst-plugins-bad-&gst10-plugins-bad-version;.tar.xz">
<!ENTITY gst10-plugins-bad-download-ftp " ">
<!ENTITY gst10-plugins-bad-md5sum "dba9e49be289f9820c29edb74733db94">
<!ENTITY gst10-plugins-bad-md5sum "1fc0788308eeaa9f3af8c69c9577caa8">
<!ENTITY gst10-plugins-bad-size "5.3 MB">
<!ENTITY gst10-plugins-bad-buildsize "165 MB (with tests)">
<!ENTITY gst10-plugins-bad-time "1.0 SBU (Using parallelism=4; with tests)">
<!ENTITY gst10-plugins-bad-buildsize "214 MB (with tests)">
<!ENTITY gst10-plugins-bad-time "0.98 SBU (Using parallelism=4; with tests)">
]>
<sect1 id="gst10-plugins-bad" xreflabel="gst-plugins-bad-&gst10-plugins-bad-version;">

6
multimedia/libdriv/gst10-plugins-base.xml
View File

@ -7,9 +7,9 @@
<!ENTITY gst10-plugins-base-download-http
"&gstreamer-dl;/gst-plugins-base/gst-plugins-base-&gst10-plugins-base-version;.tar.xz">
<!ENTITY gst10-plugins-base-download-ftp " ">
<!ENTITY gst10-plugins-base-md5sum "14648e9e8f1fa0e7a45e47c51541d31f">
<!ENTITY gst10-plugins-base-size "2.2 MB">
<!ENTITY gst10-plugins-base-buildsize "87 MB (with tests)">
<!ENTITY gst10-plugins-base-md5sum "7d495970b0b7078c50d064d228b8d93f">
<!ENTITY gst10-plugins-base-size "2.3 MB">
<!ENTITY gst10-plugins-base-buildsize "95 MB (with tests)">
<!ENTITY gst10-plugins-base-time "0.7 SBU (Using parallelism=4; with tests)">
]>

7
multimedia/libdriv/gst10-plugins-good.xml
View File

@ -7,7 +7,7 @@
<!ENTITY gst10-plugins-good-download-http
"&gstreamer-dl;/gst-plugins-good/gst-plugins-good-&gst10-plugins-good-version;.tar.xz">
<!ENTITY gst10-plugins-good-download-ftp " ">
<!ENTITY gst10-plugins-good-md5sum "98e104f96ddf9de91528ac73f028a76f">
<!ENTITY gst10-plugins-good-md5sum "6d8134ee72fd3e0fd5d92640e149721f">
<!ENTITY gst10-plugins-good-size "2.7 MB">
<!ENTITY gst10-plugins-good-buildsize "108 MB (with tests)">
<!ENTITY gst10-plugins-good-time "0.6 SBU (Using parallelism=4; with tests)">
@ -158,8 +158,9 @@ ninja</userinput></screen>
<para>
To test the results, issue: <command>ninja test</command>.
One test, <filename>generic_states</filename>
is known to fail on some systems.
Two tests, <filename>generic_states</filename> and
<filename>elements_flvmux</filename>,
are known to fail on some systems.
</para>
<para>

2
multimedia/libdriv/gst10-plugins-ugly.xml
View File

@ -7,7 +7,7 @@
<!ENTITY gst10-plugins-ugly-download-http
"&gstreamer-dl;/gst-plugins-ugly/gst-plugins-ugly-&gst10-plugins-ugly-version;.tar.xz">
<!ENTITY gst10-plugins-ugly-download-ftp " ">
<!ENTITY gst10-plugins-ugly-md5sum "b46e249b4404773d5470adcdac92c51f">
<!ENTITY gst10-plugins-ugly-md5sum "2beed209d131fb4b997183b11ced9fce">
<!ENTITY gst10-plugins-ugly-size "244 KB">
<!ENTITY gst10-plugins-ugly-buildsize "8.9 MB (with tests)">
<!ENTITY gst10-plugins-ugly-time "less than 0.1 SBU (with tests)">

4
multimedia/libdriv/gstreamer10-vaapi.xml
View File

@ -6,8 +6,8 @@
<!ENTITY gstreamer10-vaapi-download-http "&gstreamer-dl;/gstreamer-vaapi/gstreamer-vaapi-&gstreamer-vaapi-version;.tar.xz">
<!ENTITY gstreamer10-vaapi-download-ftp " ">
<!ENTITY gstreamer10-vaapi-md5sum "06a42d60ece0b78e89c2316f9176544e">
<!ENTITY gstreamer10-vaapi-size "524 KB">
<!ENTITY gstreamer10-vaapi-md5sum "5521a495f1f3de5be8f3abb1c37b80a1">
<!ENTITY gstreamer10-vaapi-size "536 KB">
<!ENTITY gstreamer10-vaapi-buildsize "13 MB">
<!ENTITY gstreamer10-vaapi-time "0.2 SBU">
]>

4
multimedia/libdriv/gstreamer10.xml
View File

@ -6,9 +6,9 @@
<!ENTITY gstreamer10-download-http "&gstreamer-dl;/gstreamer/gstreamer-&gstreamer10-version;.tar.xz">
<!ENTITY gstreamer10-download-ftp " ">
<!ENTITY gstreamer10-md5sum "f812605a25fd38a7a36ee4a2d7a0ce28">
<!ENTITY gstreamer10-md5sum "04e1a3ce2a5b107b67892a7c7de5b326">
<!ENTITY gstreamer10-size "1.7 MB">
<!ENTITY gstreamer10-buildsize "46 MB (with tests)">
<!ENTITY gstreamer10-buildsize "48 MB (with tests)">
<!ENTITY gstreamer10-time "0.3 SBU (Using parallelism=4; with tests)">
]>

61
x/installing/intel-media-driver.xml → multimedia/libdriv/intel-media-driver.xml
View File

@ -4,22 +4,23 @@
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY intel-media-driver-version "23.2.3">
<!ENTITY intel-media-driver-version "23.2.4">
<!ENTITY intel-media-driver-download-http "https://github.com/intel/media-driver/archive/refs/tags/intel-media-&intel-media-driver-version;.tar.gz">
<!ENTITY intel-media-driver-download-ftp " ">
<!ENTITY intel-media-driver-md5sum "0fe79c9b7a44302b628c5af082860978">
<!ENTITY intel-media-driver-md5sum "68ded8a286c01c1c70fd73925279d12b">
<!ENTITY intel-media-driver-size "27 MB">
<!ENTITY intel-media-driver-buildsize "2.3 GB (390 MB installed)">
<!ENTITY intel-media-driver-buildsize "2.4 GB (358 MB installed)">
<!ENTITY intel-media-driver-time "10 SBU (with parallelism=4)">
]>
<sect2 id="intel-media-driver" xreflabel="intel-media-driver-&intel-media-driver-version;">
<sect1 id="intel-media-driver" xreflabel="intel-media-driver-&intel-media-driver-version;">
<?dbhtml filename="intel-media-driver.html"?>
<sect2info>
<sect1info>
<date>$Date$</date>
</sect2info>
</sect1info>
<title>intel-media-driver-&intel-media-driver-version;</title>
@ -27,7 +28,7 @@
<primary sortas="a-intel-media-driver">intel-media-driver</primary>
</indexterm>
<sect3 role="package">
<sect2 role="package">
<title>Introduction to intel-media-driver</title>
<para>
@ -38,7 +39,7 @@
&lfs113_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -72,7 +73,8 @@
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
<!--
<bridgehead renderas="sect2">Additional Downloads</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -81,6 +83,7 @@
</para>
</listitem>
</itemizedlist>
-->
<note>
<para>
@ -90,18 +93,38 @@
</para>
</note>
<bridgehead renderas="sect4">intel-media-driver Dependencies</bridgehead>
<bridgehead renderas="sect3">intel-media-driver Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="cmake"/>,
<xref linkend="intel-gmmlib"/>, and
<xref linkend="libva"/>
</para>
</sect3>
</sect2>
<sect3 role="installation">
<sect2 role="kernel" id='intel-media-driver-kernel'>
<title>Kernel Configuration</title>
<para>
Enable the following options in the kernel configuration.
Recompile the kernel if necessary:
</para>
<screen><literal>Device Drivers ---&gt;
Graphics support ---&gt;
&lt;*/M&gt; Direct Rendering Manager (XFree86 ... support) ---&gt; [CONFIG_DRM]
&lt;*/M&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics [CONFIG_DRM_I915]</literal></screen>
<indexterm zone="intel-media-driver intel-media-driver-kernel">
<primary sortas="d-intel-media-driver">intel-media-driver</primary>
</indexterm>
</sect2>
<!-- TODO: It's said Gen9+ (Skylake or later) may need some firmware files. -->
<sect2 role="installation">
<title>Installation of intel-media-driver</title>
<note>
@ -126,11 +149,13 @@
</para>
</note>
<!--
<para>
First, fix a few build failures with GCC-13:
</para>
<screen><userinput remap="pre">patch -Np1 -i ../intel-media-driver-&intel-media-driver-version;-upstream_fixes-1.patch</userinput></screen>
-->
<para>
Install <application>intel-media-driver</application> by running the
@ -156,9 +181,9 @@ make</userinput></screen>
<screen role="root"><userinput>make install</userinput></screen>
</sect3>
</sect2>
<sect3 role="content">
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
@ -184,7 +209,7 @@ make</userinput></screen>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<bridgehead renderas="sect2">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
@ -203,6 +228,6 @@ make</userinput></screen>
</variablelist>
</sect3>
</sect2>
</sect1>

41
x/installing/intel-vaapi-driver.xml → multimedia/libdriv/intel-vaapi-driver.xml
View File

@ -13,7 +13,8 @@
<!ENTITY intel-vaapi-driver-time "0.3 SBU">
]>
<sect2 id="intel-vaapi-driver" xreflabel="intel-vaapi-driver-&intel-vaapi-driver-version;">
<sect1 id="intel-vaapi-driver" xreflabel="intel-vaapi-driver-&intel-vaapi-driver-version;">
<?dbhtml filename="intel-vaapi-driver.html"?>
<title>intel-vaapi-driver-&intel-vaapi-driver-version;</title>
@ -21,7 +22,7 @@
<primary sortas="a-intel-vaapi-driver">intel-vaapi-driver</primary>
</indexterm>
<sect3 role="package">
<sect2 role="package">
<title>Introduction to intel-vaapi-driver</title>
<para>
@ -32,7 +33,7 @@
&lfs113_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -66,16 +67,34 @@
</listitem>
</itemizedlist>
<bridgehead renderas="sect4">intel-vaapi-driver Dependencies</bridgehead>
<bridgehead renderas="sect3">intel-vaapi-driver Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="libva"/>
</para>
</sect3>
</sect2>
<sect3 role="installation">
<sect2 role="kernel" id='intel-vaapi-driver-kernel'>
<title>Kernel Configuration</title>
<para>
Enable the following options in the kernel configuration.
Recompile the kernel if necessary:
</para>
<screen><literal>Device Drivers ---&gt;
Graphics support ---&gt;
&lt;*/M&gt; Direct Rendering Manager (XFree86 ... support) ---&gt; [CONFIG_DRM]
&lt;*/M&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics [CONFIG_DRM_I915]</literal></screen>
<indexterm zone="intel-vaapi-driver intel-vaapi-driver-kernel">
<primary sortas="d-intel-vaapi-driver">intel-vaapi-driver</primary>
</indexterm>
</sect2>
<sect2 role="installation">
<title>Installation of intel-vaapi-driver</title>
<para>
@ -95,9 +114,9 @@ make</userinput></screen>
<screen role="root"><userinput>make install</userinput></screen>
</sect3>
</sect2>
<sect3 role="content">
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
@ -110,6 +129,6 @@ make</userinput></screen>
</seglistitem>
</segmentedlist>
</sect3>
</sect2>
</sect1>

5
multimedia/libdriv/libdriv.xml
View File

@ -40,6 +40,8 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="gst10-libav.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="gstreamer10-vaapi.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="id3lib.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="intel-media-driver.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="intel-vaapi-driver.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="liba52.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libao.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libaom.xml"/>
@ -61,6 +63,9 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libsamplerate.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libsndfile.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libtheora.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libva.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libvdpau.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libvdpau-va-gl.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libvorbis.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libvpx.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="mlt.xml"/>

35
x/installing/libva.xml → multimedia/libdriv/libva.xml
View File

@ -14,11 +14,12 @@
<!ENTITY libva-time "less than 0.1 SBU">
]>
<sect2 id="libva" xreflabel="libva-&libva-version;">
<sect1 id="libva" xreflabel="libva-&libva-version;">
<?dbhtml filename="libva.html"?>
<sect2info>
<sect1info>
<date>$Date$</date>
</sect2info>
</sect1info>
<title>libva-&libva-version;</title>
@ -26,7 +27,7 @@
<primary sortas="a-libva">libva</primary>
</indexterm>
<sect3 role="package">
<sect2 role="package">
<title>Introduction to libva</title>
<para>
@ -44,7 +45,7 @@
&lfs113_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -78,19 +79,19 @@
</listitem>
</itemizedlist>
<bridgehead renderas="sect4">libva Dependencies</bridgehead>
<bridgehead renderas="sect3">libva Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="libdrm"/>
</para>
<bridgehead renderas="sect5">Recommended</bridgehead>
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended">
<xref linkend="mesa"/>
</para>
<bridgehead renderas="sect5">Recommended (Runtime)</bridgehead>
<bridgehead renderas="sect4">Recommended (Runtime)</bridgehead>
<!-- "nodep" to prevent BLFS tool from blindly installing all the
drivers -->
<para role='nodep'>
@ -98,7 +99,7 @@
<xref linkend='intel-vaapi-driver'/> (for Intel GPUs provided with
Haswell CPUs or earlier),
<xref linkend='intel-media-driver'/> (for Intel GPUs provided with
Broadwell CPUs or later),
Broadwell CPUs or later), and
<xref linkend='mesa'/> (providing the <literal>r600</literal>,
<literal>raedonsi</literal>, and <literal>nouveau</literal> VA API
drivers, for the ATI/AMD Raedon HD 2xxx GPUs and later, and
@ -108,16 +109,16 @@ supported
for information on how to break it)
</para>
<bridgehead renderas="sect5">Optional</bridgehead>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="doxygen"/>,
<xref linkend="wayland"/>, and
<ulink url="https://gitlab.freedesktop.org/drm/igt-gpu-tools">intel-gpu-tools</ulink>
</para>
</sect3>
</sect2>
<sect3 role="installation">
<sect2 role="installation">
<title>Installation of libva</title>
<!-- libva*.so.2 have been around for a long time...
<caution>
@ -150,9 +151,9 @@ ninja</userinput></screen>
<screen role="root"><userinput>ninja install</userinput></screen>
</sect3>
</sect2>
<sect3 role="content">
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
@ -197,6 +198,6 @@ ninja</userinput></screen>
</variablelist>
</sect3>
</sect2>
</sect1>

41
x/installing/libvdpau-va-gl.xml → multimedia/libdriv/libvdpau-va-gl.xml
View File

@ -14,11 +14,12 @@
<!ENTITY libvdpau-va-gl-time "less than 0.1 SBU">
]>
<sect2 id="libvdpau-va-gl" xreflabel="libvdpau-va-gl-&libvdpau-va-gl-version;">
<sect1 id="libvdpau-va-gl" xreflabel="libvdpau-va-gl-&libvdpau-va-gl-version;">
<?dbhtml filename="libvdpau-va-gl.html"?>
<sect2info>
<sect1info>
<date>$Date$</date>
</sect2info>
</sect1info>
<title>libvdpau-va-gl-&libvdpau-va-gl-version;</title>
@ -26,7 +27,7 @@
<primary sortas="a-libvdpau-va-gl">libvdpau-va-gl</primary>
</indexterm>
<sect3 role="package">
<sect2 role="package">
<title>Introduction to libvdpau-va-gl</title>
<para>
@ -40,7 +41,7 @@
&lfs113_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -74,30 +75,30 @@
</listitem>
</itemizedlist>
<bridgehead renderas="sect4">libvdpau-va-gl Dependencies</bridgehead>
<bridgehead renderas="sect3">libvdpau-va-gl Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="cmake"/>,
<xref linkend="libvdpau"/>, and
<xref linkend="libva"/>
</para>
<bridgehead renderas="sect5">Optional</bridgehead>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="doxygen"/>,
<xref linkend="graphviz"/>, and
<xref linkend="texlive"/> or <xref linkend="tl-installer"/>
</para>
<bridgehead renderas="sect5">Runtime Dependency</bridgehead>
<bridgehead renderas="sect4">Runtime Dependency</bridgehead>
<para role="optional">
<xref role="runtime" linkend="mesa"/>
</para>
</sect3>
</sect2>
<sect3 role="installation">
<sect2 role="installation">
<title>Installation of libvdpau-va-gl</title>
<para>
@ -124,9 +125,9 @@ make</userinput></screen>
<screen role="root"><userinput>make install</userinput></screen>
</sect3>
</sect2>
<sect3 role="commands">
<sect2 role="commands">
<title>Command Explanations</title>
<para>
@ -134,10 +135,10 @@ make</userinput></screen>
fix the build for the C++ Standard Library header changes in gcc-13.
</para>
</sect3>
</sect2>
<sect3 role="configuration">
<sect2 role="configuration">
<title>Configuration</title>
<para>
@ -147,9 +148,9 @@ make</userinput></screen>
<screen role="root"><userinput>echo "export VDPAU_DRIVER=va_gl" >> /etc/profile.d/xorg.sh</userinput></screen>
</sect3>
</sect2>
<sect3 role="content">
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
@ -171,7 +172,7 @@ make</userinput></screen>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<bridgehead renderas="sect2">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
@ -190,6 +191,6 @@ make</userinput></screen>
</variablelist>
</sect3>
</sect2>
</sect1>

51
x/installing/libvdpau.xml → multimedia/libdriv/libvdpau.xml
View File

@ -14,11 +14,12 @@
<!ENTITY libvdpau-time "less than 0.1 SBU (with tests)">
]>
<sect2 id="libvdpau" xreflabel="libvdpau-&libvdpau-version;">
<sect1 id="libvdpau" xreflabel="libvdpau-&libvdpau-version;">
<?dbhtml filename="libvdpau.html"?>
<sect2info>
<sect1info>
<date>$Date$</date>
</sect2info>
</sect1info>
<title>libvdpau-&libvdpau-version;</title>
@ -26,7 +27,7 @@
<primary sortas="a-libvdpau">libvdpau</primary>
</indexterm>
<sect3 role="package">
<sect2 role="package">
<title>Introduction to libvdpau</title>
<para>
@ -57,7 +58,7 @@
&lfs113_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
@ -91,28 +92,38 @@
</listitem>
</itemizedlist>
<bridgehead renderas="sect4">libvdpau Dependencies</bridgehead>
<bridgehead renderas="sect3">libvdpau Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="xorg7-lib"/>
</para>
<bridgehead renderas="sect5">Optional</bridgehead>
<bridgehead renderas="sect4">Recommended (Runtime)</bridgehead>
<!-- "nodep" to prevent BLFS tool from blindly installing all the
drivers -->
<para role='nodep'>
The VDPAU driver suitable for the hardware in your system:
<xref linkend='libvdpau-va-gl'/> (for Intel GPUs) and
<xref linkend='mesa'/> (providing the <literal>r600</literal>,
<literal>raedonsi</literal>, and <literal>nouveau</literal> VDPAU
drivers, for the ATI/AMD Raedon HD 2xxx GPUs and later, and
<ulink url='https://nouveau.freedesktop.org/VideoAcceleration.html'>
supported
NVIDIA GPUs</ulink>; Mesa must be built after this package for these
drivers)
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="doxygen"/>,
<xref linkend="graphviz"/>, and
<xref linkend="texlive"/> or <xref linkend="tl-installer"/>
</para>
<bridgehead renderas="sect5">Runtime Dependency</bridgehead>
<para role="optional">
<xref role="runtime" linkend="mesa"/>
</para>
</sect2>
</sect3>
<sect3 role="installation">
<sect2 role="installation">
<title>Installation of libvdpau</title>
<para>
@ -146,9 +157,9 @@ ninja</userinput></screen>
<screen role="root"><userinput>[ -e $XORG_PREFIX/share/doc/libvdpau ] &amp;&amp; mv -v $XORG_PREFIX/share/doc/libvdpau{,&libvdpau-version;}</userinput></screen>
</sect3>
</sect2>
<sect3 role="content">
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
@ -170,7 +181,7 @@ ninja</userinput></screen>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<bridgehead renderas="sect2">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
@ -189,6 +200,6 @@ ninja</userinput></screen>
</variablelist>
</sect3>
</sect2>
</sect1>

82
multimedia/libdriv/pipewire.xml
View File

@ -6,10 +6,10 @@
<!ENTITY pipewire-download-http "https://github.com/PipeWire/pipewire/archive/&pipewire-version;/pipewire-&pipewire-version;.tar.gz">
<!ENTITY pipewire-download-ftp " ">
<!ENTITY pipewire-md5sum "b07218e9c5e0e1f3c80fe288c378d8c4">
<!ENTITY pipewire-md5sum "684576cc32eb622e8987cbb73b07d770">
<!ENTITY pipewire-size "2.0 MB">
<!ENTITY pipewire-buildsize "65 MB (with tests)">
<!ENTITY pipewire-time "0.5 SBU (with tests, both using parallelism=4)">
<!ENTITY pipewire-buildsize "80 MB (with tests)">
<!ENTITY pipewire-time "0.6 SBU (with tests, both using parallelism=4)">
]>
<sect1 id="pipewire" xreflabel="pipewire-&pipewire-version;">
@ -125,10 +125,10 @@
<screen><userinput>mkdir build &amp;&amp;
cd build &amp;&amp;
meson setup --prefix=/usr \
meson setup .. \
--prefix=/usr \
--buildtype=release \
-Dsession-managers= \
.. &amp;&amp;
-Dsession-managers="[]" &amp;&amp;
ninja</userinput></screen>
<para>
@ -157,8 +157,13 @@ ninja</userinput></screen>
href="../../xincludes/meson-buildtype-release.xml"/>
<para>
<parameter>-Dsession-managers=</parameter>: This switch
prevents automatic downloading external dependencies.
<parameter>-Dsession-managers=[]</parameter>: This switch
allows to specify the session managers to build as subprojects. Since
the recommended session manager (<ulink
url="https://gitlab.freedesktop.org/pipewire/wireplumber">
WirePlumber</ulink>) is available as a standalone
project, don't specify anything here. This prevents downloading external
dependencies during the meson step.
</para>
<para>
@ -190,8 +195,6 @@ ninja</userinput></screen>
<seglistitem>
<seg>
pipewire,
pipewire-avb,
pipewire-pulse,
pw-cat,
pw-cli,
pw-config,
@ -212,33 +215,15 @@ ninja</userinput></screen>
spa-json-dump,
spa-monitor,
spa-resample, and
pw-dsdplay, pw-midiplay, pw-midirecord, pw-play, and pw-record
(symlinks to pw-cat)
pipewire-aes67, pipewire-avb, pipewire-pulse (symlinks to pipewire),
pw-dsdplay, pw-encplay, pw-midiplay, pw-midirecord, pw-play,
pw-record (symlinks to pw-cat)
</seg>
<seg>
libpipewire-0.3.so and
56 modules below /usr/lib/pipewire-0.3 and /usr/lib/spa-0.2<!--,
[pierre July 29th, 2020]: all the following libs are in subdirectories
of /usr/lib. I'm not sure they should appear. But if they should, there
are many more libs to list...
libpulse-mainloop-glib-pw.so,
libpulse.so,
libpulse-simple.so,
libasound_module_pcm_pipewire.so, and
libgstpipewire.so
[bdubbs Sep 29th, 2020]: add
libpipewire-module-{access,adapter,client-device,client-node,
link-factory,metadata,portal,profiler,protocol-native,
rtkit,session-manager,spa-device,spa-device-factory,spa-node,
spa-node-factory}.so
libasound_module_ctl_pipewire.so
libasound_module_pcm_pipewire.so
libspa-{alsa,audioconvert,audiomixer,bluez5,control,dbus,support
v4l2,videoconvert}.so
-->
58 modules below /usr/lib/pipewire-0.3 and /usr/lib/spa-0.2
</seg>
<seg>
<!--/etc/pipewire,-->
/usr/include/pipewire-0.3,
/usr/include/spa-0.2,
/usr/lib/alsa-lib,
@ -269,7 +254,7 @@ ninja</userinput></screen>
</indexterm>
</listitem>
</varlistentry>
<!-- not installed now: deprecated
<varlistentry id="pipewire-media-session">
<term><command>pipewire-media-session</command></term>
<listitem>
@ -282,7 +267,7 @@ ninja</userinput></screen>
</indexterm>
</listitem>
</varlistentry>
-->
<varlistentry id="pipewire-pulse">
<term><command>pipewire-pulse</command></term>
<listitem>
@ -443,20 +428,6 @@ ninja</userinput></screen>
</listitem>
</varlistentry>
<!--
<varlistentry id="pw-pulse">
<term><command>pw-pulse</command></term>
<listitem>
<para>
runs Pulseaudio applications on pipewire.
</para>
<indexterm zone="pipewire pw-pulse">
<primary sortas="b-pw-pulse">pw-pulse</primary>
</indexterm>
</listitem>
</varlistentry>
-->
<varlistentry id="pw-reserve">
<term><command>pw-reserve</command></term>
<listitem>
@ -564,20 +535,7 @@ ninja</userinput></screen>
</indexterm>
</listitem>
</varlistentry>
<!--
<varlistentry id="libpulse-mainloop-glib-pw">
<term><filename class="libraryfile">libpulse-mainloop-glib-pw.so</filename></term>
<listitem>
<para>
provides a glib main() loop for pulseaudio to route media through
pipewire.
</para>
<indexterm zone="pipewire libpulse-mainloop-glib-pw">
<primary sortas="c-libpulse-mainloop-glib-pw">libpulse-mainloop-glib-pw.so</primary>
</indexterm>
</listitem>
</varlistentry>
<!-- not in /usr/lib
<varlistentry id="libpulse">
<term><filename class="libraryfile">libpulse.so</filename></term>
<listitem>

6
multimedia/libdriv/sdl2.xml
View File

@ -6,10 +6,10 @@
<!ENTITY sdl2-download-http "https://www.libsdl.org/release/SDL2-&sdl2-version;.tar.gz">
<!ENTITY sdl2-download-ftp " ">
<!ENTITY sdl2-md5sum "f7e53a08a706999ceb033bb911fe3c6e">
<!ENTITY sdl2-md5sum "ccd2cd02b2ad4f71c2588747028953c3">
<!ENTITY sdl2-size "7.7 MB">
<!ENTITY sdl2-buildsize "240 MB (with docs)">
<!ENTITY sdl2-time "0.6 SBU (using parallelism=4; with docs)">
<!ENTITY sdl2-buildsize "190 MB (with docs)">
<!ENTITY sdl2-time "0.5 SBU (using parallelism=4; with docs)">
]>
<sect1 id="sdl2" xreflabel="SDL2-&sdl2-version;">

11
multimedia/libdriv/taglib.xml
View File

@ -6,10 +6,10 @@
<!ENTITY taglib-download-http "https://taglib.org/releases/taglib-&taglib-version;.tar.gz">
<!ENTITY taglib-download-ftp " ">
<!ENTITY taglib-md5sum "0b75619b67b9149cfcbbe5c127df6395">
<!ENTITY taglib-md5sum "2fe6089da73ad414aa1b982b83415362">
<!ENTITY taglib-size "1.3 MB">
<!ENTITY taglib-buildsize "13 MB">
<!ENTITY taglib-time "0.3 SBU">
<!ENTITY taglib-time "0.2 SBU">
]>
<sect1 id="taglib" xreflabel="taglib-&taglib-version;">
@ -75,6 +75,10 @@
<xref linkend="cmake"/>
</para>
<bridgehead renderas="sect4">Optional (for tests)</bridgehead>
<para role="optional">
<ulink url='https://sourceforge.net/projects/cppunit/'>Cppunit</ulink>
</para>
</sect2>
<sect2 role="installation">
@ -95,7 +99,8 @@ cmake -DCMAKE_INSTALL_PREFIX=/usr \
make</userinput></screen>
<para>
This package does not come with a test suite.
The test suite requires <application>Cppunit</application> but it's
not a BLFS package.
</para>
<para>

3
networking/connect/connect.xml
View File

@ -36,6 +36,7 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="advanced-network.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dhcpcd.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dhcp.xml"/>
<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dhcp.xml"/>-->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="kea.xml"/>
</chapter>

682
networking/connect/kea.xml Normal file
View File

@ -0,0 +1,682 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY kea-download-http "https://downloads.isc.org/isc/kea/&kea-dhcp-version;/kea-&kea-dhcp-version;.tar.gz">
<!ENTITY kea-download-ftp "ftp://ftp.isc.org/isc/kea/&kea-dhcp-version;/kea-&kea-dhcp-version;.tar.gz">
<!ENTITY kea-md5sum "e01bdc8d68cfaca1cae17b20b26e09b6">
<!ENTITY kea-size "9.9 MB">
<!ENTITY kea-buildsize "1.1 GB">
<!ENTITY kea-time "14 SBU"><!-- Thats unexpectedly long -->
<!ENTITY kea-arm-vers "&kea-dhcp-version;">
]>
<sect1 id="kea" xreflabel="KEA-&kea-dhcp-version;">
<?dbhtml filename="kea.html"?>
<title>Kea &kea-dhcp-version;</title>
<indexterm zone="kea">
<primary sortas="a-KEA">Kea</primary>
</indexterm>
<sect2 role="package">
<title>Introduction to ISC Kea</title>
<para>
The <application>ISC Kea</application> package contains the
server programs for DHCP. It is the successor of the
old ISC DHCP server which is end-of-life since December 2022.
</para>
&lfs113_checked;
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
Download (HTTP): <ulink url="&kea-download-http;"/>
</para>
</listitem>
<listitem>
<para>
Download (FTP): <ulink url="&kea-download-ftp;"/>
</para>
</listitem>
<listitem>
<para>
Download MD5 sum: &kea-md5sum;
</para>
</listitem>
<listitem>
<para>
Download size: &kea-size;
</para>
</listitem>
<listitem>
<para>
Estimated disk space required: &kea-buildsize;
</para>
</listitem>
<listitem>
<para>
Estimated build time: &kea-time;
</para>
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">Kea Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required">
<xref linkend="boost"/>,
<xref linkend="log4cplus"/>
</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="mitkrb"/>, for documentation
<xref linkend="doxygen"/>,
<xref linkend="graphviz"/>,
<xref linkend="sphinx_rtd_theme"/>
</para>
<bridgehead renderas="sect4">Optional database backends</bridgehead>
<para role="optional">
<xref linkend="mariadb"/> or <ulink url="https://www.mysql.com/">MySQL</ulink>,
<xref linkend="postgresql"/>
</para>
<!--
<para condition="html" role="usernotes">Editor Notes:
<ulink url="&blfs-wiki;/kea"/>
</para>
-->
</sect2>
<sect2 role="kernel" id="kea-dhcp-kernel">
<title>Kernel Configuration</title>
<para>
You must have Packet Socket support. IPv6 support is optional.
</para>
<screen><literal>[*] Networking support ---&gt; [CONFIG_NET]
Networking options ---&gt;
&lt;*&gt; Packet socket [CONFIG_PACKET]
&lt;*&gt; The IPv6 Protocol ---&gt; [CONFIG_IPV6]</literal></screen>
<indexterm zone="kea kea-dhcp-kernel">
<primary sortas="k-KEA">Kea</primary>
</indexterm>
</sect2>
<sect2 role="installation">
<title>Installation of ISC Kea DHCP</title>
<para>
Install <application>ISC Kea DHCP</application> by running
the following commands:
</para>
<screen><userinput>./configure --prefix=/usr \
--sysconfdir=/etc \
--docdir=/usr/share/doc/kea-&kea-dhcp-version; \
--localstatedir=/var \
--enable-shell \
--with-openssl \
--disable-static &amp;&amp;
make</userinput></screen>
<para>
To test the results, issue: <command>make check</command>.
</para>
<para>
To install the <application>ISC Kea DHCP</application> suite,
issue the following commands as the
<systemitem class="username">root</systemitem> user:
</para>
<screen role="root"><userinput>make -j1 install</userinput></screen>
</sect2>
<sect2 role="commands">
<title>Command Explanations</title>
<para>
<parameter>--with-pgsql</parameter> or <parameter>--with-mysql</parameter>:
<application>ISC Kea</application> can store the leases on a
database. This might be useful in large environments running
a cluster of DHCP servers. Using the <emphasis>memfile</emphasis>
backend (which is a CSV file stored locally) is possible anyhow.
</para>
<para>
<parameter>--enable-generate-docs</parameter>:
If documentation is to be rebuilt, add that option. Several
dependencies must be installed for generating the documentation.
</para>
<para>
<parameter>make -j1 install</parameter>: ISC does not recommend
any form of parallel or job server options when doing the install.
</para>
</sect2>
<sect2 role="configuration">
<title>Configuring ISC Kea DHCP</title>
<para>The support of IPv4, IPv6 and DDNS has been splitted into
separate servers which runs independently from each other. Each
of them has its own configuration file. Additional configuration
files come from the keactrl agent which is uses to control the
servers in an easy way.</para>
<para>Consult the
<ulink url="https://kea.readthedocs.io/en/kea-&kea-arm-vers;/">Kea Administrator Reference Manual</ulink>
for detailed information about the configuration of <application>ISC Kea</application>
as it is a quite capable system. The configuration shown a bare
minimum to get a DHCP server running but it already includes
configuration for DDNS (Dynamic DNS). That setup might be working
for small networks with a few clients and low traffic. For greater
installations with thousands of clients, <application>ISC Kea</application>
can be configured to use databases (mariadb or postgresql) to store
the leases and build a cluster with multiple nodes. It can
be integrated to <ulink url="https://www.isc.org/categories/stork/">ISC Stork</ulink>
which is a management dashboard to <application>ISC Kea</application>.</para>
<para>
If you want to start the DHCP Server at boot, install the
<phrase revision="sysv"><filename>/etc/rc.d/init.d/kea-dhcpd</filename>
init script</phrase>
<phrase revision="systemd"><filename>kea-dhcpd.service</filename>
unit</phrase> included in the
<xref linkend="bootscripts" revision="sysv"/>
<xref linkend="systemd-units" revision="systemd"/>
package:
</para>
<screen role="root"><userinput>make install-kea-dhcpd</userinput></screen>
<sect3 id="kea-dhcp-config">
<title>Config Files</title>
<para>
<filename>/etc/kea/keactrl.conf</filename>,
<filename>/etc/kea/kea-ctrl-agent.conf</filename>,
<filename>/etc/kea/kea-dhcp4.conf</filename>,
<filename>/etc/kea/kea-dhcp6.conf</filename> and
<filename>/etc/kea/kea-dhcp-ddns.conf</filename>
</para>
<indexterm zone="kea keactrl-config">
<primary sortas="e-etc-kea-keactrl.conf">/etc/kea/keactrl.conf</primary>
</indexterm>
<indexterm zone="kea kea-ctrl-agent-config">
<primary sortas="e-etc-kea-kea-ctrl-agent.conf">/etc/kea/kea-ctrl-agent.conf</primary>
</indexterm>
<indexterm zone="kea kea-dhcp4-config">
<primary sortas="e-etc-kea-dhcp4.conf">/etc/kea/kea-dhcp4.conf</primary>
</indexterm>
<!--
<indexterm zone="kea kea-dhcp6-config">
<primary sortas="e-etc-kea-dhcp6.conf">/etc/kea/kea-dhcp6.conf</primary>
</indexterm>
-->
<indexterm zone="kea kea-dhcp-ddns-config">
<primary sortas="e-etc-kea-dhcp-ddns.conf">/etc/kea/kea-dhcp-ddns.conf</primary>
</indexterm>
</sect3>
<sect3 id="keactrl-config">
<title>Kea Control Configuration</title>
<para><command>keactrl</command> is used to control the
independent servers (IPv4, IPv6, DDNS). Its configuration file
<filename>/etc/kea/keactrl.conf</filename> is installed by
default and includes many path settings which are defined
due to the <command>configure</command> at build time. It also
includes settings to specify which of the servers should be
started.</para>
<itemizedlist>
<listitem>
<para>Control Agent</para>
<para>The Control Agent is a daemon which allows the
(re)configuration of the Kea DHCP service via REST API.
Set <literal>ctrl_agent=yes</literal> to start the
control agent (service providing a REST API), set
<literal>ctrl_agent=no</literal> in case the control agent
is not needed.</para>
</listitem>
<listitem>
<para>IPv4 DHCP server</para>
<para>This daemon handles requests for IPv4 addresses.
Set <literal>dhcp4=yes</literal> to start it, set
<literal>dhcp4=no</literal> in case DHCP service for IPv4
is not wanted.</para>
</listitem>
<listitem>
<para>IPv6 DHCP server</para>
<para>This daemon handles requests for IPv6 addresses.
Set <literal>dhcp6=yes</literal> to start it, set
<literal>dhcp6=no</literal> in case DHCP service for IPv6
is not wanted.</para>
</listitem>
<listitem>
<para>Dynamic DNS</para>
<para>This daemon is used to update a DNS server dynamically
when Kea assignes an IP address to a device.
Set <literal>dhcp_ddns=yes</literal> to enable it, set
<literal>dhcp_ddns=no</literal> in case dynamic DNS updates
are not wanted.</para>
</listitem>
</itemizedlist>
<para>The Netconf service is not installed because required
dependencies are not covered by the current BLFS book.</para>
<para>With the following command, Kea will be configured to
start the dhcp service for IPv4 and the
dynamic DNS update, while the control agent and
the dhcp service for IPv6 remains down. Tweak the command to
match your needs on started services and execute as the
<systemitem class="username">root</systemitem> user:</para>
<screen><userinput role="root">sed -e "s/^dhcp4=.*/dhcp4=yes/" \
-e "s/^dhcp6=.*/dhcp6=no/" \
-e "s/^dhcp_ddns=.*/dhcp_ddns=yes/" \
-e "s/^ctrl_agent=.*/ctrl_agent=no/" \
-i /etc/kea/keactrl.conf
</userinput></screen>
</sect3>
<sect3 id="kea-ctrl-agent-config">
<title>Control Agent Configuration</title>
<para>
The provided configuration could be used without changes
but in BLFS objects like sockets are stored in
<filename class="directory">/run</filename>
rather than in
<filename class="directory">/tmp</filename>.
</para>
<screen role="nodump"><userinput>cat &gt; /etc/kea/kea-ctrl-agent.conf &lt;&lt; "EOF"
<literal>// Begin /etc/kea/kea-ctrl-agent.conf
{
// This is a basic configuration for the Kea Control Agent.
// RESTful interface to be available at http://127.0.0.1:8000/
"Control-agent": {
"http-host": "127.0.0.1",
"http-port": 8000,
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/run/kea4-ctrl-socket"
},
"dhcp6": {
"socket-type": "unix",
"socket-name": "/run/kea6-ctrl-socket"
},
"d2": {
"socket-type": "unix",
"socket-name": "/run/kea-ddns-ctrl-socket"
}
},
"loggers": [
{
"name": "kea-ctrl-agent",
"output_options": [
{
"output": "/var/log/kea-ctrl-agent.log"
"pattern": "%D{%Y-%m-%d %H:%M:%S.%q} %-5p %m\n"
}
],
"severity": "INFO",
"debuglevel": 0
}
]
}
}
// End /etc/kea/kea-ctrl-agent.conf</literal>
EOF</userinput></screen>
</sect3>
<sect3 id="kea-dhcp4-config">
<title>IPv4 DHCP Server Configuration</title>
<para>
A sample configuration file is created in <filename>/etc/kea/kea-dhcp4.conf</filename>.
Adjust the file to suit your needs or overwrite it by using
the following sample as the <systemitem class="username">root</systemitem>
user:
</para>
<screen role="nodump"><userinput>cat &gt; /etc/kea/kea-dhcp4.conf &lt;&lt; "EOF"
<literal>// Begin /etc/kea/kea-dhcp4.conf
{
"Dhcp4": {
// Add names of your network interfaces to listen on.
"interfaces-config": {
"interfaces": [ "eth0", "eth2" ]
},
"control-socket": {
"socket-type": "unix",
"socket-name": "/run/kea4-ctrl-socket"
},
"lease-database": {
"type": "memfile",
"lfc-interval": 3600
},
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
"renew-timer": 900,
"rebind-timer": 1800,
"valid-lifetime": 3600,
// Enable DDNS - Kea will dynamically update the DNS
"ddns-send-updates" : true,
"ddns-qualifying-suffix": "your.domain.tld",
"dhcp-ddns" : {
"enable-updates": true
},
"subnet4": [
{
"subnet": "192.168.56.0/24",
"pools": [ { "pool": "192.168.56.16 - 192.168.56.254" } ],
"option-data": [
{
"name": "domain-name",
"data": "your.domain.tld"
},
{
"name": "domain-name-servers",
"data": "192.168.56.2, 192.168.3.7"
},
{
"name": "domain-search",
"data": "your.domain.tld"
},
{
"name": "routers",
"data": "192.168.56.2"
}
]
}
],
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-dhcp4.log",
"pattern": "%D{%Y-%m-%d %H:%M:%S.%q} %-5p %m\n"
}
],
"severity": "INFO",
"debuglevel": 0
}
]
}
}
// End /etc/kea/kea-dhcp4.conf</literal>
EOF</userinput></screen>
<para>
The configuration for IPv6 is similar to the configuration
of IPv4. The configuration file is
<filename>/etc/kea/kea-dhcp6.conf</filename>.
</para>
</sect3>
<sect3 id="kea-dhcp-ddns-config">
<title>Dynamic DNS Configuration</title>
<para>
If there is a <xref linkend="bind"/> server running,
<application>ISC Kea</application> can update the DNS when
it gives an IP address to a client. A sample configuration
file is created in <filename>/etc/kea/kea-dhcp-ddns.conf</filename>.
Adjust the file to suit your needs or overwrite it by using
the following sample as the <systemitem class="username">root</systemitem>
user:
</para>
<screen role="nodump" ><userinput>cat &gt; /etc/kea/kea-dhcp-ddns.conf &lt;&lt; "EOF"
<literal>// Begin /etc/kea/kea-dhcp-ddns.conf
{
"DhcpDdns": {
"ip-address": "127.0.0.1",
"port": 53001,
"control-socket": {
"socket-type": "unix",
"socket-name": "/run/kea-ddns-ctrl-socket"
},
"tsig-keys": [
{
"name" : "rndc-key",
"algorithm" : "hmac-sha256",
"secret" : "1FU5hD7faYaajQCjSdA54JkTPQxbbPrRnzOKqHcD9cM="
}
],
"forward-ddns" : {
"ddns-domains" : [
{
"name" : "your.domain.tld.",
"key-name": "rndc-key",
"dns-servers" : [
{
"ip-address" : "127.0.0.1",
"port" : 53
}
]
}
]
},
"reverse-ddns" : {
"ddns-domains" : [
{
"name" : "56.168.192.in-addr.arpa.",
"key-name": "rndc-key",
"dns-servers" : [
{
"ip-address" : "127.0.0.1",
"port" : 53
}
]
}
]
},
"loggers": [
{
"name": "kea-dhcp-ddns",
"output_options": [
{
"output": "/var/log/kea-ddns.log",
"pattern": "%D{%Y-%m-%d %H:%M:%S.%q} %-5p %m\n"
}
],
"severity": "INFO",
"debuglevel": 0
}
]
}
}
// End /etc/kea/kea-dhcp-ddns.conf</literal>
EOF</userinput></screen>
<note>
<para>
The value of <literal>secret</literal> is just an example.
Generate the key for your installation by using the
<command>rndc-confgen -a</command> command or the
<command>tsig-keygen</command> command which both are
provided by <xref linkend="bind"/>.
</para>
<para>
In this sample config it is assumed that the DNS server
runs on the same machine as Kea does (accessable via
<literal>127.0.0.1</literal>) and that this machine has
the IP <literal>192.168.56.2</literal>.
</para>
</note>
</sect3>
</sect2>
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
<segtitle>Installed Programs</segtitle>
<segtitle>Installed Libraries</segtitle>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>
keactrl, kea-admin, kea-ctrl-agent, kea-dhcp4, kea-dhcp6,
kea-dhcp-ddns, kea-lfc, kea-shell
</seg>
<seg>
libkea-*
</seg>
<seg>
/etc/kea,
/usr/include/kea,
/var/lib/kea
</seg>
</seglistitem>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
<varlistentry id="keactrl">
<term><command>keactrl</command></term>
<listitem>
<para>
Tool to control (start/stop) the server processes.
</para>
<indexterm zone="kea keactrl">
<primary sortas="b-keactrl">keactrl</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-admin">
<term><command>kea-admin</command></term>
<listitem>
<para>
kea-admin is a shell script which offers database maintenance.
</para>
<indexterm zone="kea kea-admin">
<primary sortas="b-kea-admin">kea-admin</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-ctrl-agent">
<term><command>kea-ctrl-agent</command></term>
<listitem>
<para>
Daemon which exposes a RESTful control interface for
managing Kea servers.
</para>
<indexterm zone="kea kea-ctrl-agent">
<primary sortas="b-kea-ctrl-agent">kea-ctrl-agent</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-dhcp4">
<term><command>kea-dhcp4</command></term>
<listitem>
<para>
The server daemon providing IPv4 addresses.
</para>
<indexterm zone="kea kea-dhcp4">
<primary sortas="b-kea-dhcp4">kea-dhcp4</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-dhcp6">
<term><command>kea-dhcp6</command></term>
<listitem>
<para>
The server daemon providing IPv6 addresses.
</para>
<indexterm zone="kea kea-dhcp6">
<primary sortas="b-kea-dhcp6">kea-dhcp6</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-dhcp-ddns">
<term><command>kea-dhcp-ddns</command></term>
<listitem>
<para>
The server daemon performing the dynamic DNS updates.
</para>
<indexterm zone="kea kea-dhcp-ddns">
<primary sortas="b-kea-dhcp-ddns">kea-dhcp-ddns</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="kea-lfc">
<term><command>kea-lfc</command></term>
<listitem>
<para>
The kea-lfc service process removes redundant information
from the files used to provide persistent storage for the
memfile database backend. It is run by the Kea DHCP server.
</para>
<indexterm zone="kea kea-lfc">
<primary sortas="b-kea-lfc">kea-lfc</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="keashell">
<term><command>keashell</command></term>
<listitem>
<para>
RESTful client to the <application>ISC Kea</application>
services.
</para>
<indexterm zone="kea keashell">
<primary sortas="b-keashell">keashell</primary>
</indexterm>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>

8
networking/netlibs/curl.xml
View File

@ -380,10 +380,12 @@ It appears that every test is now run under valgrind.
rm -rf docs/examples/.deps &amp;&amp;
find docs \( -name Makefile\* -o -name \*.1 -o -name \*.3 \) -exec rm {} \; &amp;&amp;
find docs \( -name Makefile\* -o \
-name \*.1 -o \
-name \*.3 -o \
-name CMakeLists.txt \) -delete &amp;&amp;
install -v -d -m755 /usr/share/doc/curl-&curl-version; &amp;&amp;
cp -v -R docs/* /usr/share/doc/curl-&curl-version;</userinput></screen>
cp -v -R docs -T /usr/share/doc/curl-&curl-version;</userinput></screen>
<para>
To run some simple verification tests on the newly installed

2
networking/netlibs/glib-networking.xml
View File

@ -9,7 +9,7 @@
<!ENTITY glib-networking-download-ftp " ">
<!-- <!ENTITY glib-networking-download-ftp
"&gnome-download-ftp;/glib-networking/2.66/glib-networking-&glib-networking-version;.tar.xz"> -->
<!ENTITY glib-networking-md5sum "7f57d2f6a68d49a656912a5d226c2ed1">
<!ENTITY glib-networking-md5sum "05b519bb1f009789e6b82af88ed1b59a">
<!ENTITY glib-networking-size "276 KB">
<!ENTITY glib-networking-buildsize "5.6 MB (with tests)">
<!ENTITY glib-networking-time "0.1 SBU (with tests)">

4
networking/netprogs/samba.xml
View File

@ -78,7 +78,6 @@
<xref linkend="jansson"/>,
<xref linkend="perl-json"/>,
<xref linkend="libtirpc"/>,
<xref linkend="lmdb"/>,
<xref linkend="perl-parse-yapp"/>, and
<xref linkend="rpcsvc-proto"/>
</para>
@ -92,7 +91,8 @@
<xref linkend="icu"/>,
<xref linkend="libtasn1"/>,
<xref linkend="libxslt"/> (for documentation),
<xref linkend="linux-pam"/>, and
<xref linkend="linux-pam"/>,
<xref linkend="lmdb"/>, and
<xref linkend="openldap"/>
</para>

31
networking/netprogs/wpa_supplicant.xml
View File

@ -381,7 +381,7 @@ update_config=1</screen>
<para revision="sysv">
If your router/access point uses DHCP to allocate IP addresses, you
can install <xref linkend="dhcp"/> client and use it to
can install <xref linkend="dhcpcd" role="nodep"/> and use it to
automatically obtain network addresses. Create the
<filename>/etc/sysconfig/ifconfig-<replaceable>wifi0</replaceable>
</filename> by running the following command as the
@ -396,35 +396,6 @@ SERVICE="wpa"
# Additional arguments to wpa_supplicant
WPA_ARGS=""
WPA_SERVICE="dhclient"
DHCP_START=""
DHCP_STOP=""
# Set PRINTIP="yes" to have the script print
# the DHCP assigned IP address
PRINTIP="no"
# Set PRINTALL="yes" to print the DHCP assigned values for
# IP, SM, DG, and 1st NS. This requires PRINTIP="yes".
PRINTALL="no"</literal>
EOF</userinput></screen>
<para revision="sysv">
If you prefer <xref linkend="dhcpcd"/> instead of
<xref linkend="dhcp"/> client, then create the
<filename>/etc/sysconfig/ifconfig-<replaceable>wifi0</replaceable>
</filename> by running the following command as the
<systemitem class="username">root</systemitem> user:
</para>
<screen role="root" revision="sysv"><userinput>cat &gt; /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> &lt;&lt; "EOF"
<literal>ONBOOT="yes"
IFACE="<replaceable>wlan0</replaceable>"
SERVICE="wpa"
# Additional arguments to wpa_supplicant
WPA_ARGS=""
WPA_SERVICE="dhcpcd"
DHCP_START="-b -q <replaceable>&lt;insert appropriate start options here&gt;</replaceable>"
DHCP_STOP="-k <replaceable>&lt;insert additional stop options here&gt;</replaceable>"</literal>

Some files were not shown because too many files have changed in this diff Show More