diff --git a/archive/git.xml b/archive/git.xml
index a4c340441b..d728b50a1b 100644
--- a/archive/git.xml
+++ b/archive/git.xml
@@ -23,18 +23,18 @@
Introduction to Git
- Git is a free and open source, distributed
+ Git is a free and open source, distributed
version control system designed to handle everything from small to very
large projects with speed and efficiency. Every
- Git clone is a full-fledged repository with
+ Git clone is a full-fledged repository with
complete history and full revision tracking capabilities, not dependent
on network access or a central server. Branching and merging are fast and
- easy to do. Git is used for version control of
- files, much like tools such as Mercurial,
- Bazaar, Subversion,
+ easy to do. Git is used for version control of
+ files, much like tools such as Mercurial,
+ Bazaar, Subversion,
CVS,
- Perforce, and
- Team Foundation Server.
+ Perforce, and
+ Team Foundation Server.
@@ -71,7 +71,7 @@
Recommended
- (needed to use Git over
+ (needed to use Git over
http, https, ftp or ftps)
@@ -81,7 +81,7 @@
Installation of Git
- Install Git by running the following
+ Install Git by running the following
commands:
@@ -242,14 +242,14 @@ sed -i '/^\* link:/s|howto/|&html/|' /usr/share/doc/git-&git-version;/howto-
--with-gitconfig=/etc/gitconfig: This sets
/etc/gitconfig as the file that stores
- the default, system wide, Git
+ the default, system wide, Git
settings.
--with-python=python3: Use this switch to use
- Python 3, instead of the EOL'ed
- Python 2. Python is used for the
+ Python 3, instead of the EOL'ed
+ Python 2. Python is used for the
git p4 interface to Perforce repositories,
and also used in some tests.
@@ -257,7 +257,7 @@ sed -i '/^\* link:/s|howto/|&html/|' /usr/share/doc/git-&git-version;/howto-
@@ -354,7 +354,7 @@ sed -i '/^\* link:/s|howto/|&html/|' /usr/share/doc/git-&git-version;/howto-
git-cvsserver
- is a CVS server emulator for Git
+ is a CVS server emulator for Git
git-cvsserver
@@ -366,7 +366,7 @@ sed -i '/^\* link:/s|howto/|&html/|' /usr/share/doc/git-&git-version;/howto-
gitk
- is a graphical Git repository browser
+ is a graphical Git repository browser
(needs Tk)
diff --git a/archive/glibc.xml b/archive/glibc.xml
index d683c85f91..c593602d76 100644
--- a/archive/glibc.xml
+++ b/archive/glibc.xml
@@ -71,7 +71,7 @@
lib32 Installation of glibc
- Install lib32-glibc by running the following commands:
+ Install lib32-glibc by running the following commands:
patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch &&
diff --git a/archive/glslang.xml b/archive/glslang.xml
index e103b81ee6..80d0b342b7 100644
--- a/archive/glslang.xml
+++ b/archive/glslang.xml
@@ -21,7 +21,7 @@
Introduction to Glslang
- The Glslang package contains an frontend and
+ The Glslang package contains an frontend and
validator for OpenGL, OpenGL ES, and Vulkan shaders.
@@ -75,7 +75,7 @@
-->
- Install Glslang by running the following
+ Install Glslang by running the following
commands:
@@ -107,7 +107,7 @@ ninjalib32 Installation of Glslang
- Install lib32-Glslang by running the following
+ Install lib32-Glslang by running the following
commands:
diff --git a/archive/gnat-binary.xml b/archive/gnat-binary.xml
index b8ab191c60..35a11e0393 100644
--- a/archive/gnat-binary.xml
+++ b/archive/gnat-binary.xml
@@ -33,12 +33,12 @@
The compiler and associated tools on this page are known as the
- GNAT technology, developed by the Adacore
- company, using the GCC backend. Since
+ GNAT technology, developed by the Adacore
+ company, using the GCC backend. Since
parts of the Ada compiler are written in Ada, there is a circular
dependency on an Ada compiler. The instructions below install a
binary compiler. You do not need to do that if you already have built
- GNAT tools. The next section covers how to
+ GNAT tools. The next section covers how to
build GNAT once the circular dependency is satisfied.
@@ -68,7 +68,7 @@
links. You can use
but not .
- If you do end up using wget
+ If you do end up using wget
regardless of the recommendation against it, please run
the following the command before unpacking:
@@ -81,9 +81,9 @@
If you are doing multilib, just download the x86_64
- GNAT binary tarball.
+ GNAT binary tarball.
The instructions in the next section for multilib will
- work as expected and GCC
+ work as expected and GCC
will continue to have multilib support.
@@ -94,7 +94,7 @@
Installation of GNAT Binaries
- Install the x86_64 GNAT
+ Install the x86_64 GNAT
binaries by running the following commands as the
root user
while still in the directory the tarball is in:
@@ -111,7 +111,7 @@ cd $GNATTBPATH &&
unset GNATTBPATH
- Or install the x86 GNAT
+ Or install the x86 GNAT
binaries by running the following commands as the
root user
while still in the directory the tarball is in:
@@ -129,7 +129,7 @@ unset GNATTBPATH
Now adjust the PATH variable so
- the GNAT software can be found
+ the GNAT software can be found
and used:
@@ -138,7 +138,7 @@ export PATH=/opt/gnat/bin:$PATH_HOLD
Ensure ld and as
- from the GNAT package aren't
+ from the GNAT package aren't
used as to prevent issues with aging by issuing the
following as the root
user:
diff --git a/archive/gnat.xml b/archive/gnat.xml
index 4fd61eb55b..81140ff084 100644
--- a/archive/gnat.xml
+++ b/archive/gnat.xml
@@ -21,10 +21,10 @@
Introduction to GNAT
- GNAT is a part of
- GCC. It is often called
+ GNAT is a part of
+ GCC. It is often called
GCC-Ada because of this. Not many packages depend
- on GNAT besides
+ on GNAT besides
, although some packages
optionally depend on it.
@@ -137,7 +137,7 @@ else
fi
- Now install GNAT by running the following
+ Now install GNAT by running the following
commands:
@@ -166,8 +166,8 @@ sed -e 's/{ target nonpic } //' \
If you have installed additional packages such as
- valgrind and gdb
- , the gcc part of the
+ valgrind and gdb
+ , the gcc part of the
test suite will run more tests than in LFS. Some of those will
report FAIL and others XPASS (pass when expected to FAIL).
As of gcc-&gcc-version;, about 74 FAIL occur in the “guality”
@@ -209,7 +209,7 @@ ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \
Cleaning Up and Testing
- Now that GNAT has been installed,
+ Now that GNAT has been installed,
it is time to clean up and test your installation to make sure
everything is working as expected.
@@ -289,7 +289,7 @@ rm -v testgnat*
mkdir build; cd build: The
- GCC documentation recommends
+ GCC documentation recommends
building the package in a dedicated build directory.
@@ -307,9 +307,9 @@ rm -v testgnat*
--with-system-zlib: Uses the system
- zlib instead of the bundled one.
- zlib is used for compressing
- and decompressing GCC's intermediate
+ zlib instead of the bundled one.
+ zlib is used for compressing
+ and decompressing GCC's intermediate
language in LTO (Link Time Optimization) object files.
@@ -332,8 +332,8 @@ rm -v testgnat*
This command builds support for ADA, C, and C++. Refer to
to find what other languages are supported. Make sure to add
- ada to the option if you recompile
- GCC.
+ ada to the option if you recompile
+ GCC.
@@ -356,7 +356,7 @@ rm -v testgnat*
mv -v /usr/lib/*gdb.py ...: The installation
- stage puts some files used by gdb under the
+ stage puts some files used by gdb under the
/usr/lib directory. This generates
spurious error messages when performing ldconfig. This
command moves the files to another location.
@@ -456,7 +456,7 @@ rm -v testgnat*
is useful for renaming files to meet the standard
- Ada default file naming conventions.
+ Ada default file naming conventions.
gnatchop
@@ -469,7 +469,7 @@ rm -v testgnat*
is used to remove files associated with a
- GNAT project.
+ GNAT project.
gnatclean
@@ -482,7 +482,7 @@ rm -v testgnat*
is intended for locating definition and/or references to
- specified entities in a GNAT project.
+ specified entities in a GNAT project.
gnatfind
@@ -531,7 +531,7 @@ rm -v testgnat*
gnatmake
- is the Ada compiler, which performs
+ is the Ada compiler, which performs
compilation, binding and linking.
@@ -545,7 +545,7 @@ rm -v testgnat*
will list the files associated with a
- GNAT project.
+ GNAT project.
gnatname
@@ -557,7 +557,7 @@ rm -v testgnat*
gnatprep
- is the GNAT external preprocessor.
+ is the GNAT external preprocessor.
gnatprep
diff --git a/archive/lib32-check.xml b/archive/lib32-check.xml
index d1f0998dc2..e8f6106a82 100644
--- a/archive/lib32-check.xml
+++ b/archive/lib32-check.xml
@@ -22,7 +22,7 @@
Introduction to lib32-Check
- The Check package was already installed in
+ The Check package was already installed in
LFS, but the lib32 instructions are missing from MLFS which is needed for
lib32-. If you are doing multilib, install
this.
@@ -47,7 +47,7 @@
lib32 Installation of Check
- Install lib32-Check by running the following
+ Install lib32-Check by running the following
commands:
@@ -107,7 +107,7 @@ ldconfig
libcheck.so
- contains functions that allow Check to
+ contains functions that allow Check to
be called from a test program
diff --git a/archive/libvk.xml b/archive/libvk.xml
index fbf4a29aa8..d8961f7b88 100644
--- a/archive/libvk.xml
+++ b/archive/libvk.xml
@@ -21,7 +21,7 @@
Introduction to Vulkan-Loader
- The Vulkan-Loader package contains a library
+ The Vulkan-Loader package contains a library
which provides the Vulkan API and provides core support for graphics
drivers for Vulkan.
@@ -68,7 +68,7 @@
- Install Vulkan-Loader by running the following
+ Install Vulkan-Loader by running the following
commands:
@@ -98,7 +98,7 @@ ninja
lib32 Installation of Vulkan-Loader
- Install lib32-Vulkan-Loader by running
+ Install lib32-Vulkan-Loader by running
the following commands:
diff --git a/archive/luit.xml b/archive/luit.xml
index 43d2b3e218..1a42681f78 100644
--- a/archive/luit.xml
+++ b/archive/luit.xml
@@ -21,7 +21,7 @@
Introduction to luit
- The luit package is a filter
+ The luit package is a filter
that can be run between an arbitrary application and a UTF-8
terminal emulator. It will convert application output from the
locale’s encoding into UTF‐8, and convert terminal input from
@@ -54,7 +54,7 @@
Installation of luit
- Install luit by running the
+ Install luit by running the
following commands:
diff --git a/archive/nvidia.xml b/archive/nvidia.xml
index 3bc7f97a8b..e8cab066b7 100644
--- a/archive/nvidia.xml
+++ b/archive/nvidia.xml
@@ -24,7 +24,7 @@
Introduction to NVIDIA
- The NVIDIA proprietary driver contains
+ The NVIDIA proprietary driver contains
firmware, kernel drivers, userland drivers pertaining to OpenGL,
Vulkan, and hardware acceleration, and provides useful utilites.
@@ -96,8 +96,8 @@
- Make sure to execute the following command when an Xorg
- instance isn't running, or else the driver will
+ Make sure to execute the following command when an Xorg
+ instance isn't running, or else the driver will
complain and quit. Alternatively, you can pass
--allow-installation-with-running-driver --no-x-check to
override NVIDIA's warnings. This is not recommended as it skips
@@ -126,7 +126,7 @@
- Install x86_64 NVIDIA by running the following
+ Install x86_64 NVIDIA by running the following
commands as the root user:
@@ -137,7 +137,7 @@
If you are only interested in the 32-bit driver, install x86
- NVIDIA by running the following
+ NVIDIA by running the following
commands as the root user:
@@ -183,7 +183,7 @@
When you update the kernel, you will also need to reinstall the
- NVIDIA driver.
+ NVIDIA driver.
@@ -344,7 +344,7 @@
nvidia-bug-report.sh
- is the NVIDIA bug reporting shell script.
+ is the NVIDIA bug reporting shell script.
nvidia-bug-report.sh
@@ -393,8 +393,8 @@
nvidia-installer
- installs, upgrades, and uninstalls the NVIDIA
- driver (running the runfile directly is
+ installs, upgrades, and uninstalls the NVIDIA
+ driver (running the runfile directly is
recommended)
@@ -407,8 +407,8 @@
nvidia-modprobe
- creates Linux device files and loads the NVIDIA
- kernel module
+ creates Linux device files and loads the NVIDIA
+ kernel module
nvidia-modprobe
@@ -444,7 +444,7 @@
nvidia-powerd
- provides support for the NVIDIA
+ provides support for the NVIDIA
Dynamic Boost feature
@@ -495,8 +495,8 @@
nvidia-uninstall
- installs, upgrades, and uninstalls the NVIDIA
- driver (running the runfile directly is
+ installs, upgrades, and uninstalls the NVIDIA
+ driver (running the runfile directly is
recommended)
@@ -509,9 +509,9 @@
nvidia-xconfig
- manipulates X11 configuration files
- to allow the NVIDIA driver to be used
- when starting X11
+ manipulates X11 configuration files
+ to allow the NVIDIA driver to be used
+ when starting X11
nvidia-xconfig
@@ -523,7 +523,7 @@
libEGL_nvidia.so
- provides NVIDIA implementations
+ provides NVIDIA implementations
of OpenGL functionality
@@ -560,7 +560,7 @@
libGLX_nvidia.so
- provides NVIDIA implementations
+ provides NVIDIA implementations
of OpenGL functionality
@@ -597,8 +597,8 @@
libglxserver_nvidia.so
- is the NVIDIA GLX extension module for
- X11
+ is the NVIDIA GLX extension module for
+ X11
libglxserver_nvidia.so
@@ -670,7 +670,7 @@
libnvidia-egl-wayland.so
- provides client-side Wayland EGL
+ provides client-side Wayland EGL
application support
@@ -708,7 +708,7 @@
provides an interface to capture and optionally encode the
- framebuffer of an X11 server screen
+ framebuffer of an X11 server screen
libnvidia-fbc.so
@@ -828,7 +828,7 @@
libnvidia-opencl.so
- provides NVIDIA's implementation of
+ provides NVIDIA's implementation of
the OpenCL API standard
@@ -907,8 +907,8 @@
libnvidia-tls.so
- provides thread local storage support for the NVIDIA
- OpenGL libraries
+ provides thread local storage support for the NVIDIA
+ OpenGL libraries
libnvidia-tls.so
@@ -921,7 +921,7 @@
is required for nvidia-settings on
- Wayland
+ Wayland
libnvidia-wayland-client.so
@@ -945,7 +945,7 @@
libvdpau_nvidia.so
- provides the NVIDIA implementation for
+ provides the NVIDIA implementation for
the VDPAU library
@@ -958,7 +958,7 @@
_nvngx.dll
- provides DLSS support for use with Wine
+ provides DLSS support for use with Wine
_nvngx.dll
@@ -982,7 +982,7 @@
nvidia-drm_gbm.so
- is the NVIDIA implementation of GBM
+ is the NVIDIA implementation of GBM
nvidia-drm_gbm.so
@@ -994,8 +994,8 @@
nvidia_drv.so
- is the NVIDIAX11
- driver
+ is the NVIDIA X11
+ driver
nvidia_drv.so
diff --git a/archive/pipewire.xml b/archive/pipewire.xml
index deaba5bdd2..509b9b2377 100644
--- a/archive/pipewire.xml
+++ b/archive/pipewire.xml
@@ -21,7 +21,7 @@
Introduction to Pipewire
- The pipewire package contains a server and
+ The pipewire package contains a server and
userspace API to handle multimedia pipelines. This includes a universal
API to connect to multimedia devices, as well as sharing multimedia
files between applications.
@@ -103,7 +103,7 @@
-->
- Install pipewire by running the following
+ Install pipewire by running the following
commands:
diff --git a/archive/spirv-headers.xml b/archive/spirv-headers.xml
index 5f035b7f76..8e02d71e15 100644
--- a/archive/spirv-headers.xml
+++ b/archive/spirv-headers.xml
@@ -21,7 +21,7 @@
Introduction to SPIRV-Headers
- The SPIRV-Headers package contains headers
+ The SPIRV-Headers package contains headers
that allow for applications to the SPIR-V language and instruction set
with Vulkan. SPIR-V is a binary intermediate language for representing
graphical shader stages and compute kernels for multiple Khronos APIs,
@@ -63,7 +63,7 @@
- Install SPIRV-Headers by running the following
+ Install SPIRV-Headers by running the following
commands:
diff --git a/archive/spirv-tools.xml b/archive/spirv-tools.xml
index f0fbc1cf4a..2bce75a9e1 100644
--- a/archive/spirv-tools.xml
+++ b/archive/spirv-tools.xml
@@ -21,7 +21,7 @@
Introduction to SPIRV-Tools
- The SPIRV-Tools package contains libraries
+ The SPIRV-Tools package contains libraries
and utilities for processing SPIR-V modules.
@@ -63,7 +63,7 @@
- Install SPIRV-Tools by running the following
+ Install SPIRV-Tools by running the following
commands:
@@ -96,7 +96,7 @@ ninja
lib32 Installation of SPIRV-Tools
- Install lib32-SPIRV-Tools by running the following
+ Install lib32-SPIRV-Tools by running the following
commands:
diff --git a/archive/twm.xml b/archive/twm.xml
index 926aa12a06..8738efe03a 100644
--- a/archive/twm.xml
+++ b/archive/twm.xml
@@ -26,7 +26,7 @@
Introduction to twm
- The twm package contains a very minimal
+ The twm package contains a very minimal
window manager.
@@ -87,7 +87,7 @@
Installation of twm
- Install twm by running the
+ Install twm by running the
following commands:
@@ -111,7 +111,7 @@ make
Command Explanationssed -i -e '/^rcdir =/s...: This command ensures
- the twm configuration file gets installed in
+ the twm configuration file gets installed in
the proper location.
diff --git a/archive/vkheaders.xml b/archive/vkheaders.xml
index 25c1b118c4..b7d390ed73 100644
--- a/archive/vkheaders.xml
+++ b/archive/vkheaders.xml
@@ -21,7 +21,7 @@
Introduction to Vulkan-headers
- The Vulkan-Headers package contains a set of
+ The Vulkan-Headers package contains a set of
header files necessary to build and link applications against the Vulkan
API.
@@ -52,7 +52,7 @@
Installation of Vulkan-Headers
- Install Vulkan-Headers by running the following
+ Install Vulkan-Headers by running the following
commands:
diff --git a/archive/wireplumber.xml b/archive/wireplumber.xml
index 7b5be185c1..714046dc74 100644
--- a/archive/wireplumber.xml
+++ b/archive/wireplumber.xml
@@ -21,8 +21,8 @@
Introduction to Wireplumber
- The Wireplumber package contains a session and
- policy manager for Pipewire.
+ The Wireplumber package contains a session and
+ policy manager for Pipewire.
@@ -58,7 +58,7 @@
Installation of Wireplumber
- Install Wireplumber by running the following
+ Install Wireplumber by running the following
commands:
diff --git a/archive/x7legacy.xml b/archive/x7legacy.xml
index 2935ed80e5..6ee708df3d 100644
--- a/archive/x7legacy.xml
+++ b/archive/x7legacy.xml
@@ -46,11 +46,11 @@
Introduction to Xorg Legacy
- Xorg's ancestor (X11R1, in 1987) at
+ Xorg's ancestor (X11R1, in 1987) at
first only provided bitmap fonts, with a tool
(bdftopcf) to assist in their installation. With the
- introduction of xorg-server-1.19.0 and
- libXfont2 many people will not need them.
+ introduction of xorg-server-1.19.0 and
+ libXfont2 many people will not need them.
There are still a few old packages which might require, or benefit from,
these deprecated fonts and so the following packages are shown here.
diff --git a/archive/xclock.xml b/archive/xclock.xml
index de8ef92695..7952a0cd85 100644
--- a/archive/xclock.xml
+++ b/archive/xclock.xml
@@ -26,7 +26,7 @@
Introduction to xclock
- The xclock package contains a simple
+ The xclock package contains a simple
clock application which is used in the default xinit configuration.
@@ -82,7 +82,7 @@
Installation of xclock
- Install xclock by running the
+ Install xclock by running the
following commands:
diff --git a/archive/xterm.xml b/archive/xterm.xml
index 1dd8a15b15..dc1f49bd5e 100644
--- a/archive/xterm.xml
+++ b/archive/xterm.xml
@@ -26,7 +26,7 @@
Introduction to xterm
- xterm is a terminal emulator for
+ xterm is a terminal emulator for
the X Window System.
@@ -97,7 +97,7 @@
Installation of xterm
- Install xterm by running the
+ Install xterm by running the
following commands:
@@ -155,7 +155,7 @@ cp -v *.desktop /usr/share/applications/
make install-ti: This command installs corrected
terminfo description files for use with
- xterm.
+ xterm.
-->
diff --git a/book/bookinfo.xml b/book/bookinfo.xml
index bff2b5d91c..0271e11b72 100644
--- a/book/bookinfo.xml
+++ b/book/bookinfo.xml
@@ -49,8 +49,8 @@
This book introduces and guides the reader through additions to the
- system like Steam,
- Wine, and their dependencies after the
+ system like Steam,
+ Wine, and their dependencies after the
LFS or Multilib-LFS book on x86_64 systems.
diff --git a/book/organization.xml b/book/organization.xml
index 29bfe75560..d5aff1bdc7 100644
--- a/book/organization.xml
+++ b/book/organization.xml
@@ -26,28 +26,26 @@
This section is dedicated to covering dependencies that are shared
- between Steam and Wine.
- As it turns out, there are quite a lot of
- dependencies they both depend on. Anything specific to
- Steam and Wine are covered
- in their respective chapters.
+ between Steam and Wine. As it turns out, there are quite a lot of
+ dependencies they both depend on. Anything specific to Steam and
+ Wine are covered in their respective chapters.
Part III - Steam
- This part details how to install Steam
- and the linear line of dependencies required, as well as some
- configuration for certain packages.
+ This part details how to install Steam and the linear line of
+ dependencies required, as well as some configuration for certain
+ packages.
Part IV - Wine
- This section goes over installing a toolchain called
- MinGW-w64, some of the packages necessary to both compile
- Wine and use it, and lastly how to compile
- Wine and configure it.
+ This section goes over installing a toolchain called
+ MinGW-w64, some of the packages necessary to both compile
+ Wine and use it, and lastly how to compile
+ Wine and configure it.
Part V - Quality of Life
diff --git a/book/preface.xml b/book/preface.xml
index 81ba43f6cd..ec16d81f30 100644
--- a/book/preface.xml
+++ b/book/preface.xml
@@ -12,11 +12,11 @@
Sometime after my first install of LFS, I had a question that others had:
- how do I install Steam on this system? I kept
+ how do I install Steam on this system? I kept
that thought in the back of my head as I went for Beyond LFS, a book that
covered a good number of packages I needed. However, the issue of
- Steam was not cleared up yet. So I just tried to
- install the Steam tarball. Because I did not
+ Steam was not cleared up yet. So I just tried to
+ install the Steam tarball. Because I did not
have 32-bit libraries, this ended in failure.
@@ -34,12 +34,12 @@
Rahul Chandra in the same thread mentioned his scripts for his distro,
Tucana. These scripts gave me a basic idea of how to do lib32 installations
for BLFS packages which were necessary for
- Steam.. While this wasn't exactly difficult,
+ Steam.. While this wasn't exactly difficult,
it was a big timesink as I had to manually type in all the lib32
compilation options to successfully build 32-bit libraries. Even after
having built all the 32-bit libraries required, a few more fixes and files
were necessary. After about a week, I managed to get
- Steam working. I realized that this was a lot of
+ Steam working. I realized that this was a lot of
work, and many users who'd want to do the same thing would get stuck and
not know what to do. In the worst case, they'd give up before even reaching
their goal. I had made a pretty lackluster stream
series that included that installation of
- Wine, not just Steam.
+ Wine, not just Steam.
My general idea was to compile all the stream footage (roughly 40 GB worth)
into a single video master guide. When some time passed, I came to the
conclusion that for a installation guide for two complex packages on an LFS
diff --git a/book/whoread.xml b/book/whoread.xml
index ec365090c6..6f91365258 100644
--- a/book/whoread.xml
+++ b/book/whoread.xml
@@ -13,8 +13,8 @@
This book is aimed towards users who want to use a system following
- the Linux From Scratch book but also want to use Steam
- and/or Wine.
+ the Linux From Scratch book but also want to use Steam
+ and/or Wine.
The official Linux From Scratch and Beyond Linux From Scratch books
do not support these two packages. However, users should still have
both the choice and an easy to follow guide to get these packages
diff --git a/introduction/multilib/mesonfiles.xml b/introduction/multilib/mesonfiles.xml
index 407f881ff6..91b1a748e7 100644
--- a/introduction/multilib/mesonfiles.xml
+++ b/introduction/multilib/mesonfiles.xml
@@ -15,16 +15,16 @@
Introduction to Meson Toolchain Files
- Most applications that rely on the Meson
+ Most applications that rely on the Meson
build system have decent support for cross compilation, ie. compiling
32-bit binaries on a 64-bit system. It can be as easy as setting the
CC, CXX, and PKG_CONFIG_PATH
variables before using the meson setup ..
command to compile 32-bit binaries on a 64-bit system.
However, some projects are more complicated for many different
- reasons, leading to the necessity of Meson
- toolchain files. They specify compilers,
- options that should be invoked, the pkg-conf
+ reasons, leading to the necessity of Meson
+ toolchain files. They specify compilers,
+ options that should be invoked, the pkg-conf
binary (or rather symlink that uses a certain personality file) to use,
llvm-config to use, etc. This is required for many
Meson projects, especially if you have followed BLFS before this book.
@@ -32,7 +32,7 @@
- There are two Meson files: the cross
+ There are two Meson files: the cross
toolchain file and the native toolchain file. There are different situations
for using either.
diff --git a/introduction/welcome/rationale.xml b/introduction/welcome/rationale.xml
index 3207dc67c9..a6e07541eb 100644
--- a/introduction/welcome/rationale.xml
+++ b/introduction/welcome/rationale.xml
@@ -27,8 +27,8 @@
the book but rather in the BLFS book. There are multiple reasons
for this, but the most notable one is the packages that aren't in
the book aren't important for the main packages in the book, those
- being Steam and
- Wine. They are still listed anyway if users
+ being Steam and
+ Wine. They are still listed anyway if users
want more support out of the specific packages not specific to the main
packages, like media playback for example. Another reason for
packages not being in the book is that the packages take a lot
@@ -64,10 +64,10 @@
- Install ALSA Library by
+ Install ALSA Library by
running the following commands:
@@ -123,7 +123,7 @@ esac
make
- If you have Doxygen installed and you wish to
+ If you have Doxygen installed and you wish to
build the library API documentation, run the following
commands from the top-level directory of the source tree:
diff --git a/shareddeps/audio/alsa-plugins.xml b/shareddeps/audio/alsa-plugins.xml
index 7fc5113446..91483aa095 100644
--- a/shareddeps/audio/alsa-plugins.xml
+++ b/shareddeps/audio/alsa-plugins.xml
@@ -21,7 +21,7 @@
Introduction to ALSA Plugins
- The ALSA Plugins package contains
+ The ALSA Plugins package contains
plugins for various audio libraries and sound servers.
@@ -65,7 +65,7 @@
Installation of ALSA Plugins
- Install ALSA Plugins by
+ Install ALSA Plugins by
running the following commands:
@@ -88,7 +88,7 @@ make
lib32 Installation of ALSA Plugins
- Install 32-bit ALSA Plugins by
+ Install 32-bit ALSA Plugins by
running the following commands:
@@ -170,8 +170,8 @@ ldconfig
libasound_module_pcm_oss
- Allows native ALSA applications to
- run on OSS
+ Allows native ALSA applications to
+ run on OSS
libasound_module_pcm_oss
@@ -208,7 +208,7 @@ ldconfig
libasound_module_pcm_jack
- Allows native ALSA applications to
+ Allows native ALSA applications to
work with jackd
@@ -221,8 +221,8 @@ ldconfig
libasound_module_pcm_pulse
- Allows native ALSA applications
- to access a PulseAudio sound
+ Allows native ALSA applications
+ to access a PulseAudio sound
daemon
diff --git a/shareddeps/audio/alsa-utils.xml b/shareddeps/audio/alsa-utils.xml
index fe03a4c3cd..6047e1f8f7 100644
--- a/shareddeps/audio/alsa-utils.xml
+++ b/shareddeps/audio/alsa-utils.xml
@@ -22,7 +22,7 @@
Introduction to ALSA Utilities
- The ALSA Utilities package contains
+ The ALSA Utilities package contains
various utilities which are useful for controlling your sound
card.
@@ -78,7 +78,7 @@
-->
- Install ALSA Utilities by
+ Install ALSA Utilities by
running the following commands:
@@ -109,7 +109,7 @@ make
--disable-alsaconf: This switch disables building
the alsaconf configuration tool which is incompatible
- with Udev.
+ with Udev.
@@ -166,7 +166,7 @@ make
The alsactl program is normally run from a
- standard udev rule. The first time it
+ standard udev rule. The first time it
is run, it will complain that there is no state in
/var/lib/alsa/asound.state. You can prevent
this by running the following command as the
@@ -177,7 +177,7 @@ make
The volume settings should be restored from the saved state by
- Udev when the device is detected
+ Udev when the device is detected
(during boot or when plugged in for USB devices).
- Install libvorbis by running the following
+ Install libvorbis by running the following
commands:
@@ -94,7 +94,7 @@ install -v -m644 doc/Vorbis* /usr/share/doc/libvorbis-&libvorbis-version;lib32 Installation of libvorbis
- Install lib32-libvorbis by running the following
+ Install lib32-libvorbis by running the following
commands:
diff --git a/shareddeps/audio/opus.xml b/shareddeps/audio/opus.xml
index 3634fdeddf..a05398b692 100644
--- a/shareddeps/audio/opus.xml
+++ b/shareddeps/audio/opus.xml
@@ -21,7 +21,7 @@
Introduction to Opus
- Opus is a lossy audio compression format
+ Opus is a lossy audio compression format
developed by the Internet Engineering Task Force (IETF) that is
particularly suitable for interactive speech and audio transmission over
the Internet. This package provides the Opus development library and
@@ -55,7 +55,7 @@
Installation of Opus
- Install Opus by running the following
+ Install Opus by running the following
commands:
@@ -84,7 +84,7 @@ ninja
lib32 Installation of Opus
- Install lib32-Opus by running the following
+ Install lib32-Opus by running the following
commands:
diff --git a/shareddeps/audio/pulseaudio.xml b/shareddeps/audio/pulseaudio.xml
index a6013921d5..31cb21c6f9 100644
--- a/shareddeps/audio/pulseaudio.xml
+++ b/shareddeps/audio/pulseaudio.xml
@@ -22,7 +22,7 @@
Introduction to PulseAudio
- PulseAudio is a sound system for POSIX OSes,
+ PulseAudio is a sound system for POSIX OSes,
meaning that it is a proxy for sound applications. It allows you to do
advanced operations on your sound data as it passes between your
application and your hardware. Things like transferring the audio to a
@@ -100,7 +100,7 @@
sed '/doxygen/d' -i meson.build
-->
- Install PulseAudio by running the following
+ Install PulseAudio by running the following
commands:
@@ -129,7 +129,7 @@ ninja
url="https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/"/>
for more information.
While still as the root
- user, remove the D-Bus configuration file
+ user, remove the D-Bus configuration file
for the system wide daemon to avoid creating unnecessary system
users and groups:
@@ -142,7 +142,7 @@ ninja
lib32 Installation of PulseAudio
- Install lib32-PulseAudio by running the following
+ Install lib32-PulseAudio by running the following
commands:
@@ -191,7 +191,7 @@ ldconfig
-D tests=false: This switch disables building
- tests as they require Check.
+ tests as they require Check.
You may have to configure the audio system. You can start
- pulseaudio in command line mode using
+ pulseaudio in command line mode using
pulseaudio -C and then list various
information and change settings. See
man pulse-cli-syntax.
@@ -270,14 +270,14 @@ ldconfig
usermod -a -G audio <username>
- If pulseaudio was working but you no-longer
+ If pulseaudio was working but you no-longer
have sound, after checking for hardware issues (speakers or headphones
not connected, external amplifier not connected) you may need to fix it.
One suggestion is to close the application, such as
- firefox where sound has stopped working, then
+ firefox where sound has stopped working, then
run: pactl list short sinks followed by:
pacmd set-default-sink <sink #> and then
restart the application.
@@ -344,7 +344,7 @@ ldconfig
esdcompat
- is the PulseAudio ESD wrapper script.
+ is the PulseAudio ESD wrapper script.
esdcompat
@@ -358,7 +358,7 @@ ldconfig
plays back or records raw or encoded audio streams on a
- PulseAudio sound server
+ PulseAudio sound server
pacat
@@ -370,7 +370,7 @@ ldconfig
pacmd
- is a tool used to reconfigure a PulseAudio
+ is a tool used to reconfigure a PulseAudio
sound server during runtime
@@ -383,7 +383,7 @@ ldconfig
pactl
- is used to control a running PulseAudio
+ is used to control a running PulseAudio
sound server
@@ -396,7 +396,7 @@ ldconfig
padsp
- is the PulseAudio OSS Wrapper
+ is the PulseAudio OSS Wrapper
padsp
@@ -421,7 +421,7 @@ ldconfig
is used to play audio files on a
- PulseAudio sound server
+ PulseAudio sound server
paplay
@@ -458,7 +458,7 @@ ldconfig
is a tool that can be used to tell a local
- PulseAudio sound server to temporarily
+ PulseAudio sound server to temporarily
suspend access to the audio devices, to allow other applications
to access them directly
@@ -472,7 +472,7 @@ ldconfig
pax11publish
- is the PulseAudio
+ is the PulseAudio
X11 Credential Utility
@@ -486,7 +486,7 @@ ldconfig
is a shell script that prints various information relating to the
- Pulseaudio server currently in use
+ Pulseaudio server currently in use
pa-info
@@ -512,7 +512,7 @@ ldconfig
is an equalizer interface for
- PulseAudio equalizer sinks
+ PulseAudio equalizer sinks
(Requires fftw at build time)
@@ -526,7 +526,7 @@ ldconfig
start-pulseaudio-kde
- Starts PulseAudio and loads
+ Starts PulseAudio and loads
module-device-manager to use KDE routing policies.
@@ -539,7 +539,7 @@ ldconfig
start-pulseaudio-x11
- starts PulseAudio and registers it to
+ starts PulseAudio and registers it to
the X11 session manager
diff --git a/shareddeps/audio/speex.xml b/shareddeps/audio/speex.xml
index 7469607d5c..3bdd7dd5e4 100644
--- a/shareddeps/audio/speex.xml
+++ b/shareddeps/audio/speex.xml
@@ -21,7 +21,7 @@
Introduction to Speex
- Speex is an audio compression format
+ Speex is an audio compression format
designed specifically for speech. It is well-adapted to internet
applications and provides useful features that are not present in most
other CODECs.
@@ -76,7 +76,7 @@
- Install Speex by running the
+ Install Speex by running the
following commands:
@@ -121,7 +121,7 @@ popd
lib32 Installation of Speex
- Install lib32-Speex by running the
+ Install lib32-Speex by running the
following commands:
@@ -216,7 +216,7 @@ popd
speexdec
- decodes a Speex file and
+ decodes a Speex file and
produces a WAV or raw file
@@ -229,7 +229,7 @@ popd
speexenc
- encodes a WAV or raw file using Speex
+ encodes a WAV or raw file using Speex
speexenc
@@ -254,7 +254,7 @@ popd
is a speech processing library that goes along with the
- Speex codec
+ Speex codec
libspeexdsp.so
diff --git a/shareddeps/checkpoint/whatnow.xml b/shareddeps/checkpoint/whatnow.xml
index 6ec9740bab..7367418959 100644
--- a/shareddeps/checkpoint/whatnow.xml
+++ b/shareddeps/checkpoint/whatnow.xml
@@ -27,7 +27,7 @@
and not accidentally lock yourself inside of it without a hard reboot. The
installation of those components is not covered in this book, as the
specific components will depend on if you plan to use
- X11, Wayland, or
+ X11, Wayland, or
both. This page acts as a simple nudge to help point you in the right
direction. When you are done setting up your graphical environment, you can
come back and continue with the next chapters.
@@ -53,7 +53,7 @@
It is recommended to read up on the BLFS page Xorg-7 Testing and
Configuration. It is pretty comprehensive. However, using with X11 requires a
+ linkend="nvidia"/> with X11 requires a
slightly different setup, and there may be extra information you wish to
know.
@@ -63,9 +63,9 @@
Using a conventional /etc/X11/xorg.conf
- can lead to issues, if X11 manages to
- even start. In order to use the NVIDIA
- driver when starting X11, run the following
+ can lead to issues, if X11 manages to
+ even start. In order to use the NVIDIA
+ driver when starting X11, run the following
command as the &root; user:
@@ -118,8 +118,8 @@
If you compiled Zink in , chances are
- X11 or any
- Wayland compositors will use the Gallium3D
+ X11 or any
+ Wayland compositors will use the Gallium3D
driver meant for your GPU specifically. You can override this by
setting the following variable:
@@ -242,7 +242,7 @@
A compositor talks with and can change
what is seen on screen. Compositors can add animations, borders,
shadows, opacity, etc. to windows. They can also enable vsync.
- Though compositors aren't needed on X11,
+ Though compositors aren't needed on X11,
they make the graphical environment look nicer. These visual
enhancements can be GPU-intensive if the GPU is weak or the graphics
driver isn't that performantIf you decide to use a
@@ -276,9 +276,9 @@
Wayland
- Wayland is much simpler to set up than X11.
+ Wayland is much simpler to set up than X11.
You should still read the X11 section above, as much of the information
- is also relevant to Wayland. There are a few
+ is also relevant to Wayland. There are a few
changes, however.
@@ -288,10 +288,10 @@
You will only need to worry about the refresh rate if it's
applicable to you. You won't need to worry about making sure the
- NVIDIA driver is used when starting
- Wayland. However, read through the
+ NVIDIA driver is used when starting
+ Wayland. However, read through the
installation instructions for your chosen graphical environment, as
- they may have information regarding NVIDIA.
+ they may have information regarding NVIDIA.
Results can be shotty, and sometimes the environment won't be able to
start. Do your research first.
@@ -302,9 +302,9 @@
Window Managers, Desktop Environments, and Compositors
- Unlike on X11, the window manager and
+ Unlike on X11, the window manager and
compositor will always be combined on
- Wayland. Minimal graphical environments are
+ Wayland. Minimal graphical environments are
called compositors instead of window managers, but desktop environments
are still called desktop environments. For compositors, the only
additional components that need to be installed are a terminal and
@@ -315,10 +315,10 @@
Compositors
- Many X11 window managers do not support
- Wayland. There are some unofficial
+ Many X11 window managers do not support
+ Wayland. There are some unofficial
ports that use certain reusable frameworks which would
- be called an X11 compositor, like
+ be called an X11 compositor, like
wlroots (these are called compositor libraries). You can
try some ports if you wish but some of them do their own thing
@@ -326,7 +326,7 @@
- Native Wayland compositors include
+ Native Wayland compositors include
Hyprland,
Sway, and
Wayfire.
@@ -342,8 +342,8 @@
Go with GNOME or
KDE Plasma. They have
- good Wayland support. Like with
- X11, you can launch these using a display
+ good Wayland support. Like with
+ X11, you can launch these using a display
manager.
diff --git a/shareddeps/dps/basicx/other/cmake.xml b/shareddeps/dps/basicx/other/cmake.xml
index 66aa95e707..bfbac1c758 100644
--- a/shareddeps/dps/basicx/other/cmake.xml
+++ b/shareddeps/dps/basicx/other/cmake.xml
@@ -21,11 +21,11 @@
Introduction to CMake
- The CMake package contains a modern
+ The CMake package contains a modern
toolset used for generating Makefiles. It is a successor of the
auto-generated configure script and aims to
be platform- and compiler-independent. A significant user of
- CMake is KDE
+ CMake is KDE
since version 4.
@@ -87,7 +87,7 @@
-->
- Install CMake by running the following
+ Install CMake by running the following
commands:
@@ -156,13 +156,13 @@ make
--no-system-jsoncpp and
--no-system-cppdap: These switches remove the
- JSON-C++ library from the list of system
+ JSON-C++ library from the list of system
libraries. A bundled version of that library is used instead.
--no-system-librhash: This switch removes the
- librhash library from the list of system
+ librhash library from the list of system
libraries used. A bundled version of that library is used instead.
@@ -174,7 +174,7 @@ make
: This switch enables performing the
- CMake bootstrap with multiple jobs
+ CMake bootstrap with multiple jobs
at one time.
@@ -237,7 +237,7 @@ make
cpack
- is the CMake packaging program
+ is the CMake packaging program
cpack
diff --git a/shareddeps/dps/basicx/other/dbus.xml b/shareddeps/dps/basicx/other/dbus.xml
index 2356973e9b..2b1768984d 100644
--- a/shareddeps/dps/basicx/other/dbus.xml
+++ b/shareddeps/dps/basicx/other/dbus.xml
@@ -21,7 +21,7 @@
Introduction to D-Bus
- Even though D-Bus was built in LFS, there are
+ Even though D-Bus was built in LFS, there are
some features provided by the package that other GLFS packages need, but
their dependencies didn't fit into LFS.
@@ -128,7 +128,7 @@
If any packages install a
- D-Bus.service
+ D-Bus .service
file outside of the standard /usr/share/dbus-1/services directory,
that directory should be added to the local session configuration.
@@ -171,8 +171,8 @@ EOF
Note that this boot script only starts the system-wide
- D-Bus daemon. Each user requiring access to
- D-Bus services will also need to run a
+ D-Bus daemon. Each user requiring access to
+ D-Bus services will also need to run a
session daemon as well. There are many methods you can use to start a
session daemon using the dbus-launch command. Review
the dbus-launch man page for details about the
@@ -295,7 +295,7 @@ kill $DBUS_SESSION_BUS_PID
dbus-daemon
- is the D-Bus message bus daemon
+ is the D-Bus message bus daemon
dbus-daemon
@@ -322,7 +322,7 @@ kill $DBUS_SESSION_BUS_PID
is used to monitor messages going through a
- D-Bus message bus
+ D-Bus message bus
dbus-monitor
@@ -334,7 +334,7 @@ kill $DBUS_SESSION_BUS_PID
dbus-run-session
- starts a process as a new D-Bus session
+ starts a process as a new D-Bus session
dbus-run-session
@@ -346,7 +346,7 @@ kill $DBUS_SESSION_BUS_PID
dbus-send
- is used to send a message to a D-Bus
+ is used to send a message to a D-Bus
message bus
@@ -359,9 +359,9 @@ kill $DBUS_SESSION_BUS_PID
dbus-test-tool
- is a D-Bus traffic generator and test
+ is a D-Bus traffic generator and test
tool; it is a multi-purpose tool for debugging and profiling
- D-Bus
+ D-Bus
dbus-test-tool
@@ -374,7 +374,7 @@ kill $DBUS_SESSION_BUS_PID
is used to update the environment used for
- D-Bus session services;
+ D-Bus session services;
it updates the list of environment variables used by
dbus-daemon --session when it activates session
services without using systemd
@@ -403,8 +403,8 @@ kill $DBUS_SESSION_BUS_PID
contains the API functions used by the
- D-Bus message daemon.
- D-Bus is first a library that provides
+ D-Bus message daemon.
+ D-Bus is first a library that provides
one-to-one communication between any two applications;
dbus-daemon is an application that uses this
library to implement a message bus daemon
diff --git a/shareddeps/dps/basicx/other/fontconfig.xml b/shareddeps/dps/basicx/other/fontconfig.xml
index 951e49e718..07cb8a18b6 100644
--- a/shareddeps/dps/basicx/other/fontconfig.xml
+++ b/shareddeps/dps/basicx/other/fontconfig.xml
@@ -22,7 +22,7 @@
Introduction to Fontconfig
- The Fontconfig package contains
+ The Fontconfig package contains
a library and support programs used for configuring and
customizing font access.
@@ -70,7 +70,7 @@
Installation of Fontconfig
- Install Fontconfig by running the following
+ Install Fontconfig by running the following
commands:
@@ -98,7 +98,7 @@ ninja
lib32 Installation of Fontconfig
- Install lib32-Fontconfig by running the
+ Install lib32-Fontconfig by running the
following commands:
@@ -161,7 +161,7 @@ ldconfig
Configuration Information
- The main configuration file for Fontconfig is
+ The main configuration file for Fontconfig is
/etc/fonts/fonts.conf. Generally you do not want
to edit this file. It will also read /etc/fonts/local.conf
and any files in /etc/fonts/conf.d.
@@ -169,7 +169,7 @@ ldconfig
(or update) the /etc/fonts/local.conf file with your
local information or add a new file in
/etc/fonts/conf.d. The default
- location of fonts in Fontconfig is:
+ location of fonts in Fontconfig is:
@@ -192,7 +192,7 @@ ldconfig
- Fontconfig also ships many example
+ Fontconfig also ships many example
configuration files in the
/usr/share/fontconfig/conf.avail
directory. Symlinking specific files to
@@ -211,7 +211,7 @@ ldconfig
- More information about configuring Fontconfig
+ More information about configuring Fontconfig
can be found in the user's manual in .
@@ -366,7 +366,7 @@ ldconfig
libfontconfig
- contains functions used by the Fontconfig
+ contains functions used by the Fontconfig
programs and also by other programs to configure or customize font
access
diff --git a/shareddeps/dps/basicx/other/freetype2-pass1.xml b/shareddeps/dps/basicx/other/freetype2-pass1.xml
index a7d7beb86b..a81e79d2d1 100644
--- a/shareddeps/dps/basicx/other/freetype2-pass1.xml
+++ b/shareddeps/dps/basicx/other/freetype2-pass1.xml
@@ -25,15 +25,15 @@
Introduction to FreeType2 - Pass 1
- The FreeType2 package contains
+ The FreeType2 package contains
a library which allows applications to properly render
- TrueType fonts.
+ TrueType fonts.
This package has a circular dependency on , so this package must be installed first,
- harfBuzz second, then lastly this
+ harfBuzz second, then lastly this
package again. This is the first pass.
@@ -132,9 +132,9 @@ rm -v /usr/share/doc/freetype-&freetype2-version;/freetype-config.1<
: If
- harfbuzz is installed prior to
- freetype without
- freetype support, use this switch to avoid a
+ harfbuzz is installed prior to
+ freetype without
+ freetype support, use this switch to avoid a
build failure.
@@ -182,7 +182,7 @@ rm -v /usr/share/doc/freetype-&freetype2-version;/freetype-config.1<
freetype-config
- is used to get FreeType compilation
+ is used to get FreeType compilation
and linking information
diff --git a/shareddeps/dps/basicx/other/freetype2-pass2.xml b/shareddeps/dps/basicx/other/freetype2-pass2.xml
index 2280f99423..8ae744a22a 100644
--- a/shareddeps/dps/basicx/other/freetype2-pass2.xml
+++ b/shareddeps/dps/basicx/other/freetype2-pass2.xml
@@ -95,9 +95,9 @@
: If
- harfbuzz is installed prior to
- freetype without
- freetype support, use this switch to avoid a
+ harfbuzz is installed prior to
+ freetype without
+ freetype support, use this switch to avoid a
build failure.
@@ -145,7 +145,7 @@
freetype-config
- is used to get FreeType compilation
+ is used to get FreeType compilation
and linking information
diff --git a/shareddeps/dps/basicx/other/gnutls.xml b/shareddeps/dps/basicx/other/gnutls.xml
index 1cffc22fa1..fa30d3123d 100644
--- a/shareddeps/dps/basicx/other/gnutls.xml
+++ b/shareddeps/dps/basicx/other/gnutls.xml
@@ -21,9 +21,9 @@
Introduction to GnuTLS
- The GnuTLS package contains libraries and
+ The GnuTLS package contains libraries and
userspace tools which provide a secure layer over a reliable transport
- layer. Currently the GnuTLS library implements
+ layer. Currently the GnuTLS library implements
the proposed standards by the IETF's TLS working group. Quoting from the
TLS 1.3 protocol specification
@@ -39,7 +39,7 @@
- GnuTLS provides support for TLS 1.3, TLS 1.2,
+ GnuTLS provides support for TLS 1.3, TLS 1.2,
TLS 1.1, TLS 1.0, and (optionally) SSL 3.0 protocols. It also supports
TLS extensions, including server name and max record size. Additionally,
the library supports authentication using the SRP protocol, X.509
@@ -95,7 +95,7 @@
Note that if you do not install , a
- version shipped in the GnuTLS tarball will be
+ version shipped in the GnuTLS tarball will be
used instead.
@@ -105,7 +105,7 @@
Installation of GnuTLS
- Install GnuTLS by running the
+ Install GnuTLS by running the
following commands:
diff --git a/shareddeps/dps/basicx/other/harfbuzz.xml b/shareddeps/dps/basicx/other/harfbuzz.xml
index 0195e0304b..9397b3b67d 100644
--- a/shareddeps/dps/basicx/other/harfbuzz.xml
+++ b/shareddeps/dps/basicx/other/harfbuzz.xml
@@ -22,7 +22,7 @@
Introduction to HarfBuzz
- The HarfBuzz package contains an OpenType text
+ The HarfBuzz package contains an OpenType text
shaping engine.
@@ -58,7 +58,7 @@
Installation of HarfBuzz
- Install HarfBuzz by running the following
+ Install HarfBuzz by running the following
commands:
@@ -89,7 +89,7 @@ ninja
lib32 Installation of HarfBuzz
- Install lib32-HarfBuzz by running the following
+ Install lib32-HarfBuzz by running the following
commands:
@@ -125,14 +125,14 @@ ldconfig
-D cairo=disabled: This switch forces this package
- to not link against Cairo for the lib32 build
- as it will mistakenly believe that lib32-Cairo
+ to not link against Cairo for the lib32 build
+ as it will mistakenly believe that lib32-Cairo
is installed if the 64-bit version is installed.
-D graphite2=disabled: This switch disables
- Graphite2 support, which isn't in GLFS.
+ Graphite2 support, which isn't in GLFS.
@@ -143,7 +143,7 @@ ldconfig
$HOME/.local/share/xorg/Xorg.0.log, about missing font
@@ -99,7 +99,7 @@
Generally, there is no specific configuration required for
- Xorg, but customization is possible. For
+ Xorg, but customization is possible. For
details, see below.
@@ -113,8 +113,8 @@
DRI is a framework for allowing software to access graphics hardware in
a safe and efficient manner. It is installed in
- X by default (using
- Mesa) if you have a supported video card.
+ X by default (using
+ Mesa) if you have a supported video card.
@@ -294,12 +294,12 @@ usermod -a -G video <user running xorg>
In order to use PRIME for GPU switching, make sure that you are using
Linux Kernel 3.4 or later (recommended). You will need latest DRI and
- DDX drivers for your hardware and Xorg Server
+ DDX drivers for your hardware and Xorg Server
1.13 or later.
- Xorg Server should load both GPU drivers
+ Xorg Server should load both GPU drivers
automatically. You can check that by running:
@@ -327,7 +327,7 @@ Provider 1: id: 0x56 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
- With the Xorg modesetting driver,
+ With the Xorg modesetting driver,
which is DRI3 capable, the above command is no longer
necessary. It does no harm however.
diff --git a/shareddeps/dps/x/xorg-server.xml b/shareddeps/dps/x/xorg-server.xml
index b59dc62e88..4f6928ab7c 100644
--- a/shareddeps/dps/x/xorg-server.xml
+++ b/shareddeps/dps/x/xorg-server.xml
@@ -25,7 +25,7 @@
Introduction to Xorg Server
- The Xorg Server is the core
+ The Xorg Server is the core
of the X Window system.
diff --git a/shareddeps/dps/x/xwayland.xml b/shareddeps/dps/x/xwayland.xml
index 94df63db5d..ad6f3a68be 100644
--- a/shareddeps/dps/x/xwayland.xml
+++ b/shareddeps/dps/x/xwayland.xml
@@ -21,7 +21,7 @@
Introduction to Xwayland
- The Xwayland package is an Xorg server
+ The Xwayland package is an Xorg server
running on top of the wayland server. It has been separated from the
main Xorg server package. It allows running X clients inside a
wayland session.
@@ -66,7 +66,7 @@
Installation of Xwayland
- Install xwayland by running the following
+ Install xwayland by running the following
commands:
diff --git a/shareddeps/drivers/aboutgl.xml b/shareddeps/drivers/aboutgl.xml
index 7e4616bd55..2aeb2c6a41 100644
--- a/shareddeps/drivers/aboutgl.xml
+++ b/shareddeps/drivers/aboutgl.xml
@@ -24,14 +24,14 @@
- So, Mesa came in and implemented drivers and
+ So, Mesa came in and implemented drivers and
functions for OpenGL. They also implement GLX and EGL which provide
- interfaces to window systems like Xorg.
+ interfaces to window systems like Xorg.
However, their method doesn't dispatch the calls in a vendor-neutral way.
For the most part, this approach is fine and doesn't lead to any issues.
- NVIDIA has decided that this was a bad enough
+ NVIDIA has decided that this was a bad enough
approach to warrant making another implementation of OpenGL called
- libglvnd. It only provides the implementations
+ libglvnd. It only provides the implementations
for OpenGL, OpenGL ES, GLX, and EGL. This had led to legacy OpenGL vs new
OpenGL on Linux.
@@ -50,7 +50,7 @@
This is only a problem for binary only packages and some
- CMake build systems. For this book and in
+ CMake build systems. For this book and in
BLFS, you shouldn't run into any of those issues unless you wish to use
, which specifically requires . SLFS aims to work around issues that arise from
@@ -62,7 +62,7 @@
url="https://www.shipofharkinian.com/">Ship of Harkinian, a PC
port of the Nintendo 64 game, Legend of Zelda: Ocarina of Time, links
against new OpenGL and will be broken with only
- Mesa installed; furthermore, trying to get
+ Mesa installed; furthermore, trying to get
around the issue by building from source also leads to many issues.
However, the binary of the PC port made from statically recompiling the
Nintendo 64 game, Legend of Zelda: Majora's Mask, called . If you want new OpenGL, support for some binary-only
packages, , and get past some
- CMake build systems, install . If you want a driver from , you can build that after
- libglvnd. Mesa will
- auto-detect libglvnd and will skip building
+ libglvnd. Mesa will
+ auto-detect libglvnd and will skip building
its OpenGL implementations.
@@ -113,11 +113,11 @@
GLES, specifically v2 and v3, are used sometimes, but mostly in one
- area. Such an area is in Wayland
+ area. Such an area is in Wayland
compositors and compositor libraries, such as
- Hyprland, Mutter,
- Wayfire, and
- Wlroots. While compositors can utilize
+ Hyprland, Mutter,
+ Wayfire, and
+ Wlroots. While compositors can utilize
Vulkan, most compositors require GLES rendering and don't offer a Vulkan
solution, or any other rendering API solution. GLESv1 on the otherhand
is an outdated specification of the GLES API that has been phased out
@@ -131,12 +131,12 @@
History of Wayland and GLES
- When the Wayland set of protocols were made, a
+ When the Wayland set of protocols were made, a
reference implementation had to be made for it to show what was possible,
and how to create a compositor for the new protocol. The result was
- Weston. For its rendering API, it used, and
+ Weston. For its rendering API, it used, and
uses, GLES and EGL. This was done so that the dependency on the
- libraries from the X Window System wasn't
+ libraries from the X Window System wasn't
needed, that a Wayland-only setup was possible. A small benefit of using
GLES was that it could run on embedded systems like Raspberry Pis.
@@ -168,7 +168,7 @@
- On the otherhand, if you are using the X
+ On the otherhand, if you are using the X
Window System, GLES will almost never be used and that support for the
API can be disabled without much worry. However, you kill off the
ability to use Wayland compositors that require GLES rendering if you
diff --git a/shareddeps/drivers/amdgpu-pro.xml b/shareddeps/drivers/amdgpu-pro.xml
index 87141d997f..968ad9e999 100644
--- a/shareddeps/drivers/amdgpu-pro.xml
+++ b/shareddeps/drivers/amdgpu-pro.xml
@@ -27,7 +27,7 @@
- The AMDGPU PRO proprietary driver contains
+ The AMDGPU PRO proprietary driver contains
userland drivers and libraries, providing hardware acceleration encoding,
EGL, OpenGL, GLES, and Vulkan support FOR AMDGPU
cards. If you do not have an AMDGPU card, you can skip this page.
diff --git a/shareddeps/drivers/cbindgen.xml b/shareddeps/drivers/cbindgen.xml
index 4ff19ff9e3..835778ec76 100644
--- a/shareddeps/drivers/cbindgen.xml
+++ b/shareddeps/drivers/cbindgen.xml
@@ -21,7 +21,7 @@
Introduction to Cbindgen
- Cbindgen can be used to generate C bindings for
+ Cbindgen can be used to generate C bindings for
Rust code.
@@ -52,7 +52,7 @@
Installation of cbindgen
- Install cbindgen by running the following
+ Install cbindgen by running the following
commands:
@@ -102,7 +102,7 @@
cbindgen
- generates C bindings for Rust code
+ generates C bindings for Rust code
cbindgen
diff --git a/shareddeps/drivers/cython.xml b/shareddeps/drivers/cython.xml
index 033c9057b7..06c2e05f3a 100644
--- a/shareddeps/drivers/cython.xml
+++ b/shareddeps/drivers/cython.xml
@@ -21,8 +21,8 @@
Introduction to Cython
- The Cython package provides a compiler for
- writing C extensions for the Python language.
+ The Cython package provides a compiler for
+ writing C extensions for the Python language.
&long-build-time;
@@ -91,7 +91,7 @@
cydbg
- is the Cython debugger
+ is the Cython debugger
cydbg
@@ -103,8 +103,8 @@
cython
- is a compiler for code written in the Cython
- language. It outputs a C/C++ program which can be
+ is a compiler for code written in the Cython
+ language. It outputs a C/C++ program which can be
compiled with a C/C++ compiler
@@ -117,9 +117,9 @@
cythonize
- is a compiler for code written in the Cython
- language. It outputs an extension module which is
- directly importable from Python
+ is a compiler for code written in the Cython
+ language. It outputs an extension module which is
+ directly importable from Python
cythonize
diff --git a/shareddeps/drivers/gbm.xml b/shareddeps/drivers/gbm.xml
index fe4d607af7..ddba0411cd 100644
--- a/shareddeps/drivers/gbm.xml
+++ b/shareddeps/drivers/gbm.xml
@@ -21,21 +21,21 @@
Introduction to GBM
- The GBM
+ The GBM
Graphics Buffer Manager.
library provides API functions for graphical rendering and is supplied by
- Mesa. Most drivers on Linux distributions come
- from Mesa, so GBM
+ Mesa. Most drivers on Linux distributions come
+ from Mesa, so GBM
will get installed along those drivers. On the other hand, does not need the full Mesa
- stack, but it still needs the GBM library. As
+ linkend="nvidia"/> does not need the full Mesa
+ stack, but it still needs the GBM library. As
such, you can install just what you need. You will not need to install
the full stack if you want to install , but you can if you so choose. It can be a good idea
to do so as to have a fallback (Zink Gallium3D + Nouveau Vulkan). If you
- are not installing NVIDIA, skip to and keep going till you reach to get a complete installation of drivers and other
libraries.
@@ -43,7 +43,7 @@
- Mesa is updated relatively often. You may
+ Mesa is updated relatively often. You may
want to use the latest available &mesa-major-minor;.x mesa version.
@@ -84,7 +84,7 @@
Installation of GBM
- Install the GBM by running the following
+ Install the GBM by running the following
commands:
@@ -122,7 +122,7 @@ fi
lib32 Installation of GBM
- Install lib32-GBM by running the following
+ Install lib32-GBM by running the following
commands:
diff --git a/shareddeps/drivers/hwdata.xml b/shareddeps/drivers/hwdata.xml
index 2f19803a87..592cde0912 100644
--- a/shareddeps/drivers/hwdata.xml
+++ b/shareddeps/drivers/hwdata.xml
@@ -21,7 +21,7 @@
Introduction to hwdata
- The hwdata package contains
+ The hwdata package contains
current PCI and vendor id data.
@@ -44,7 +44,7 @@
Installation of hwdata
- Install hwdata by
+ Install hwdata by
running the following commands:
diff --git a/shareddeps/drivers/libclc.xml b/shareddeps/drivers/libclc.xml
index 3110ad904f..ae5659b6f0 100644
--- a/shareddeps/drivers/libclc.xml
+++ b/shareddeps/drivers/libclc.xml
@@ -21,7 +21,7 @@
Introduction to libclc
- The libclc package contains library requirements
+ The libclc package contains library requirements
of the OpenCL C programming language (provides header files but no
libraries itself).
@@ -53,7 +53,7 @@
Installation of libclc
- Install libclc by running the following
+ Install libclc by running the following
commands:
diff --git a/shareddeps/drivers/libdrm.xml b/shareddeps/drivers/libdrm.xml
index 4ec80da63f..964d02d140 100644
--- a/shareddeps/drivers/libdrm.xml
+++ b/shareddeps/drivers/libdrm.xml
@@ -21,7 +21,7 @@
Introduction to Libdrm
- Libdrm provides a userspace library for
+ Libdrm provides a userspace library for
accessing the direct rendering manager (DRM) on operating systems that
support the ioctl interface. Libdrm is a low-level library, typically used
by graphics drivers such as the Mesa DRI drivers, the X drivers, libva and
@@ -68,7 +68,7 @@
-->
- Install libdrm by running the following
+ Install libdrm by running the following
commands:
@@ -96,7 +96,7 @@ ninja
lib32 Installation of Libdrm
- Install lib32-libdrm by running the following
+ Install lib32-libdrm by running the following
commands:
@@ -138,7 +138,7 @@ ldconfig
-D udev=true: This parameter enables support for using
- Udev instead of mknod.
+ Udev instead of mknod.
diff --git a/shareddeps/drivers/libglvnd.xml b/shareddeps/drivers/libglvnd.xml
index f4f728ba3d..872c2e66f7 100644
--- a/shareddeps/drivers/libglvnd.xml
+++ b/shareddeps/drivers/libglvnd.xml
@@ -21,7 +21,7 @@
Introduction to libglvnd
- The libglvnd package provides OpenGL
+ The libglvnd package provides OpenGL
implementations that dispatch API calls to a given driver vendor. Some of
the libraries are simply wrappers to the main dispatcher.
@@ -142,14 +142,14 @@ ldconfig
While installing this package can help prevent a lot of issues down the
road, this package can come with some caveats and all of them are in
relation to BLFS. BLFS naturally expects that the only OpenGL vendor is
- Mesa, so the instructions will thus assume
+ Mesa, so the instructions will thus assume
that this package has not been installed. The following have known
issues, and solutions:
- Mesa: In BLFS, a patch is listed in
+ Mesa: In BLFS, a patch is listed in
the Mesa page and will
instruct you to apply it. This will cause an issue unless you explictly
tell the build system not to link against this package's libraries,
@@ -160,23 +160,23 @@ ldconfig
package it tries to link against.Either don't apply that patch or follow this book's page instead. Thanks to
- Mesa's build system autodetecting if
- libglvnd is installed, the installation
+ Mesa's build system autodetecting if
+ libglvnd is installed, the installation
instructions don't change that much between this book and BLFS. The
main differences are lib32 support and not listing the demos
patch.
- GLU: In BLFS, the GLU: In BLFS, the GLU page explictly sets the GL
- vendor to be Mesa as the build system will
- otherwise expect libglvnd and
+ vendor to be Mesa as the build system will
+ otherwise expect libglvnd and
libOpenGL to be installed.
While the BLFS page instructions lead to a successful compilation, the
resulting library does not function properly. You should follow the
SLFS GLU page
instead. It also does check if the vendor is
- Mesa.
+ Mesa.
diff --git a/shareddeps/drivers/libva.xml b/shareddeps/drivers/libva.xml
index 7fd720d6ec..493aea188c 100644
--- a/shareddeps/drivers/libva.xml
+++ b/shareddeps/drivers/libva.xml
@@ -25,7 +25,7 @@
Introduction to libva
- The libva package contains a library which
+ The libva package contains a library which
provides access to hardware accelerated video processing, using hardware
to accelerate video processing in order to offload the central
processing unit (CPU) to decode and encode compressed digital video. The VA
@@ -102,7 +102,7 @@
-->
- Install libva by running the following
+ Install libva by running the following
commands:
@@ -128,7 +128,7 @@ ninja
lib32 Installation of libva
- Install lib32-libva by running the following
+ Install lib32-libva by running the following
commands:
diff --git a/shareddeps/drivers/libvdpau-va-gl.xml b/shareddeps/drivers/libvdpau-va-gl.xml
index d5d004efcd..0c84084f5f 100644
--- a/shareddeps/drivers/libvdpau-va-gl.xml
+++ b/shareddeps/drivers/libvdpau-va-gl.xml
@@ -25,7 +25,7 @@
Introduction to libvdpau-va-gl
- The libvdpau-va-gl package contains a library
+ The libvdpau-va-gl package contains a library
which implements the VDPAU library. Libvdpau_va_gl uses OpenGL under the
hood to accelerate drawing and scaling and the VA-API (if available) to
accelerate video decoding. For now VA-API is available on some Intel
@@ -62,7 +62,7 @@
Installation of libvdpau-va-gl
- Install libvdpau-va-gl by running the following
+ Install libvdpau-va-gl by running the following
commands:
@@ -93,7 +93,7 @@ make
lib32 Installation of libvdpau-va-gl
- Install lib32-libvdpau-va-gl by running the
+ Install lib32-libvdpau-va-gl by running the
following commands:
diff --git a/shareddeps/drivers/libvdpau.xml b/shareddeps/drivers/libvdpau.xml
index beb0eddd41..2d2d76f9a1 100644
--- a/shareddeps/drivers/libvdpau.xml
+++ b/shareddeps/drivers/libvdpau.xml
@@ -25,7 +25,7 @@
Introduction to libvdpau
- The libvdpau package contains a library which
+ The libvdpau package contains a library which
implements the VDPAU library.
@@ -101,7 +101,7 @@
Installation of libvdpau
- Install libvdpau by running the following
+ Install libvdpau by running the following
commands:
@@ -130,7 +130,7 @@ ninja
lib32 Installation of libvdpau
- Install lib32-libvdpau by running the following
+ Install lib32-libvdpau by running the following
commands:
diff --git a/shareddeps/drivers/libyaml.xml b/shareddeps/drivers/libyaml.xml
index 56a713f5f3..b41cbddc36 100644
--- a/shareddeps/drivers/libyaml.xml
+++ b/shareddeps/drivers/libyaml.xml
@@ -21,7 +21,7 @@
Introduction to libyaml
- The yaml package contains a C
+ The yaml package contains a C
library for parsing and emitting YAML (YAML Ain't Markup
Language) code.
@@ -52,7 +52,7 @@
Installation of libyaml
- Install libyaml by running the following
+ Install libyaml by running the following
commands:
diff --git a/shareddeps/drivers/llvm.xml b/shareddeps/drivers/llvm.xml
index aea701e19c..09af38316c 100644
--- a/shareddeps/drivers/llvm.xml
+++ b/shareddeps/drivers/llvm.xml
@@ -21,7 +21,7 @@
Introduction to LLVM
- The LLVM package contains a collection of
+ The LLVM package contains a collection of
modular and reusable compiler and toolchain technologies. The Low Level
Virtual Machine (LLVM) Core libraries provide a modern source and
target-independent optimizer, along with code generation support for many
@@ -31,18 +31,18 @@
- Clang provides new C, C++, Objective C
- and Objective C++ front-ends for LLVM and is
+ Clang provides new C, C++, Objective C
+ and Objective C++ front-ends for LLVM and is
required by some desktop packages such as
Firefox
and for if that is built using the system
- LLVM.
+ LLVM.
- The Compiler RT package provides
+ The Compiler RT package provides
runtime sanitizer and profiling libraries for developers who use
- Clang and LLVM.
+ Clang and LLVM.
@@ -146,7 +146,7 @@ sed '/LLVM_THIRD_PARTY_DIR/s@../third-party@third-party-&llvm-version;.src@' \
-i cmake/modules/HandleLLVMOptions.cmake
- Extract clang into
+ Extract clang into
the source tree by running the following commands:
@@ -154,7 +154,7 @@ sed '/LLVM_THIRD_PARTY_DIR/s@../third-party@third-party-&llvm-version;.src@' \
mv tools/clang-&llvm-version;.src tools/clang
- Extract compiler-rt into
+ Extract compiler-rt into
the source tree by running the following commands:
@@ -164,7 +164,7 @@ mv projects/compiler-rt-&llvm-version;.src projects/compiler-rt
There are many Python scripts in this package which use
/usr/bin/env python to access the system Python
- which on LFS is Python3. Use the following
+ which on LFS is Python3. Use the following
command to fix these scripts:
@@ -179,7 +179,7 @@ mv projects/compiler-rt-&llvm-version;.src projects/compiler-rtsed 's/utility/tool/' -i utils/FileCheck/CMakeLists.txt
- Install LLVM by running the following
+ Install LLVM by running the following
commands:
@@ -264,8 +264,8 @@ ldconfig
-D LLVM_ENABLE_FFI=ON: This switch allows
- LLVM to use
- libffi.
+ LLVM to use
+ libffi.
@@ -273,7 +273,7 @@ ldconfig
the libraries as static and links all of them into an unique shared one.
This is the recommended way of building a shared library and is required
by in order to build against the system-installed
- LLVM.
+ LLVM.
@@ -345,7 +345,7 @@ ldconfig
: if used instead of
-D LLVM_BUILD_LLVM_DYLIB=ON and
-D LLVM_LINK_LLVM_DYLIB=ON, builds all the
- LLVM libraries (about 60) as shared
+ LLVM libraries (about 60) as shared
libraries instead of static.
@@ -362,7 +362,7 @@ ldconfig
files to make enabled by default for
clang and clang++, so
the default configuration of their SSP feature will be consistent
- with GCC:
+ with GCC:
mkdir -pv /etc/clang &&
@@ -491,7 +491,7 @@ doneclang
- is the Clang C, C++,
+ is the Clang C, C++,
and Objective-C compiler
@@ -709,7 +709,7 @@ done
llc
- is the LLVM static compiler
+ is the LLVM static compiler
llc
@@ -722,7 +722,7 @@ done
is used to directly execute programs from
- LLVM bitcode
+ LLVM bitcode
lli
@@ -747,7 +747,7 @@ done
llvm-ar
- is the LLVM archiver
+ is the LLVM archiver
llvm-ar
@@ -759,7 +759,7 @@ done
llvm-as
- is the LLVM assembler
+ is the LLVM assembler
llvm-as
@@ -771,7 +771,7 @@ done
llvm-bcanalyzer
- is the LLVM bitcode analyzer
+ is the LLVM bitcode analyzer
llvm-bcanalyzer
@@ -821,7 +821,7 @@ done
llvm-config
- Prints LLVM compilation options
+ Prints LLVM compilation options
llvm-config
@@ -943,7 +943,7 @@ done
llvm-diff
- is the LLVM structural
+ is the LLVM structural
'diff'
@@ -956,7 +956,7 @@ done
llvm-dis
- is the LLVM disassembler
+ is the LLVM disassembler
llvm-dis
@@ -1031,7 +1031,7 @@ done
is used to extract a function from an
- LLVM module
+ LLVM module
llvm-extract
@@ -1108,7 +1108,7 @@ done
llvm-link
- is the LLVM linker
+ is the LLVM linker
llvm-link
@@ -1132,7 +1132,7 @@ done
llvm-lto
- is the LLVM LTO (link time optimization)
+ is the LLVM LTO (link time optimization)
linker
@@ -1219,7 +1219,7 @@ done
llvm-nm
- is used to list LLVM bitcode
+ is used to list LLVM bitcode
and object file's symbol table
@@ -1244,7 +1244,7 @@ done
llvm-objdump
- is an LLVM object file dumper
+ is an LLVM object file dumper
llvm-objdump
@@ -1305,7 +1305,7 @@ done
llvm-ranlib
- is used to generate an index for a LLVM
+ is used to generate an index for a LLVM
archive
@@ -1381,7 +1381,7 @@ done
llvm-rtdyld
- is the LLVM MC-JIT tool
+ is the LLVM MC-JIT tool
llvm-rtdyld
@@ -1393,7 +1393,7 @@ done
llvm-size
- is the LLVM object size dumper
+ is the LLVM object size dumper
llvm-size
@@ -1405,7 +1405,7 @@ done
llvm-split
- is the LLVM module splitter
+ is the LLVM module splitter
llvm-split
@@ -1455,7 +1455,7 @@ done
llvm-tblgen
- is the LLVM Target Description
+ is the LLVM Target Description
To C++ Code Generator
@@ -1468,7 +1468,7 @@ done
llvm-tli-checker
- is the LLVM TargetLibraryInfo
+ is the LLVM TargetLibraryInfo
versus SDK checker
@@ -1519,7 +1519,7 @@ done
opt
- is the LLVM optimizer
+ is the LLVM optimizer
opt
@@ -1555,8 +1555,8 @@ done
scan-build
- is a Perl script that invokes the
- Clang static analyzer
+ is a Perl script that invokes the
+ Clang static analyzer
scan-build
@@ -1568,8 +1568,8 @@ done
scan-build-py
- is a Python script that invokes the
- Clang static analyzer
+ is a Python script that invokes the
+ Clang static analyzer
scan-build-py
@@ -1581,7 +1581,7 @@ done
scan-view
- is a viewer for Clang static analyzer
+ is a viewer for Clang static analyzer
results
@@ -1594,7 +1594,7 @@ done
verify-uselistorder
- is the LLVM tool to verify use-list
+ is the LLVM tool to verify use-list
order
diff --git a/shareddeps/drivers/mako.xml b/shareddeps/drivers/mako.xml
index ab07498b79..88798d28ac 100644
--- a/shareddeps/drivers/mako.xml
+++ b/shareddeps/drivers/mako.xml
@@ -21,7 +21,7 @@
Introduction to Mako
- Mako is a Python module that implements hyperfast
+ Mako is a Python module that implements hyperfast
and lightweight templating for the Python platform.
diff --git a/shareddeps/drivers/mesa.xml b/shareddeps/drivers/mesa.xml
index 6a01460a37..af77c4f601 100644
--- a/shareddeps/drivers/mesa.xml
+++ b/shareddeps/drivers/mesa.xml
@@ -20,14 +20,14 @@
Introduction to Mesa
- Mesa offers a wide variety of graphic
+ Mesa offers a wide variety of graphic
software, like the OpenGL libraries and drivers, Vulkan drivers,
and other drivers.
Every driver from this package works with . The
- package will auto-detect a libglvnd
+ package will auto-detect a libglvnd
installation if present and will link against the libraries provided by
that package. Thus, the OpenGL libraries provided by this package will
not be built, only the drivers for OpenGL.
@@ -43,7 +43,7 @@
- Mesa is updated relatively often. You may
+ Mesa is updated relatively often. You may
want to use the latest available &mesa-major-minor;.x mesa version.
@@ -112,8 +112,8 @@
(to provide VA-API support for some
Gallium3D drivers, note that there is a circular dependency. You must
- build libva first without EGL and GLX support,
- install this package, and rebuild libva)
+ build libva first without EGL and GLX support,
+ install this package, and rebuild libva)
@@ -159,7 +159,7 @@
,
valgrind,
Mesa-Demos
- (provides more than 300 demos to test Mesa),
+ (provides more than 300 demos to test Mesa),
Bellagio OpenMAX Integration
Layer (for mobile platforms), and
@@ -172,7 +172,7 @@
Installation of Mesa
- Install Mesa by running the following
+ Install Mesa by running the following
commands:
@@ -219,7 +219,7 @@ ninja
lib32 Installation of Mesa
- Install lib32-Mesa by running the following
+ Install lib32-Mesa by running the following
commands:
@@ -316,7 +316,7 @@ ldconfig
virgl (for QEMU virtual GPU
- with virglrender support)
+ with virglrender support)
@@ -332,7 +332,7 @@ ldconfig
llvmpipe (softpipe but uses
- LLVM to increase performance)
+ LLVM to increase performance)
@@ -398,7 +398,7 @@ ldconfig
nouveau (for GTX 16XX, RTX 20XX, or newer NVIDIA GPUs;
this driver is maturing and is already quite performant, although less so
- than the NVIDIA driver; however, it is a good
+ than the NVIDIA driver; however, it is a good
replacement, especially when used with zink)
@@ -627,7 +627,7 @@ ldconfig
libgbm
- is the Mesa Graphics Buffer
+ is the Mesa Graphics Buffer
Manager library
@@ -640,7 +640,7 @@ ldconfig
libglapi
- is Mesa's implementation of the OpenGL
+ is Mesa's implementation of the OpenGL
API; provided if is not installed
diff --git a/shareddeps/drivers/nvidia-egl.xml b/shareddeps/drivers/nvidia-egl.xml
index 7f0732ed28..5757bcb977 100644
--- a/shareddeps/drivers/nvidia-egl.xml
+++ b/shareddeps/drivers/nvidia-egl.xml
@@ -18,8 +18,8 @@
Introduction to NVIDIA EGL Libraries
- The NVIDIA EGL Libraries allow the EGL drivers
- for the NVIDIA driver to function properly. If
+ The NVIDIA EGL Libraries allow the EGL drivers
+ for the NVIDIA driver to function properly. If
you are not installing , skip this package.
@@ -149,7 +149,7 @@ done
libnvidia-egl-wayland
- provides client-side Wayland EGL
+ provides client-side Wayland EGL
application support
diff --git a/shareddeps/drivers/nvidia.xml b/shareddeps/drivers/nvidia.xml
index 6063e7c20e..5a093bf7f6 100644
--- a/shareddeps/drivers/nvidia.xml
+++ b/shareddeps/drivers/nvidia.xml
@@ -20,7 +20,7 @@
Introduction to NVIDIA
- The NVIDIA proprietary driver contains
+ The NVIDIA proprietary driver contains
firmware, kernel drivers, userland drivers pertaining to OpenGL,
Vulkan, and hardware acceleration, and provides useful utilites for
NVIDIA cards. If you don't have a NVIDIA GPU, skip to the next package.
@@ -159,7 +159,7 @@
- Extract the NVIDIA driver runfile and
+ Extract the NVIDIA driver runfile and
navigate to the extracted directory:
@@ -169,7 +169,7 @@ cd NVIDIA-Linux-x86_64-&nvidia-version;
- Compile Rust by running the following
+ Compile Rust by running the following
commands:
@@ -328,9 +328,9 @@ fi
Still as the &root; user, fix the installation of the documentation
- and symlink a Zsh completion file into the
- correct location and move a Bash completion
- file into the location recommended by the Bash
+ and symlink a Zsh completion file into the
+ correct location and move a Bash completion
+ file into the location recommended by the Bash
completion maintainers:
@@ -397,9 +397,9 @@ mv -v /etc/bash_completion.d/cargo \
Configuration Information
- If you installed Rustc in
+ If you installed Rustc in
/opt, you need to update the
- following configuration files so that Rustc
+ following configuration files so that Rustc
is correctly found by other packages and system processes.
diff --git a/shareddeps/drivers/spirv-llvm-translator.xml b/shareddeps/drivers/spirv-llvm-translator.xml
index 7ddc768625..e6defa1afb 100644
--- a/shareddeps/drivers/spirv-llvm-translator.xml
+++ b/shareddeps/drivers/spirv-llvm-translator.xml
@@ -22,7 +22,7 @@
Introduction to SPIRV-LLVM-Translator
- SPIRV-LLVM-Translator is a tool and a library
+ SPIRV-LLVM-Translator is a tool and a library
for bi-directional translation between SPIR-V and LLVM IR.
@@ -55,7 +55,7 @@
Installation of SPIRV-LLVM-Translator
- Install SPIRV-LLVM-Translator by running the following
+ Install SPIRV-LLVM-Translator by running the following
commands:
@@ -87,7 +87,7 @@ ninja
lib32 Installation of SPIRV-LLVM-Translator
- Install lib32-SPIRV-LLVM-Translator by running the following
+ Install lib32-SPIRV-LLVM-Translator by running the following
commands:
diff --git a/shareddeps/net/curl.xml b/shareddeps/net/curl.xml
index f07ccb6111..138a358764 100644
--- a/shareddeps/net/curl.xml
+++ b/shareddeps/net/curl.xml
@@ -21,7 +21,7 @@
Introduction to cURL
- The cURL package contains a utility
+ The cURL package contains a utility
and a library used for transferring files with URL syntax to any of
the following protocols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP,
HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTSP, SMB, SMBS,
@@ -90,7 +90,7 @@
-->
- Install cURL by running the following
+ Install cURL by running the following
commands:
@@ -136,7 +136,7 @@ cp -v -R docs -T /usr/share/doc/curl-&curl-version;
lib32 Installation of cURL
- Install lib32-cURL
+ Install lib32-cURL
by running the following commands:
@@ -185,34 +185,34 @@ ldconfig
--with-openssl: This parameter chooses
- OpenSSL as SSL/TLS implementation.
+ OpenSSL as SSL/TLS implementation.
This option is not needed if is
selected instead.
: This parameter adds
- Kerberos 5 support to
+ Kerberos 5 support to
libcurl.
: Use this switch to
- build with GnuTLS support
- instead of OpenSSL for SSL/TLS. This requires
+ build with GnuTLS support
+ instead of OpenSSL for SSL/TLS. This requires
to be installed already.
: Use
this switch instead of --with-ca-path if
- building with GnuTLS support
- instead of OpenSSL for SSL/TLS.
+ building with GnuTLS support
+ instead of OpenSSL for SSL/TLS.
: This parameter adds
- SSH support to cURL. This is disabled
+ SSH support to cURL. This is disabled
by default.
diff --git a/shareddeps/net/libidn2.xml b/shareddeps/net/libidn2.xml
index c99308b169..2494ccd133 100644
--- a/shareddeps/net/libidn2.xml
+++ b/shareddeps/net/libidn2.xml
@@ -23,7 +23,7 @@
Introduction to libidn2
- libidn2 is a package designed for
+ libidn2 is a package designed for
internationalized string handling based on standards from the
Internet Engineering Task Force (IETF)'s IDN working group, designed for
internationalized domain names.
@@ -56,7 +56,7 @@
Installation of libidn2
- Install libidn2 by running the following
+ Install libidn2 by running the following
commands:
@@ -79,7 +79,7 @@ make
lib32 Installation of lib32-libidn2
- Install lib32-libidn2
+ Install lib32-libidn2
by running the following commands:
diff --git a/shareddeps/net/libpsl.xml b/shareddeps/net/libpsl.xml
index d8f9301f4b..41b9dce2b9 100644
--- a/shareddeps/net/libpsl.xml
+++ b/shareddeps/net/libpsl.xml
@@ -21,7 +21,7 @@
Introduction to libpsl
- The libpsl package provides a library for
+ The libpsl package provides a library for
accessing and resolving information from the Public Suffix List (PSL). The PSL
is a set of domain names beyond the standard suffixes, such as .com.
@@ -58,7 +58,7 @@
Installation of libpsl
- Install libpsl by running the following
+ Install libpsl by running the following
commands:
@@ -84,7 +84,7 @@ ninja
lib32 Installation of libpsl
- Install lib32-libpsl
+ Install lib32-libpsl
by running the following commands:
diff --git a/shareddeps/net/libtasn1.xml b/shareddeps/net/libtasn1.xml
index 8e16f18038..2f5ca919e9 100644
--- a/shareddeps/net/libtasn1.xml
+++ b/shareddeps/net/libtasn1.xml
@@ -22,7 +22,7 @@
Introduction to libtasn1
- libtasn1 is a highly portable C library
+ libtasn1 is a highly portable C library
that encodes and decodes DER/BER data following an ASN.1 schema.
@@ -45,7 +45,7 @@
Installation of libtasn1
- Install libtasn1 by running the
+ Install libtasn1 by running the
following commands:
@@ -76,7 +76,7 @@ make
lib32 Installation of libtasn1
- Install lib32-libtasn1
+ Install lib32-libtasn1
by running the following commands:
@@ -165,7 +165,7 @@ ldconfig
is an ASN.1 syntax tree generator for
- libtasn1
+ libtasn1
asn1Parser
diff --git a/shareddeps/net/libunistring.xml b/shareddeps/net/libunistring.xml
index 6a363317aa..661a7e088c 100644
--- a/shareddeps/net/libunistring.xml
+++ b/shareddeps/net/libunistring.xml
@@ -22,7 +22,7 @@
Introduction to libunistring
- libunistring is a library that provides
+ libunistring is a library that provides
functions for manipulating Unicode strings and for manipulating C
strings according to the Unicode standard.
@@ -48,7 +48,7 @@
Installation of libunistring
- Install libunistring by running the following
+ Install libunistring by running the following
commands:
@@ -74,7 +74,7 @@ make
lib32 Installation of lib32-libunistring
- Install lib32-libunistring
+ Install lib32-libunistring
by running the following commands:
diff --git a/shareddeps/net/make-ca.xml b/shareddeps/net/make-ca.xml
index b8fb549c5c..57c734deff 100644
--- a/shareddeps/net/make-ca.xml
+++ b/shareddeps/net/make-ca.xml
@@ -77,7 +77,7 @@
Installation of make-ca and Generation of the CA-certificates stores
- The make-ca script will download and process
+ The make-ca script will download and process
the certificates included in the certdata.txt file
for use as trust anchors for the trust module.
Additionally, it will generate system certificate stores used by BLFS
@@ -89,12 +89,12 @@
trust anchors to /etc/ssl/local prior to any
updates, preserving custom trust values that differ from Mozilla when
using the trust utility from
- p11-kit to operate on the trust store.
+ p11-kit to operate on the trust store.
Before you can install the package, you should add an extra instruction
- to the make-ca script that makes a
+ to the make-ca script that makes a
compatibility symlink that is used by Debian Linux packages and is
required by as its main development is done on
Debian Linux. Add that instruction to the script now:
@@ -105,7 +105,7 @@
EOF
- Now to install the make-ca script, it must be
+ Now to install the make-ca script, it must be
installed into the correct location as the &root; user:
@@ -115,7 +115,7 @@ install -vdm755 /etc/ssl/local
Technically, this package is already installed at this point.
- But most packages listing make-ca as
+ But most packages listing make-ca as
a dependency actually require the system certificate store set up
by this package, rather than the make-ca
program itself. So the instructions for using
@@ -134,7 +134,7 @@ install -vdm755 /etc/ssl/local
If running the script a second time with the same version of
certdata.txt, for instance, to update the
- stores when make-ca is upgraded, or to
+ stores when make-ca is upgraded, or to
add additional stores as the requisite software is installed,
replace the -g switch with the
-r switch in the command line. If packaging,
@@ -173,23 +173,23 @@ install -vdm755 /etc/ssl/local
There are three trust types that are recognized by the
- make-ca script, SSL/TLS, S/Mime, and code
- signing. For OpenSSL, these are
+ make-ca script, SSL/TLS, S/Mime, and code
+ signing. For OpenSSL, these are
serverAuth,
emailProtection, and
codeSigning respectively. If one of the three
trust arguments is omitted, the certificate is neither trusted, nor
rejected for that role. Clients that use
- OpenSSL or NSS
+ OpenSSL or NSS
encountering this certificate will present a warning to the user.
Clients using
- GnuTLS without
- p11-kit support are not aware of trusted
+ GnuTLS without
+ p11-kit support are not aware of trusted
certificates. To include this CA into the
ca-bundle.crt,
email-ca-bundle.crt, or
objsign-ca-bundle.crt files
- (the GnuTLS legacy bundles), it must have the
+ (the GnuTLS legacy bundles), it must have the
appropriate trust arguments.
@@ -201,14 +201,14 @@ install -vdm755 /etc/ssl/local
This directory is also used to store certificates that were added to or
modified in the system trust store by so that
trust values are maintained across upgrades. Files in this directory must
- be in the OpenSSL trusted certificate format.
+ be in the OpenSSL trusted certificate format.
Certificates imported using the trust utility from
will utilize the x509 Extended Key Usage values
to assign default trust values for the system anchors.
If you need to override trust values, or otherwise need to create
- an OpenSSL trusted certificate manually
+ an OpenSSL trusted certificate manually
from a regular PEM encoded file, you need to add trust arguments to the
openssl command, and create a new certificate. For
example, using the CAcert
@@ -258,9 +258,9 @@ openssl x509 -in class3.crt -text -fingerprint -setalias "CAcert Class 3 root" \
Using make-ca with Python3
- When Python3 was installed in LFS/MLFS, it
- included the pip3 module with vendored
- certificates from the Certifi module. That was
+ When Python3 was installed in LFS/MLFS, it
+ included the pip3 module with vendored
+ certificates from the Certifi module. That was
necessary, but it means that whenever pip3 is used it
can reference those certificates, primarily when creating a virtual
environment or when installing a module with all its wheel dependencies
@@ -271,21 +271,21 @@ openssl x509 -in class3.crt -text -fingerprint -setalias "CAcert Class 3 root" \
It is generally considered that the System Administrator should be in
charge of which certificates are available. Now that and have been installed and
- make-ca has been configured, it is possible to
+ make-ca has been configured, it is possible to
make pip3 use the system certificates.
The vendored certificates installed in LFS are a snapshot from when the
- pulled-in version of Certifi was created. If
+ pulled-in version of Certifi was created. If
you regularly update the system certificates, the vendored version will
become out of date.
- To use the system certificates in Python3, you
+ To use the system certificates in Python3, you
should set _PIP_STANDALONE_CERT to point to them, e.g for
- the bash shell:
+ the bash shell:
export _PIP_STANDALONE_CERT=/etc/pki/tls/certs/ca-bundle.crt
@@ -293,8 +293,8 @@ openssl x509 -in class3.crt -text -fingerprint -setalias "CAcert Class 3 root" \
If you have created virtual environments, for example when testing modules,
- and those include the Requests and
- Certifi modules in ~/.local/lib/python&python3-majorver;/
then those local modules will be used instead of the system
certificates unless you remove the local modules.
diff --git a/shareddeps/net/nspr.xml b/shareddeps/net/nspr.xml
index 12396f4a01..0ca53f2d1f 100644
--- a/shareddeps/net/nspr.xml
+++ b/shareddeps/net/nspr.xml
@@ -21,7 +21,7 @@
Introduction to NSPR
- Netscape Portable Runtime (NSPR) provides a
+ Netscape Portable Runtime (NSPR) provides a
platform-neutral API for system level and libc like functions.
@@ -44,7 +44,7 @@
Installation of NSPR
- Install NSPR by running the following commands:
+ Install NSPR by running the following commands:
cd nspr &&
@@ -77,7 +77,7 @@ makelib32 Installation of NSPR
- Install lib32-NSPR by running the following commands:
+ Install lib32-NSPR by running the following commands:
make distclean &&
@@ -174,7 +174,7 @@ ldconfig
provides compiler and linker options to other packages that use
- NSPR
+ NSPR
nspr-config
diff --git a/shareddeps/net/nss.xml b/shareddeps/net/nss.xml
index b64e46f551..fbcbc770a6 100644
--- a/shareddeps/net/nss.xml
+++ b/shareddeps/net/nss.xml
@@ -28,7 +28,7 @@
Introduction to NSS
- The Network Security Services (NSS) package is
+ The Network Security Services (NSS) package is
a set of libraries designed to support cross-platform development of
security-enabled client and server applications. Applications built with
NSS can support SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12,
@@ -122,7 +122,7 @@ fi
- Install NSS by running the following commands:
+ Install NSS by running the following commands:
patch -Np1 -i ../nss-standalone-1.patch &&
@@ -181,7 +181,7 @@ fi
- Install lib32-NSS by running the following commands:
+ Install lib32-NSS by running the following commands:
cd ../nss &&
@@ -235,13 +235,13 @@ ldconfigUSE_SYSTEM_ZLIB=1: This option is passed to
make to ensure that the
libssl3.so library is linked to
- the system installed zlib instead of the
+ the system installed zlib instead of the
in-tree version.
ZLIB_LIBS=-lz: This option provides the
- linker flags needed to link to the system zlib.
+ linker flags needed to link to the system zlib.
@@ -258,7 +258,7 @@ ldconfig
$([ -f /usr/lib{,32}/libsqlite3.so ] && echo
NSS_USE_SYSTEM_SQLITE=1): This tests if
- sqlite is installed and if so it
+ sqlite is installed and if so it
echos the option NSS_USE_SYSTEM_SQLITE=1 to
make so that
libsoftokn3.so will link against
diff --git a/shareddeps/net/p11-kit.xml b/shareddeps/net/p11-kit.xml
index d48f0053df..9c696f5ebc 100644
--- a/shareddeps/net/p11-kit.xml
+++ b/shareddeps/net/p11-kit.xml
@@ -22,7 +22,7 @@
Introduction to p11-kit
- The p11-kit package provides a way to load and
+ The p11-kit package provides a way to load and
enumerate PKCS #11 (a Cryptographic Token Interface Standard) modules.
@@ -81,7 +81,7 @@ cat >> trust/trust-extract-compat << "EOF"
EOF
- Install p11-kit by running the following
+ Install p11-kit by running the following
commands:
@@ -114,7 +114,7 @@ ln -sfv /usr/libexec/p11-kit/trust-extract-compat \
lib32 Installation of p11-kit
- Install lib32-p11-kit
+ Install lib32-p11-kit
by running the following commands:
@@ -156,7 +156,7 @@ ldconfig
: Use this switch if you want to
- use the Freebl library from NSS for SHA1 and
+ use the Freebl library from NSS for SHA1 and
MD5 hashing.
diff --git a/shareddeps/net/python3.xml b/shareddeps/net/python3.xml
index 63909f73f9..9be8c51f6c 100644
--- a/shareddeps/net/python3.xml
+++ b/shareddeps/net/python3.xml
@@ -23,15 +23,15 @@
Introduction to Python 3
- The Python 3 package contains the
- Python development environment.
+ The Python 3 package contains the
+ Python development environment.
This is useful for object-oriented programming, writing scripts,
prototyping large programs or developing entire applications.
- Python 3 was installed in LFS.
+ Python 3 was installed in LFS.
The only reason to rebuild it here is if is
installed or if upgrading.
@@ -93,7 +93,7 @@
Installation of Python 3
- Install Python 3 by running the following
+ Install Python 3 by running the following
commands:
@@ -122,7 +122,7 @@ make
--with-system-expat: This switch enables linking
- against the system version of Expat.
+ against the system version of Expat.
- Install Desktop File Utils by
+ Install Desktop File Utils by
running the following commands:
@@ -123,8 +123,8 @@ ninja
class="directory">/usr/share. These locations can be
extended with the environment variables XDG_CONFIG_DIRS
and XDG_DATA_DIRS, respectively. The
- GNOME, KDE and
- XFCE environments respect these
+ GNOME, KDE and
+ XFCE environments respect these
settings.
diff --git a/shareddeps/security/duktape.xml b/shareddeps/security/duktape.xml
index f39a610b0d..88b9dea679 100644
--- a/shareddeps/security/duktape.xml
+++ b/shareddeps/security/duktape.xml
@@ -22,7 +22,7 @@
Introduction to duktape
- duktape is an embeddable Javascript
+ duktape is an embeddable Javascript
engine, with a focus on portability and compact footprint.
@@ -47,7 +47,7 @@
Installation of duktape
- Install duktape by running the
+ Install duktape by running the
following commands:
diff --git a/shareddeps/security/elogind.xml b/shareddeps/security/elogind.xml
index 309b3e5563..2dcec16c44 100644
--- a/shareddeps/security/elogind.xml
+++ b/shareddeps/security/elogind.xml
@@ -22,13 +22,13 @@
Introduction to elogind
- elogind is the
- systemd project's "logind", extracted to
+ elogind is the
+ systemd project's "logind", extracted to
be a standalone daemon. It integrates with
to track all the users logged in to a system, and whether they
are logged in graphically, on the console, or remotely.
- Elogind exposes this information via the
- standard org.freedesktop.login1 D-Bus
+ Elogind exposes this information via the
+ standard org.freedesktop.login1 D-Bus
interface, and also through the file system using systemd's standard
/run/systemd layout.
@@ -77,7 +77,7 @@
Installation of elogind
- Install elogind by running the following
+ Install elogind by running the following
commands:
@@ -107,7 +107,7 @@ ln -sfvn elogind /usr/include/systemd
lib32 Installation of elogind
- Install lib32-elogind by running the following
+ Install lib32-elogind by running the following
commands:
@@ -163,14 +163,14 @@ ldconfig
-D cgroup-controller=elogind: This switch is
necessary to build this package when the kernel is not built with
enabled. Note that
- elogind strictly needs
+ elogind strictly needs
a kernel with enabled at runtime,
but this switch will allow building the package first.
-D dbuspolicydir=/etc/dbus-1/system.d: This switch
- sets the location of the D-Bus policy
+ sets the location of the D-Bus policy
directory.
@@ -226,7 +226,7 @@ ldconfig
Each user will need to register a user session using
- Linux-PAM at login. The
+ Linux-PAM at login. The
/etc/pam.d/system-session file needs to
be modified and a new file must be created in order for
elogind to work correctly. Run the following
diff --git a/shareddeps/security/glib2.xml b/shareddeps/security/glib2.xml
index 999cdbb74c..cca54f565d 100644
--- a/shareddeps/security/glib2.xml
+++ b/shareddeps/security/glib2.xml
@@ -22,7 +22,7 @@
Introduction to GLib
- The GLib package contains low-level
+ The GLib package contains low-level
libraries useful for providing data structure handling for C, portability
wrappers and interfaces for runtime functionality such as an
event loop, threads, dynamic loading and an object system.
@@ -160,7 +160,7 @@ fi
- Install GLib by running the following
+ Install GLib by running the following
commands:
@@ -378,7 +378,7 @@ ldconfig
is a simple tool used for working with
- D-Bus objects
+ D-Bus objects
gdbus
@@ -391,7 +391,7 @@ ldconfig
is used to generate code and/or documentation for one or
- more D-Bus interfaces
+ more D-Bus interfaces
gdbus-codegen
@@ -439,7 +439,7 @@ ldconfig
gio
- is a utility that makes many GIO
+ is a utility that makes many GIO
features available from the command line
@@ -506,7 +506,7 @@ ldconfig
glib-gettextize
- is a variant of the gettext
+ is a variant of the gettext
internationalization utility
diff --git a/shareddeps/security/icu.xml b/shareddeps/security/icu.xml
index 16645a567a..d6846074ff 100644
--- a/shareddeps/security/icu.xml
+++ b/shareddeps/security/icu.xml
@@ -23,10 +23,10 @@
Introduction to ICU
- The International Components for Unicode (ICU)
+ The International Components for Unicode (ICU)
package is a mature, widely used set of C/C++ libraries providing Unicode
and Globalization support for software applications.
- ICU is widely portable and gives applications
+ ICU is widely portable and gives applications
the same results on all platforms.
@@ -111,7 +111,7 @@
patch -p1 -i ../icu4c-&icu-version;-fix_enumeration-1.patch
-->
- Install ICU by running the following commands:
+ Install ICU by running the following commands:
- Install libxml2 by running the following
+ Install libxml2 by running the following
commands:
@@ -102,7 +102,7 @@ sed '/libs=/s/xml2.*/xml2"/' -i /usr/bin/xml2-config
lib32 Installation of libxml2
- Install lib32-libxml2 by running the following
+ Install lib32-libxml2 by running the following
commands:
@@ -140,13 +140,13 @@ ldconfig
--with-history: This switch enables
- Readline support when running
+ Readline support when running
xmlcatalog or xmllint in shell mode.
--with-icu: This switch enables support for
- ICU, which provides additional Unicode support.
+ ICU, which provides additional Unicode support.
This is needed for some packages outside of GLFS, such as for QtWebEngine.
diff --git a/shareddeps/security/linux-pam.xml b/shareddeps/security/linux-pam.xml
index e1fe96af01..1e2159887d 100644
--- a/shareddeps/security/linux-pam.xml
+++ b/shareddeps/security/linux-pam.xml
@@ -23,7 +23,7 @@
Introduction to Linux PAM
- The Linux PAM package contains
+ The Linux PAM package contains
Pluggable Authentication Modules used by the local
system administrator to control how application programs authenticate
users.
@@ -81,7 +81,7 @@
Installation of Linux PAM
- Compile and link Linux PAM by
+ Compile and link Linux PAM by
running the following commands:
@@ -175,7 +175,7 @@ chmod -v 4755 /usr/sbin/unix_chkpwd
lib32 Installation of Linux PAM
- Install lib32-Linux-PAM by
+ Install lib32-Linux-PAM by
running the following commands:
@@ -318,7 +318,7 @@ session required pam_deny.so
EOF
- The PAM man page (man
+ The PAM man page (man
pam) provides a good starting point to learn
about the several fields, and allowable entries. The
Linux-PAM System Administrators' Guide at
diff --git a/shareddeps/security/pcre2.xml b/shareddeps/security/pcre2.xml
index 95daac3e2c..217c9df7eb 100644
--- a/shareddeps/security/pcre2.xml
+++ b/shareddeps/security/pcre2.xml
@@ -22,10 +22,10 @@
Introduction to PCRE2
- The PCRE2 package contains a new generation of
- the Perl Compatible Regular Expression
+ The PCRE2 package contains a new generation of
+ the Perl Compatible Regular Expression
libraries. These are useful for implementing regular expression pattern
- matching using the same syntax and semantics as Perl.
+ matching using the same syntax and semantics as Perl.
@@ -47,7 +47,7 @@
Installation of PCRE2
- Install PCRE2 by running the following
+ Install PCRE2 by running the following
commands:
@@ -74,7 +74,7 @@ make
lib32 Installation of PCRE2
- Install lib32-PCRE2 by running the
+ Install lib32-PCRE2 by running the
following commands:
@@ -127,19 +127,19 @@ ldconfig
--enable-pcre2grep-libz: This switch adds support
- for reading .gz compressed files to pcre2grep.
+ for reading .gz compressed files to pcre2grep.
--enable-pcre2grep-libbz2: This switch adds
support for reading .bz2 compressed files to
- pcre2grep.
+ pcre2grep.
--enable-pcre2test-libreadline: This switch adds
line editing and history features to the
- pcre2test program.
+ pcre2test program.
&static-libraries;
@@ -186,9 +186,9 @@ ldconfig
pcre2grep
- is a version of grep
+ is a version of grep
that understands
- Perl compatible regular expressions.
+ Perl compatible regular expressions.
pcre2grep
@@ -201,7 +201,7 @@ ldconfig
can test a
- Perl compatible regular expression.
+ Perl compatible regular expression.
pcre2
@@ -214,7 +214,7 @@ ldconfig
outputs compilation information to programs linking against the
- PCRE2 libraries
+ PCRE2 libraries
pcre2-config
diff --git a/shareddeps/security/polkit.xml b/shareddeps/security/polkit.xml
index 4b9c8c2cfd..19d18b55ea 100644
--- a/shareddeps/security/polkit.xml
+++ b/shareddeps/security/polkit.xml
@@ -22,7 +22,7 @@
Introduction to Polkit
- Polkit is a toolkit for defining and handling
+ Polkit is a toolkit for defining and handling
authorizations. It is used for allowing unprivileged processes to
communicate with privileged processes.
@@ -77,10 +77,10 @@
Since elogindsystemd-logind
uses PAM to register user sessions, it is a good idea to build
- Polkit with PAM support so
+ Polkit with PAM support so
elogindsystemd-logind
- can track Polkit sessions.
+ can track Polkit sessions.
@@ -116,7 +116,7 @@ useradd -c "PolicyKit Daemon Owner" -d /etc/polkit-1 -u 27 \
-g polkitd -s /bin/false polkitd
- Install Polkit by running the following
+ Install Polkit by running the following
commands:
@@ -172,7 +172,7 @@ rm -rf /usr/lib/{sysusers,tmpfiles}.d
-D os_type=lfs: This switch ensures that
even if distribution auto detection fails, the distribution/OS type
- will be hardcoded in Polkit.
+ will be hardcoded in Polkit.
@@ -182,9 +182,9 @@ rm -rf /usr/lib/{sysusers,tmpfiles}.d
: This switch enables the
- package to use the Shadow rather than the
- Linux PAM Authentication framework. Use it
- if you have not installed Linux PAM.
+ package to use the Shadow rather than the
+ Linux PAM Authentication framework. Use it
+ if you have not installed Linux PAM.
@@ -293,7 +293,7 @@ rm -rf /usr/lib/{sysusers,tmpfiles}.d
polkitd
- provides the org.freedesktop.PolicyKit1 D-Bus
+ provides the org.freedesktop.PolicyKit1 D-Bus
service on the system message bus
@@ -306,7 +306,7 @@ rm -rf /usr/lib/{sysusers,tmpfiles}.d
libpolkit-agent-1
- contains the Polkit authentication
+ contains the Polkit authentication
agent API functions
@@ -319,7 +319,7 @@ rm -rf /usr/lib/{sysusers,tmpfiles}.d
libpolkit-gobject-1
- contains the Polkit authorization API functions
+ contains the Polkit authorization API functions
libpolkit-gobject-1
diff --git a/shareddeps/security/shadow.xml b/shareddeps/security/shadow.xml
index 9c507a1c52..9ecf55c033 100644
--- a/shareddeps/security/shadow.xml
+++ b/shareddeps/security/shadow.xml
@@ -22,11 +22,11 @@
Introduction to Shadow
- Shadow was indeed installed in LFS and there is
+ Shadow was indeed installed in LFS and there is
no reason to reinstall it unless you installed
- Linux-PAM after your LFS system was completed.
- If you have installed Linux-PAM,
- reinstalling Shadow will allow programs such as
+ Linux-PAM after your LFS system was completed.
+ If you have installed Linux-PAM,
+ reinstalling Shadow will allow programs such as
login and su to utilize PAM.
@@ -68,9 +68,9 @@
The installation commands shown below are for installations where
- Linux-PAM has been installed and
- Shadow is being reinstalled to support the
- Linux-PAM installation.
+ Linux-PAM has been installed and
+ Shadow is being reinstalled to support the
+ Linux-PAM installation.
@@ -84,7 +84,7 @@
- Reinstall Shadow by running the following
+ Reinstall Shadow by running the following
commands:
@@ -200,7 +200,7 @@ make
Configuring Shadow
- Shadow's stock configuration for the
+ Shadow's stock configuration for the
useradd utility may not be desirable for your
installation. One default parameter causes useradd to
create a mailbox file for any newly created user.
@@ -248,15 +248,15 @@ make
Configuration Information
- Configuring your system to use Linux-PAM can
+ Configuring your system to use Linux-PAM can
be a complex task. The information below will provide a basic setup so
- that Shadow's login and password
+ that Shadow's login and password
functionality will work effectively with
- Linux-PAM. Review the information and links
+ Linux-PAM. Review the information and links
on the page for further configuration
information. For information specific to integrating
- Shadow, Linux-PAM
- and libpwquality, you can visit the
+ Shadow, Linux-PAM
+ and libpwquality, you can visit the
following link:
@@ -274,7 +274,7 @@ make
The login program currently performs many functions
- which Linux-PAM modules should now handle.
+ which Linux-PAM modules should now handle.
The following sed command will comment out the
appropriate lines in /etc/login.defs, and stop
login from performing these functions (a backup
@@ -313,8 +313,8 @@ done
Configuring the /etc/pam.d/ Files
- As mentioned previously in the Linux-PAM
- instructions, Linux-PAM has two supported
+ As mentioned previously in the Linux-PAM
+ instructions, Linux-PAM has two supported
methods for configuration. The commands below assume that you've
chosen to use a directory based configuration, where each program has
its own configuration file. You can optionally use a single
@@ -325,7 +325,7 @@ done
As the root user, create
- the following Linux-PAM configuration files
+ the following Linux-PAM configuration files
in the /etc/pam.d/ directory
(or add the contents to the /etc/pam.conf file)
using the following commands:
@@ -476,7 +476,7 @@ done
At this point, you should do a simple test to see if
- Shadow is working as expected. Open
+ Shadow is working as expected. Open
another terminal and log in as
root, and then run
login and login as another user. If you do
@@ -485,10 +485,10 @@ done
now and double check the above configuration files manually.
Any error is the sign of an error in the above procedure.
You can also run the
- test suite from the Linux-PAM package
+ test suite from the Linux-PAM package
to assist you in determining the problem. If you cannot find and
fix the error, you should recompile
- Shadow adding the
+ Shadow adding the
switch to the
configure command in the above instructions
(also move the /etc/login.defs.orig backup
@@ -504,7 +504,7 @@ done
Instead of using the /etc/login.access file for
- controlling access to the system, Linux-PAM
+ controlling access to the system, Linux-PAM
uses the pam_access.so module
along with the /etc/security/access.conf file.
Rename the /etc/login.access file using the
@@ -534,7 +534,7 @@ done
Instead of using the /etc/limits file for
limiting usage of system resources,
- Linux-PAM uses the
+ Linux-PAM uses the
pam_limits.so module along
with the /etc/security/limits.conf file. Rename
the /etc/limits file using the following command:
diff --git a/shareddeps/security/shared-mime-info.xml b/shareddeps/security/shared-mime-info.xml
index 88ae145236..9337716851 100644
--- a/shareddeps/security/shared-mime-info.xml
+++ b/shareddeps/security/shared-mime-info.xml
@@ -25,7 +25,7 @@ xreflabel="shared-mime-info-&shared-mime-info-version;">
Introduction to Shared Mime Info
- The Shared Mime Info package contains a
+ The Shared Mime Info package contains a
MIME database. This allows central updates of MIME information for all
supporting applications.
@@ -67,7 +67,7 @@ xreflabel="shared-mime-info-&shared-mime-info-version;">
Installation of Shared Mime Info
- Install Shared Mime Info by running the
+ Install Shared Mime Info by running the
following commands:
@@ -92,7 +92,7 @@ ninja
If you have followed the instructions above to build
- xdgmime, to test the result issue
+ xdgmime, to test the result issue
ninja test.
diff --git a/shareddeps/security/systemd.xml b/shareddeps/security/systemd.xml
index 9c208a4595..4cdae1a654 100644
--- a/shareddeps/security/systemd.xml
+++ b/shareddeps/security/systemd.xml
@@ -25,11 +25,11 @@
Introduction to Systemd
- While Systemd was installed when
+ While Systemd was installed when
building LFS, there are many features provided by the package that
were not included in the initial installation because
- Linux-PAM was not yet installed.
- The Systemd package needs to be
+ Linux-PAM was not yet installed.
+ The Systemd package needs to be
rebuilt to provide a working systemd-logind service,
which provides many additional features for dependent packages.
@@ -70,13 +70,13 @@
is not strictly required to build
- Systemd, but the main reason to rebuild
- Systemd in GLFS (it's already built in
+ Systemd, but the main reason to rebuild
+ Systemd in GLFS (it's already built in
LFS anyway) is for the systemd-logind daemon and
the
pam_systemd.so PAM module.
is required for them. All packages in
- GLFS book with a dependency on Systemd
+ GLFS book with a dependency on Systemd
expect that it has been rebuilt with .
@@ -102,7 +102,7 @@
-e 's/GROUP="sgx", //' rules.d/50-udev-default.rules.in
- Rebuild Systemd by running the
+ Rebuild Systemd by running the
following commands:
@@ -136,7 +136,7 @@ ninja
For the best test results, make sure you run the test suite from
a system that is booted by the same
- Systemd version you are rebuilding.
+ Systemd version you are rebuilding.
@@ -161,7 +161,7 @@ ninja
lib32 Installation of Systemd
- Rebuild lib32-Systemd by running the
+ Rebuild lib32-Systemd by running the
following commands:
@@ -343,7 +343,7 @@ EOF
is a PAM module used to register user sessions with the
- systemd login manager,
+ systemd login manager,
systemd-logind
diff --git a/steam/steam/steam.xml b/steam/steam/steam.xml
index a442d7521a..7d29554ed8 100644
--- a/steam/steam/steam.xml
+++ b/steam/steam/steam.xml
@@ -21,7 +21,7 @@
Introduction to Steam
- The Steam package provides a digital software
+ The Steam package provides a digital software
delivery system, store, and launcher through VALVE's proprietary runtime.
@@ -63,7 +63,7 @@
ln -sf /usr/bin/true steamdeps
- Then install Steam by running
+ Then install Steam by running
the following command as the root
user:
@@ -78,9 +78,9 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
ln -sf /usr/bin/true steamdeps: This command
- makes the steamdepsPython
- script always exit with code 0 as it uses APT and its
- Python module, which isn't installed in LFS
+ makes the steamdeps Python
+ script always exit with code 0 as it uses APT and its
+ Python module, which isn't installed in LFS
and shouldn't be.
@@ -111,8 +111,8 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
Are launching in an X11 instance or have
- Xwayland running in a
- Wayland session
+ Xwayland running in a
+ Wayland sessionHave a working internet connection
@@ -122,23 +122,23 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
After you have made sure of the points above, now you can launch
steam. This will download the runtime for the
- Steam client. Afterwards, you will be brought
+ Steam client. Afterwards, you will be brought
to the login screen. Make extra sure you have the symlink made in
or you will not be able to get past this point.
Then, everything should work as normal and you can go ahead and allow
- Proton as you normally would on any given
+ Proton as you normally would on any given
Linux distribution.
If you find that launching any game doesn't open a window but still shows
that it is running, there is a good chance that
- Steam made a change that is incompatible with
+ Steam made a change that is incompatible with
your current version of the kernel and you need to upgrade. Even a
version difference between linux-6.12.3 and linux-6.12.8 can be enough
- for Steam or any of its runtime components
+ for Steam or any of its runtime components
to refuse opening a window, although this usually doesn't prevent
- Steam itself from launching. Even if you don't
+ Steam itself from launching. Even if you don't
upgrade this package, components downloaded by this package will get
updated as time goes on.
@@ -183,7 +183,7 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
is launcher shell script that unpacks
bootstraplinux_ubuntu12_32.tar.xz and properly
- launches Steam
+ launches Steam
bin_steam.sh
@@ -195,7 +195,7 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
bin_steamdeps.sh
- is a Python script which checks
+ is a Python script which checks
for dependencies using APT
@@ -235,7 +235,7 @@ mv -v /usr/share/doc/steam{,-&steam-version;}
is a tarball containing 32-bit software that fetches the
- Steam runtime from VALVE's servers
+ Steam runtime from VALVE's servers
bootstraplinux_ubuntu12_32.tar.xz
diff --git a/steam/steamdepsinst/libgpg-error.xml b/steam/steamdepsinst/libgpg-error.xml
index 46d4368d04..40281b3ea6 100644
--- a/steam/steamdepsinst/libgpg-error.xml
+++ b/steam/steamdepsinst/libgpg-error.xml
@@ -21,9 +21,9 @@
Introduction to libgpg-error
- The libgpg-error package contains a
+ The libgpg-error package contains a
library that defines common error values for all
- GnuPG components.
+ GnuPG components.
@@ -45,7 +45,7 @@
Installation of libgpg-error
- Install libgpg-error by running the
+ Install libgpg-error by running the
following commands:
@@ -104,7 +104,7 @@ install -v -m644 -D README /usr/share/doc/libgpg-error-&libgpg-error-version;/RE
gpg-error
- is used to determine libgpg-error
+ is used to determine libgpg-error
error codes
@@ -142,7 +142,7 @@ install -v -m644 -D README /usr/share/doc/libgpg-error-&libgpg-error-version;/RE
libgpg-error
- contains the libgpg-error API
+ contains the libgpg-error API
functions
diff --git a/steam/steamdepsinst/steamdepsinst.xml b/steam/steamdepsinst/steamdepsinst.xml
index a0e6adb187..f058651ac7 100644
--- a/steam/steamdepsinst/steamdepsinst.xml
+++ b/steam/steamdepsinst/steamdepsinst.xml
@@ -11,7 +11,7 @@
Installing Steam Dependencies
- This chapter covers installing Steam specific
+ This chapter covers installing Steam specific
dependencies.
diff --git a/steam/steamdepsinst/xdg-user-dirs.xml b/steam/steamdepsinst/xdg-user-dirs.xml
index 483c6a1ce9..d3dd046eea 100644
--- a/steam/steamdepsinst/xdg-user-dirs.xml
+++ b/steam/steamdepsinst/xdg-user-dirs.xml
@@ -24,7 +24,7 @@
Introduction to Xdg-user-dirs
- Xdg-user-dirs is a tool to help manage well
+ Xdg-user-dirs is a tool to help manage well
known user directories like the desktop folder and the music folder.
It also handles localization (i.e. translation) of the filenames.
@@ -48,7 +48,7 @@
Installation of Xdg-user-dirs
- Install xdg-user-dirs by running the following
+ Install xdg-user-dirs by running the following
commands:
diff --git a/steam/steampre/steampre.xml b/steam/steampre/steampre.xml
index 761952044f..786f9820fd 100644
--- a/steam/steampre/steampre.xml
+++ b/steam/steampre/steampre.xml
@@ -12,7 +12,7 @@
This chapter covers preliminary material for understanding what
- Steam is and what it requires.
+ Steam is and what it requires.
diff --git a/template/template.xml b/template/template.xml
index 24d003b8d4..8aa5e9b629 100644
--- a/template/template.xml
+++ b/template/template.xml
@@ -32,7 +32,7 @@
Introduction to TEMPLATE
- The TEMPLATE package contains...
+ The TEMPLATE package contains...
This is useful for...
@@ -142,7 +142,7 @@
Installation of TEMPLATE
- Install TEMPLATE by running the following
+ Install TEMPLATE by running the following
commands:
diff --git a/wine/gs/fdk-aac.xml b/wine/gs/fdk-aac.xml
index d2558033ef..99129f6981 100644
--- a/wine/gs/fdk-aac.xml
+++ b/wine/gs/fdk-aac.xml
@@ -22,7 +22,7 @@
Introduction to fdk-aac
- The fdk-aac package provides the Fraunhofer FDK
+ The fdk-aac package provides the Fraunhofer FDK
AAC library, which is purported to be a high quality Advanced Audio Coding
implementation.
@@ -46,7 +46,7 @@
Installation of fdk-aac
- Install fdk-aac by running the following
+ Install fdk-aac by running the following
commands:
@@ -69,7 +69,7 @@ make
lib32 Installation of fdk-aac
- Install lib32-fdk-aac by running the following
+ Install lib32-fdk-aac by running the following
commands:
diff --git a/wine/gs/ffmpeg.xml b/wine/gs/ffmpeg.xml
index 8ca3bec204..84a9cadc66 100644
--- a/wine/gs/ffmpeg.xml
+++ b/wine/gs/ffmpeg.xml
@@ -22,14 +22,14 @@
Introduction to FFmpeg
- FFmpeg is a solution to record, convert and
+ FFmpeg is a solution to record, convert and
stream audio and video. It is a very fast video and audio converter and it
can also acquire from a live audio/video source. Designed to be intuitive,
the command-line interface (ffmpeg) tries to figure out
- all the parameters, when possible. FFmpeg can
+ all the parameters, when possible. FFmpeg can
also convert from any sample rate to any other, and resize video on the
fly with a high quality polyphase filter.
- FFmpeg can use a Video4Linux compatible video
+ FFmpeg can use a Video4Linux compatible video
source and any Open Sound System audio source.
@@ -124,7 +124,7 @@
-i libavcodec/libx265.c
- Install FFmpeg by running the following
+ Install FFmpeg by running the following
commands:
@@ -168,7 +168,7 @@ install -v -m644 doc/*.txt /usr/share/doc/ffmpeg-&ffmpeg-version;
lib32 Installation of FFmpeg
- Install lib32-FFmpeg by running the following
+ Install lib32-FFmpeg by running the following
commands:
@@ -216,7 +216,7 @@ ldconfig
--enable-libfreetype: Enables
- Freetype support.
+ Freetype support.
@@ -324,8 +324,8 @@ ldconfig
: Use this option instead of
--enable-openssl, if you want to use
- GnuTLS instead of
- OpenSSL for HTTPS protocol.
+ GnuTLS instead of
+ OpenSSL for HTTPS protocol.
@@ -336,7 +336,7 @@ ldconfig
: Enables support for
- Pulseaudio for audio output.
+ Pulseaudio for audio output.
@@ -447,7 +447,7 @@ ldconfig
libavcodec
- is a library containing the FFmpeg codecs
+ is a library containing the FFmpeg codecs
(both encoding and decoding)
@@ -460,7 +460,7 @@ ldconfig
libavdevice
- is the FFmpeg device handling library
+ is the FFmpeg device handling library
libavdevice
@@ -511,7 +511,7 @@ ldconfig
libavutil
- is the FFmpeg utility library
+ is the FFmpeg utility library
libavutil
@@ -523,7 +523,7 @@ ldconfig
libpostproc
- is the FFmpeg post processing library
+ is the FFmpeg post processing library
libpostproc
@@ -535,7 +535,7 @@ ldconfig
libswresample
- is the FFmpeg audio rescaling library,
+ is the FFmpeg audio rescaling library,
it contains functions for converting audio sample formats
@@ -548,7 +548,7 @@ ldconfig
libswscale
- is the FFmpeg image rescaling library
+ is the FFmpeg image rescaling library
libswscale
diff --git a/wine/gs/gs.xml b/wine/gs/gs.xml
index 6725e512ae..3a2f6e24c8 100644
--- a/wine/gs/gs.xml
+++ b/wine/gs/gs.xml
@@ -11,9 +11,9 @@
GS
- This chapter covers how to install GStreamer and
- its dependencies. GStreamer is used in
- Wine for some codec playback.
+ This chapter covers how to install GStreamer and
+ its dependencies. GStreamer is used in
+ Wine for some codec playback.
diff --git a/wine/gs/gstreamer-suite.xml b/wine/gs/gstreamer-suite.xml
index 1157b3b161..01946da272 100644
--- a/wine/gs/gstreamer-suite.xml
+++ b/wine/gs/gstreamer-suite.xml
@@ -18,7 +18,7 @@
Introduction to the GStreamer Suite
- GStreamer is a streaming media framework that
+ GStreamer is a streaming media framework that
enables applications to share a common set of plugins for tasks such as
video encoding and decoding, audio encoding and decoding, audio and video
filters, audio visualisation, web streaming and anything else that
@@ -450,7 +450,7 @@ done
is a tool that prints out information on available
- GStreamer plugins,
+ GStreamer plugins,
information about a particular plugin, or information
about a particular element
@@ -465,7 +465,7 @@ done
is a tool that builds and runs basic
- GStreamer pipelines
+ GStreamer pipelines
gst-launch-1.0
@@ -491,7 +491,7 @@ done
is a tool used to gather statistics about
- GStreamer operations
+ GStreamer operations
gst-stats-1.0
@@ -528,8 +528,8 @@ done
gst-typefind-1.0
- uses the GStreamer type finding system
- to determine the relevant GStreamer
+ uses the GStreamer type finding system
+ to determine the relevant GStreamer
plugin to parse or decode files, and the corresponding MIME type
@@ -605,7 +605,7 @@ done
libgstreamer-1.0
- provides all of the core GStreamer
+ provides all of the core GStreamer
services, including initialization, plugin management and types,
as well as the object hierarchy that defines elements and bins,
along with some more specialized elements
diff --git a/wine/gs/lame.xml b/wine/gs/lame.xml
index 3f961ecb53..dd3fd508f6 100644
--- a/wine/gs/lame.xml
+++ b/wine/gs/lame.xml
@@ -22,7 +22,7 @@
Introduction to LAME
- The LAME package contains an MP3
+ The LAME package contains an MP3
encoder and optionally, an MP3 frame analyzer. This is useful
for creating and analyzing compressed audio files.
@@ -64,7 +64,7 @@
sed -i -e 's/^\(\s*hardcode_libdir_flag_spec\s*=\).*/\1/' configure
- Install LAME by running
+ Install LAME by running
the following commands:
@@ -91,7 +91,7 @@ make
lib32 Installation of LAME
- Install lib32-LAME by running
+ Install lib32-LAME by running
the following commands:
diff --git a/wine/gs/libaom.xml b/wine/gs/libaom.xml
index 1c6aec824b..fd08a3ea1d 100644
--- a/wine/gs/libaom.xml
+++ b/wine/gs/libaom.xml
@@ -20,7 +20,7 @@
Introduction to libaom
- The libaom package contains a reference
+ The libaom package contains a reference
version of the Alliance for Open Media video codec. This codec is a
patent free alternative to H.265, and is starting to be used throughout
the internet.
@@ -51,7 +51,7 @@
Installation of libaom
- Install libaom by running the following
+ Install libaom by running the following
commands:
@@ -85,7 +85,7 @@ rm -v /usr/lib/libaom.a
lib32 Installation of libaom
- Install lib32-libaom by running the following
+ Install lib32-libaom by running the following
commands:
@@ -125,7 +125,7 @@ ldconfig
-D ENABLE_DOCS=no: This switch disables building
- the documentation because doxygen is not
+ the documentation because doxygen is not
installed.
diff --git a/wine/gs/libvpx.xml b/wine/gs/libvpx.xml
index fbd137be1b..dd3afae999 100644
--- a/wine/gs/libvpx.xml
+++ b/wine/gs/libvpx.xml
@@ -71,7 +71,7 @@
find -type f | xargs touch
- Install libvpx by running the
+ Install libvpx by running the
following commands:
@@ -104,7 +104,7 @@ make
lib32-Installation of libvpx
- Install lib32-libvpx by running the
+ Install lib32-libvpx by running the
following commands:
@@ -149,7 +149,7 @@ ldconfig
mkdir libvpx-build && cd libvpx-build:
- The libvpx developers
+ The libvpx developers
recommend building in a dedicated build directory.
diff --git a/wine/gs/nasm.xml b/wine/gs/nasm.xml
index ddf3815b79..9edcd763e2 100644
--- a/wine/gs/nasm.xml
+++ b/wine/gs/nasm.xml
@@ -22,7 +22,7 @@
Introduction to NASM
- NASM (Netwide Assembler) is an 80x86
+ NASM (Netwide Assembler) is an 80x86
assembler designed for portability and modularity. It includes a
disassembler as well.
@@ -63,7 +63,7 @@
tar -xf ../nasm-&nasm-version;-xdoc.tar.xz --strip-components=1
- Install NASM by running
+ Install NASM by running
the following commands:
diff --git a/wine/gs/x264.xml b/wine/gs/x264.xml
index 5cebfeb756..cc65a7e569 100644
--- a/wine/gs/x264.xml
+++ b/wine/gs/x264.xml
@@ -22,7 +22,7 @@
Introduction to x264
- x264 package provides a library for encoding
+ x264 package provides a library for encoding
video streams into the H.264/MPEG-4 AVC format.
@@ -67,7 +67,7 @@
-->
- Install x264 by running the following
+ Install x264 by running the following
commands:
@@ -94,7 +94,7 @@ make
lib32 Installation of x264
- Install lib32-x264 by running the following
+ Install lib32-x264 by running the following
commands:
diff --git a/wine/gs/x265.xml b/wine/gs/x265.xml
index 1596cc6ba0..cc12fb9341 100644
--- a/wine/gs/x265.xml
+++ b/wine/gs/x265.xml
@@ -22,7 +22,7 @@
Introduction to x265
- x265 package provides a library for encoding
+ x265 package provides a library for encoding
video streams into the H.265/HEVC format.
@@ -70,7 +70,7 @@
-i source/CMakeLists.txt
- Install x265 by running the following
+ Install x265 by running the following
commands:
@@ -128,7 +128,7 @@ rm -vf /usr/lib/libx265.a
lib32-Installation of x265
- Install lib32-x265 by running the following
+ Install lib32-x265 by running the following
commands:
diff --git a/wine/mingw-w64/mingw-w64-binutils.xml b/wine/mingw-w64/mingw-w64-binutils.xml
index 158e070cbf..01a7e554c0 100644
--- a/wine/mingw-w64/mingw-w64-binutils.xml
+++ b/wine/mingw-w64/mingw-w64-binutils.xml
@@ -51,7 +51,7 @@
x86_64 MinGW-w64-Binutils
- Install x86_64 MinGW-w64-Binutils
+ Install x86_64 MinGW-w64-Binutils
by running the following commands:
@@ -82,7 +82,7 @@ cd ..
i686 MinGW-w64-Binutils
- Install i686 MinGW-w64-Binutils
+ Install i686 MinGW-w64-Binutils
by running the following commands:
@@ -161,7 +161,7 @@ rm -rf DESTDIR
{i686,x86_64}-w64-mingw32-windmc,
{i686,x86_64}-w64-mingw32-windres,
ar, as, dlltool, ld, ld.bfd, nm, objcopy, ranlib,
- readelf, and strip (MinGW-w64
+ readelf, and strip (MinGW-w64
specific binaries besides formatting include:
{i686,x86_64}-w64-mingw32-dllwrap,
{i686,x86_64}-w64-mingw32-windmc,
@@ -180,7 +180,7 @@ rm -rf DESTDIR
- Only binutils specific to MinGW-w64
+ Only binutils specific to MinGW-w64
will be explained. For the rest, see
Binutils.
diff --git a/wine/mingw-w64/mingw-w64-gcc-static.xml b/wine/mingw-w64/mingw-w64-gcc-static.xml
index c92de6e726..d79cbe05f5 100644
--- a/wine/mingw-w64/mingw-w64-gcc-static.xml
+++ b/wine/mingw-w64/mingw-w64-gcc-static.xml
@@ -21,8 +21,8 @@
Introduction to Static MinGW-w64-GCC
- MinGW-w64-GCC provides
- GCC compilers for MinGW-w64,
+ MinGW-w64-GCC provides
+ GCC compilers for MinGW-w64,
allowing users and applications to compile code targetting
Windows. This will be done in steps to avoid the need for
already present binaries. This is the static build, which
@@ -62,7 +62,7 @@
x86_64 Installation of Static MinGW-w64-GCC
- Install x86_64 Static MinGW-w64-GCC by
+ Install x86_64 Static MinGW-w64-GCC by
running the following commands:
@@ -90,7 +90,7 @@ make all-gcc
i686 Installation of Static MinGW-w64-GCC
- Install i686 Static MinGW-w64-GCC by running
+ Install i686 Static MinGW-w64-GCC by running
the following commands:
@@ -123,7 +123,7 @@ make all-gcc
mkdir build; cd build: The
- GCC documentation recommends
+ GCC documentation recommends
building the package in a dedicated build directory.
diff --git a/wine/mingw-w64/mingw-w64-gcc.xml b/wine/mingw-w64/mingw-w64-gcc.xml
index 10ad7f6987..d72feae7df 100644
--- a/wine/mingw-w64/mingw-w64-gcc.xml
+++ b/wine/mingw-w64/mingw-w64-gcc.xml
@@ -21,7 +21,7 @@
Introduction to MinGW-w64-GCC
- MinGW-w64-GCC has been built statically
+ MinGW-w64-GCC has been built statically
beforehand, and it should be rebuilt to support dynamic linking. This
section will be dedicated to finishing the MinGW-w64 toolchain.
@@ -64,7 +64,7 @@
x86_64 Installation of MinGW-w64-GCC
- Install x86_64 MinGW-w64-GCC by running the
+ Install x86_64 MinGW-w64-GCC by running the
following commands:
@@ -96,7 +96,7 @@ strip /usr/libexec/gcc/x86_64-w64-mingw32/&mingw-w64-gcc-version;/{cc1*,collect2
i686 Installation of MinGW-w64-GCC
- Install i686 MinGW-w64-GCC by running the
+ Install i686 MinGW-w64-GCC by running the
following commands:
@@ -129,7 +129,7 @@ strip /usr/libexec/gcc/i686-w64-mingw32/&mingw-w64-gcc-version;/{cc1*,collect2,l
Testing the Toolchain
- Now that the MinGW-w64 cross toolchain has
+ Now that the MinGW-w64 cross toolchain has
been fully installed, it is time to test the installation to make sure
everything is working as expected.
@@ -165,7 +165,7 @@ g++ -m32 main.cpp &&
rm -v a.out main.{c,cpp}
- Now test the MinGW-w64 cross compiler.
+ Now test the MinGW-w64 cross compiler.
@@ -216,7 +216,7 @@ rm -v a.exe main.{c,cpp}
mkdir build; cd build: The
- GCC documentation recommends
+ GCC documentation recommends
building the package in a dedicated build directory.
diff --git a/wine/mingw-w64/mingw-w64-headers.xml b/wine/mingw-w64/mingw-w64-headers.xml
index d53dea6f77..f49a53467d 100644
--- a/wine/mingw-w64/mingw-w64-headers.xml
+++ b/wine/mingw-w64/mingw-w64-headers.xml
@@ -64,7 +64,7 @@
x86_64 MinGW-w64-headers
- Install x86_64 MinGW-w64-headers
+ Install x86_64 MinGW-w64-headers
by running the following commands:
@@ -88,7 +88,7 @@ cd build-x86_64-headers &&
i686 MinGW-w64-headers
- Install i686 MinGW-w64-headers
+ Install i686 MinGW-w64-headers
by running the following commands:
diff --git a/wine/mingw-w64/mingw-w64.xml b/wine/mingw-w64/mingw-w64.xml
index e0d7e5fb1d..ed3c0d9cb6 100644
--- a/wine/mingw-w64/mingw-w64.xml
+++ b/wine/mingw-w64/mingw-w64.xml
@@ -59,7 +59,7 @@
x86_64 MinGW-w64
- Install x86_64 MinGW-w64
+ Install x86_64 MinGW-w64
by running the following commands:
@@ -110,7 +110,7 @@ make
i686 MinGW-w64
- Install i686 MinGW-w64
+ Install i686 MinGW-w64
by running the following commands:
diff --git a/wine/mingw-w64/whatis-mingw-w64.xml b/wine/mingw-w64/whatis-mingw-w64.xml
index 626f36c696..57db4fd42e 100644
--- a/wine/mingw-w64/whatis-mingw-w64.xml
+++ b/wine/mingw-w64/whatis-mingw-w64.xml
@@ -11,16 +11,16 @@
What is the MinGW-w64 Toolchain?
- MinGW-w64 itself is a package providing headers,
+ MinGW-w64 itself is a package providing headers,
C runtime libraries, and much more. When support for it is built into
- compilers such as GCC, it enables the building
+ compilers such as GCC, it enables the building
of software targetting Windows, such as programs and libraries. This
software is aimed to be used on Windows, but can also be used on Linux.
- LLVM can also be used for the toolchain. This
- book will use GCC instead as it has easier
+ LLVM can also be used for the toolchain. This
+ book will use GCC instead as it has easier
instructions, quicker build times, and saves disk space.
@@ -40,10 +40,10 @@
system, we do not have such DLLs installed on the system, and they were
never compiled in LFS or earlier in this book.
does install DLL files but are strictly meant for
- Wine and Proton as a way of exposing DLSS.
- MinGW-w64 only installs static libraries, which
+ Wine and Proton as a way of exposing DLSS.
+ MinGW-w64 only installs static libraries, which
are helpful when compiling Windows software, but are useless at runtime.
- Wine needs to compile the dynamic libraries for
+ Wine needs to compile the dynamic libraries for
most Windows software to function.
@@ -51,10 +51,10 @@
If you are a developer and wish to target Windows, this toolchain should be
pretty useful. You won't need to follow any of the chapters after this one
if you just want the MinGW-w64 toolchain. It is recommended to still
- install Wine for sanity checks revolving around
+ install Wine for sanity checks revolving around
your built software you are developing, although it isn't a perfect
replacement for an accurate Windows environment. While the built software
- may work fine with Wine, it could be totally
+ may work fine with Wine, it could be totally
broken on Windows.
diff --git a/wine/misc/libxkbcommon.xml b/wine/misc/libxkbcommon.xml
index 8ba2f5c7ec..0798f27d61 100644
--- a/wine/misc/libxkbcommon.xml
+++ b/wine/misc/libxkbcommon.xml
@@ -21,7 +21,7 @@
Introduction to libxkbcommon
- libxkbcommon is a keymap compiler and
+ libxkbcommon is a keymap compiler and
support library which processes a reduced subset of keymaps as
defined by the XKB specification.
@@ -73,7 +73,7 @@
sed -i "s/sizeof(dtdstr)/ARRAY_SIZE(dtdstr) - 1/" src/registry.c
- Install libxkbcommon by running the following
+ Install libxkbcommon by running the following
commands:
@@ -105,7 +105,7 @@ ninja
lib32 Installation of libxkbcommon
- Install lib32-libxkbcommon by running the following
+ Install lib32-libxkbcommon by running the following
commands:
@@ -191,7 +191,7 @@ ldconfig
libxkbcommon
- contains the libxkbcommon API functions
+ contains the libxkbcommon API functions
libxkbcommon
@@ -203,7 +203,7 @@ ldconfig
libxkbcommon-x11
- contains the libxkbcommon X11 specific API
+ contains the libxkbcommon X11 specific API
functions
diff --git a/wine/misc/misc.xml b/wine/misc/misc.xml
index 4243784951..cbeaa3f5fd 100644
--- a/wine/misc/misc.xml
+++ b/wine/misc/misc.xml
@@ -11,8 +11,8 @@
Miscellaneous
- This chapter covers miscellaneous dependencies of
- Wine that don't fit in any given category.
+ This chapter covers miscellaneous dependencies of
+ Wine that don't fit in any given category.
diff --git a/wine/misc/sdl2.xml b/wine/misc/sdl2.xml
index 63fc9bbc6b..5aea9180e7 100644
--- a/wine/misc/sdl2.xml
+++ b/wine/misc/sdl2.xml
@@ -21,7 +21,7 @@
Introduction to SDL2
- The Simple DirectMedia Layer Version 2 (SDL2
+ The Simple DirectMedia Layer Version 2 (SDL2
for short) is a cross-platform library designed to make it easy to write
multimedia software, such as games and emulators.
@@ -90,7 +90,7 @@
-->
- Install SDL2 by running the
+ Install SDL2 by running the
following commands:
@@ -118,7 +118,7 @@ rm -v /usr/lib/libSDL2*.a
lib32 Installation of SDL2
- Install lib32-SDL2 by running the
+ Install lib32-SDL2 by running the
following commands:
@@ -147,7 +147,7 @@ ldconfig
Testing SDL2
- If you wish to, test the installation of SDL2
+ If you wish to, test the installation of SDL2
using the included test programs. None of the resulting binaries need
to be installed. Issue the following commands to build the test
programs:
diff --git a/wine/wine/dxvk.xml b/wine/wine/dxvk.xml
index df11f6fddd..9f5ada5ec6 100644
--- a/wine/wine/dxvk.xml
+++ b/wine/wine/dxvk.xml
@@ -18,9 +18,9 @@
Introduction to DXVK
- The DXVK package contains DLL files which
+ The DXVK package contains DLL files which
converts Direct3D 8-11 calls to Vulkan. By default in
- Wine, Direct3D 8-11 calls are converted to
+ Wine, Direct3D 8-11 calls are converted to
OpenGL calls in a poor manner, leading to bad performance. As such,
many people install this package.
@@ -97,7 +97,7 @@ mv -T Vulkan-Headers-* \
If you are doing multilib, it is recommended to install 32-bit along with
- 64-bit DXVK as there are plenty of 32-bit
+ 64-bit DXVK as there are plenty of 32-bit
Direct3D applications.
@@ -105,7 +105,7 @@ mv -T Vulkan-Headers-* \
64-bit Installation
- Install 64-bit DXVK by running
+ Install 64-bit DXVK by running
the following commands:
@@ -133,7 +133,7 @@ install -vDm644 build-win64/DESTDIR/bin/*.dll \
32-bit Installation
- Install 32-bit DXVK by running
+ Install 32-bit DXVK by running
the following commands:
@@ -169,7 +169,7 @@ install -vDm644 build-win32/DESTDIR/bin/*.dll \
- First, create the Wine prefix if it is not
+ First, create the Wine prefix if it is not
already made:
@@ -178,13 +178,13 @@ install -vDm644 build-win32/DESTDIR/bin/*.dll \
wineboot may report an error in the output, but this
is normal and frequent. Usually, these errors are non-fatal and you won't
- need to typically worry about them. Wine is
+ need to typically worry about them. Wine is
very verbose.
While the DXVK DLL files have been installed, they are not yet in the
- Wine prefix. Create symlinks so that they can be
- found by Wine, whilst allowing updating of this
+ Wine prefix. Create symlinks so that they can be
+ found by Wine, whilst allowing updating of this
package without having to copy everything over again. Along with this, the
registry must be updated to use the new DLLs. Do this for each
archetecture you have installed.
@@ -244,13 +244,13 @@ done
WINEPREFIX=~/.wine wineboot -u: This command creates a
- Wine prefix and copies over any missing files
+ Wine prefix and copies over any missing files
to it. It will not reset an existing prefix.
wine reg add ...: This command overrides the
- registry so that Wine will use the new DLL
+ registry so that Wine will use the new DLL
files instead of the old ones.
diff --git a/wine/wine/vkd3d-proton.xml b/wine/wine/vkd3d-proton.xml
index d9f61cb455..5151663a25 100644
--- a/wine/wine/vkd3d-proton.xml
+++ b/wine/wine/vkd3d-proton.xml
@@ -18,12 +18,12 @@
Introduction to VKD3D-Proton
- The VKD3D-Proton package contains DLL files
+ The VKD3D-Proton package contains DLL files
which converts Direct3D 12 calls to Vulkan. By default in
- Wine, Direct3D 12 calls are also converted to
+ Wine, Direct3D 12 calls are also converted to
Vulkan; however, this package makes more aggressive optimizations geared
towards gaming and replaces the default implementation provided by
- Wine, VKD3D.
+ Wine, VKD3D.
VKD3D-Proton Dependencies
@@ -129,7 +129,7 @@ mv -T SPIRV-Tools-* \
64-bit Installation
- Install 64-bit VKD3D-Proton by running
+ Install 64-bit VKD3D-Proton by running
the following commands:
@@ -157,7 +157,7 @@ install -vDm644 build-win64/DESTDIR/bin/*.dll \
32-bit Installation
- Install 32-bit VKD3D-Proton by running
+ Install 32-bit VKD3D-Proton by running
the following commands:
@@ -187,8 +187,8 @@ install -vDm644 build-win32/DESTDIR/bin/*.dll \
Setting Up VKD3D-ProtonWhile the VKD3D-Proton DLL files have been installed, they are not yet in the
- Wine prefix. Create symlinks so that they can be
- found by Wine, whilst allowing updating of this
+ Wine prefix. Create symlinks so that they can be
+ found by Wine, whilst allowing updating of this
package without having to copy everything over again. Along with this, the
registry must be updated to use the new DLLs. Do this for each
archetecture you have installed.
@@ -248,7 +248,7 @@ done
wine reg add ...: This command overrides the
- registry so that Wine will use the new DLL
+ registry so that Wine will use the new DLL
files instead of the old ones.
diff --git a/wine/wine/wine.xml b/wine/wine/wine.xml
index 8987d05a8c..d6b23ac447 100644
--- a/wine/wine/wine.xml
+++ b/wine/wine/wine.xml
@@ -65,8 +65,8 @@
- Install 32-bit only Wine by running
+ Install 32-bit only Wine by running
the following commands:
@@ -212,12 +212,12 @@ make
As for Direct3D 12, you may also wish to install
which replaces
- VKD3D provided by
- Wine. VKD3D is less
+ VKD3D provided by
+ Wine. VKD3D is less
aggressive with optimizations and is geared for general use, whereas
- VKD3D-Proton has aggressive optimizations and
+ VKD3D-Proton has aggressive optimizations and
is geared towards gaming. Despite the name, it can be used with
- Wine and works quite well.
+ Wine and works quite well.
@@ -303,7 +303,7 @@ make
msiexec
- is the Wine MSI installer;
+ is the Wine MSI installer;
symlink to wine
@@ -316,7 +316,7 @@ make
notepad
- is the Wine text editor;
+ is the Wine text editor;
symlink to wine
@@ -329,7 +329,7 @@ make
regedit
- is the Wine registry editor;
+ is the Wine registry editor;
symlink to wine
@@ -342,7 +342,7 @@ make
regsvr32
- is the Wine DLL Registration Server;
+ is the Wine DLL Registration Server;
symlink to wine
@@ -355,7 +355,7 @@ make
widl
- is the Wine Interface Definition
+ is the Wine Interface Definition
Language (IDL) compiler
@@ -380,7 +380,7 @@ make
wineboot
- performs Wine initialization, startup,
+ performs Wine initialization, startup,
and shutdown tasks;
symlink to wine
@@ -394,7 +394,7 @@ make
winebuild
- is the Wine DLL builder
+ is the Wine DLL builder
winebuild
@@ -406,7 +406,7 @@ make
winecfg
- is the Wine Configuration Editor;
+ is the Wine Configuration Editor;
symlink to wine
@@ -419,7 +419,7 @@ make
wineconsole
- is the Wine console;
+ is the Wine console;
symlink to wine
@@ -432,8 +432,8 @@ make
wine{cpp,g++,gcc}
- is the Wine C and C++
- MinGW-w64 Compatible Compiler
+ is the Wine C and C++
+ MinGW-w64 Compatible Compiler
winecompilers
@@ -445,7 +445,7 @@ make
winedbg
- is the Wine debugger;
+ is the Wine debugger;
symlink to wine
@@ -458,7 +458,7 @@ make
winedump
- is a Wine DLL tool
+ is a Wine DLL tool
winedump
@@ -470,7 +470,7 @@ make
winefile
- is a Wine File Manager;
+ is a Wine File Manager;
symlink to wine
@@ -496,10 +496,10 @@ make
winemine
- is the WineMinesweeper
- game; it is also just an example and not meant
- to be an accurate implementation of Minesweeper;
-
+ is the Wine Minesweeper
+ game; it is also just an example and not meant
+ to be an accurate implementation of Minesweeper;
+
symlink to wine
@@ -525,7 +525,7 @@ make
wineserver
- is the Wine server
+ is the Wine server
wineserver
@@ -537,7 +537,7 @@ make
wmc
- is the Wine Message Compiler
+ is the Wine Message Compiler
wmc
@@ -549,7 +549,7 @@ make
wrc
- is the Wine Resource Compiler
+ is the Wine Resource Compiler
wrc
diff --git a/wine/wine/winechpt.xml b/wine/wine/winechpt.xml
index 51cd64583b..59e241771e 100644
--- a/wine/wine/winechpt.xml
+++ b/wine/wine/winechpt.xml
@@ -11,7 +11,7 @@
Wine
- This chapter covers the installation of Wine and
+ This chapter covers the installation of Wine and
some packages that help with its performance in graphical environments.
diff --git a/wine/winepre/whatiswine.xml b/wine/winepre/whatiswine.xml
index 580e8967de..dc8a5ddc14 100644
--- a/wine/winepre/whatiswine.xml
+++ b/wine/winepre/whatiswine.xml
@@ -12,24 +12,24 @@
What is Wine?
- Wine is an application that allows users
+ Wine is an application that allows users
to execute Windows software via a compatibilty layer. Although the
acronym of WINE (Wine Is Not Emulation) describes itself as not an
emulator but as a compatabilty layer, many still see it as one.
- Wine is geared towards running normal
- Windows software whereas Steam's Proton
+ Wine is geared towards running normal
+ Windows software whereas Steam's Proton
is more geared towards playing games at high performance. Trying
- to run regular Windows software may be troublesome with
- Proton but is no trouble to Wine.
- Even some games run better on Wine but
- struggle or simply don't launch with Proton.
+ to run regular Windows software may be troublesome with
+ Proton but is no trouble to Wine.
+ Even some games run better on Wine but
+ struggle or simply don't launch with Proton.
- As Wine deals with a foreign format,
+ As Wine deals with a foreign format,
it is to be expected that it depends on an extra toolchain as well as
other dependencies. Please check before
continuing with this section.
diff --git a/wine/winepre/winedeps.xml b/wine/winepre/winedeps.xml
index 8808f1e1d4..bc53b7eb55 100644
--- a/wine/winepre/winedeps.xml
+++ b/wine/winepre/winedeps.xml
@@ -27,16 +27,16 @@
If you don't want a WoW64 build, follow the instructions
- normally and skip the lib32 instructions. When you reach the
- MinGW-w64 section, follow only the x86_64 instructions.
+ normally and skip the lib32 instructions. When you reach the
+ MinGW-w64 section, follow only the x86_64 instructions.
If you want a 32-bit only build, follow only the lib32
- instructions. When you reach MinGW-w64, follow
+ instructions. When you reach MinGW-w64, follow
the i686 instructions. However, for the sake of continuing onto BLFS, it is
recommended to do the normal installations as well, save for
- MinGW-w64.
+ MinGW-w64.
diff --git a/wine/winepre/winepre.xml b/wine/winepre/winepre.xml
index f0f82d2d53..40a2044b9f 100644
--- a/wine/winepre/winepre.xml
+++ b/wine/winepre/winepre.xml
@@ -12,7 +12,7 @@
This chapter covers preliminary material for understanding what
- Wine is and what it requires.
+ Wine is and what it requires.