Beyond Linux ® From Scratch (System V Edition)

Note

Since elogind uses PAM to register user sessions, it is a good idea to build Polkit with PAM support so elogind can track Polkit sessions.

Optional

GTK-Doc-1.33.2, dbusmock-0.30.2, and SpiderMonkey from Firefox-115.7.0 (can be used in place of duktape)

Optional Runtime Dependencies

One polkit authentication agent for using polkit in the graphical environment: polkit-kde-agent in Plasma-5.27.10 for KDE, the agent built in gnome-shell-45.4 for GNOME3, polkit-gnome-0.105 for XFCE, and lxqt-policykit-1.4.0 for LXQt

Note

If libxslt-1.1.39 is installed, then docbook-xml-4.5 and docbook-xsl-nons-1.79.2 are required. If you have installed libxslt-1.1.39, but you do not want to install any of the DocBook packages mentioned, you will need to use -Dman=false in the instructions below.

Installation of Polkit

There should be a dedicated user and group to take control of the polkitd daemon after it is started. Issue the following commands as the root user:

groupadd -fg 27 polkitd &&
useradd -c "PolicyKit Daemon Owner" -d /etc/polkit-1 -u 27 \
        -g polkitd -s /bin/false polkitd

First fix a build problem for sysV based systems:

sed -i '/systemd_sysusers_dir/s/^/#/' meson.build

Install Polkit by running the following commands:

mkdir build &&
cd    build &&

meson setup ..                      \
      --prefix=/usr                 \
      --buildtype=release           \
      -Dman=true                    \
      -Dsession_tracking=libelogind \
      -Dtests=true                  &&
ninja

To test the results, first ensure that the system D-Bus daemon is running, and both D-Bus Python-1.3.2 and dbusmock-0.30.2 are installed. Then run ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dtests=true: This switch allows to run the test suite of this package. As Polkit is used for authorizations, its integrity can affect system security. So it's recommended to run the test suite building this package.

-Djs_engine=mozjs: This switch allows using the SpiderMonkey from Firefox-115.7.0 JavaScript engine instead of the duktape-2.7.0 JavaScript engine.

-Dos_type=lfs: Use this switch if you did not create the /etc/lfs-release file or distribution auto detection will fail and you will be unable to use Polkit.

-Dauthfw=shadow: 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.

-Dintrospection=false: Use this option if you are certain that you do not need gobject-introspection files for polkit, or do not have gobject-introspection installed.

-Dman=false: Use this option to disable generating and installing manual pages. This is useful if libxslt is not installed.

-Dexamples=true: Use this option to build the example programs.

-Dgtk_doc=true: Use this option to enable building and installing the API documentation.

Installed Programs: pkaction, pkcheck, pkexec, pkttyagent, and polkitd

Installed Libraries: libpolkit-agent-1.so and libpolkit-gobject-1.so

Installed Directories: /etc/polkit-1, /usr/include/polkit-1, /usr/lib/polkit-1, /usr/share/gtk-doc/html/polkit-1, and /usr/share/polkit-1

Short Descriptions

pkaction	is used to obtain information about registered PolicyKit actions
pkcheck	is used to check whether a process is authorized for action
pkexec	allows an authorized user to execute a command as another user
pkttyagent	is used to start a textual authentication agent for the subject
polkitd	provides the org.freedesktop.PolicyKit1 D-Bus service on the system message bus
`libpolkit-agent-1.so`	contains the Polkit authentication agent API functions
`libpolkit-gobject-1.so`	contains the Polkit authorization API functions

polkit-gnome-0.105

Introduction to Polkit GNOME

The Polkit GNOME package provides an Authentication Agent for Polkit that integrates well with the GNOME Desktop environment.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/polkit-gnome/0.105/polkit-gnome-0.105.tar.xz
Download MD5 sum: 50ecad37c8342fb4a52f590db7530621
Download size: 305 KB
Estimated disk space required: 5.0 MB
Estimated build time: 0.1 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/polkit-gnome-0.105-consolidated_fixes-1.patch

Polkit GNOME Dependencies

Required

AccountsService-23.13.9, GTK+-3.24.41, and Polkit-124

Installation of Polkit GNOME

First, apply some fixes that allow for the proper user icon to be used, as well as some security fixes:

patch -Np1 -i ../polkit-gnome-0.105-consolidated_fixes-1.patch

Install Polkit GNOME by running the following commands:

./configure --prefix=/usr &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Configuring Polkit GNOME

Automatic Startup

For the authentication framework to work, polkit-gnome-authentication-agent-1 needs to be started. However, make install did not install a startup file for the Polkit GNOME so you have to create it by yourself.

Issue the following commands as the root user to create a startup file for Polkit GNOME:

mkdir -p /etc/xdg/autostart &&
cat > /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop << "EOF"
[Desktop Entry]
Name=PolicyKit Authentication Agent
Comment=PolicyKit Authentication Agent
Exec=/usr/libexec/polkit-gnome-authentication-agent-1
Terminal=false
Type=Application
Categories=
NoDisplay=true
OnlyShowIn=GNOME;XFCE;Unity;
AutostartCondition=GNOME3 unless-session gnome
EOF

Installed Program: polkit-gnome-authentication-agent-1

Installed Libraries: None

Installed Directory: None

Short Descriptions

polkit-gnome-authentication-agent-1

is the Polkit authentication agent

Shadow-4.14.5

Introduction to Shadow

Shadow was indeed installed in LFS and there is no reason to reinstall it unless you installed CrackLib or Linux-PAM after your LFS system was completed. If you have installed CrackLib after LFS, then reinstalling Shadow will enable strong password support. If you have installed Linux-PAM, reinstalling Shadow will allow programs such as login and su to utilize PAM.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/shadow-maint/shadow/releases/download/4.14.5/shadow-4.14.5.tar.xz
Download MD5 sum: 452b0e59f08bf618482228ba3732d0ae
Download size: 1.7 MB
Estimated disk space required: 38 MB
Estimated build time: 0.2 SBU

Shadow Dependencies

Required

Linux-PAM-1.6.0 or CrackLib-2.9.11

Optional

libbsd and tcb

Installation of Shadow

Important

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.

If you are reinstalling Shadow to provide strong password support using the CrackLib library without using Linux-PAM, ensure you add the --with-libcrack parameter to the configure script below and also issue the following command:

sed -i 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@' etc/login.defs

Warning

If reinstalling shadow for a version update, be sure to reaccomplish the Linux-PAM configuration below. The installation of shadow overwrites many of the files in /etc/pam.d/.

Reinstall Shadow by running the following commands:

sed -i 's/groups$(EXEEXT) //' src/Makefile.in          &&

find man -name Makefile.in -exec sed -i 's/groups\.1 / /'   {} \; &&
find man -name Makefile.in -exec sed -i 's/getspnam\.3 / /' {} \; &&
find man -name Makefile.in -exec sed -i 's/passwd\.5 / /'   {} \; &&

sed -e 's@#ENCRYPT_METHOD DES@ENCRYPT_METHOD YESCRYPT@' \
    -e 's@/var/spool/mail@/var/mail@'                   \
    -e '/PATH=/{s@/sbin:@@;s@/bin:@@}'                  \
    -i etc/login.defs                                   &&

./configure --sysconfdir=/etc   \
            --disable-static    \
            --without-libbsd    \
            --with-{b,yes}crypt &&
make

This package does not come with a test suite.

Now, as the root user:

make exec_prefix=/usr pamddir= install

The man pages were installed in LFS, but if reinstallation is desired, run (as the root user):

make -C man install-man

Command Explanations

sed -i 's/groups$(EXEEXT) //' src/Makefile.in: This sed is used to suppress the installation of the groups program as the version from the Coreutils package installed during LFS is preferred.

find man -name Makefile.in -exec ... {} \;: The first command is used to suppress the installation of the groups man pages so the existing ones installed from the Coreutils package are not replaced. The two other commands prevent installation of manual pages that are already installed by Man-pages in LFS.

sed -e 's@#ENCRYPT_METHOD DES@ENCRYPT_METHOD YESCRYPT@' -e 's@/var/spool/mail@/var/mail@' -e '/PATH=/{s@/sbin:@@;s@/bin:@@}' -i etc/login.defs: Instead of using the default 'DES' method, this command modifies the installation to use the much more secure 'YESCRYPT' method of hashing passwords, which also allows passwords longer than eight characters. The command also changes the obsolete /var/spool/mail location for user mailboxes that Shadow uses by default to the /var/mail location. It also changes the default path to be consistent with that set in LFS.

--without-libbsd: Prevents looking for the readpassphrase function, which can be found only in libbsd, which we do not have in BLFS. An internal implementation of readpassphrase is used instead.

pamddir=: Prevents installation of the shipped PAM configuration files into /etc/pam.d. The shipped configuration does not work with the BLFS PAM configuration and we will create these configuration files explicitly.

Configuring Linux-PAM to Work with Shadow

Note

The rest of this page is devoted to configuring Shadow to work properly with Linux-PAM. If you do not have Linux-PAM installed, and you reinstalled Shadow to support strong passwords via the CrackLib library, no further configuration is required.

Config Files

/etc/pam.d/* or alternatively /etc/pam.conf, /etc/login.defs and /etc/security/*

Configuration Information

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 functionality will work effectively with Linux-PAM. Review the information and links on the Linux-PAM-1.6.0 page for further configuration information. For information specific to integrating Shadow, Linux-PAM and libpwquality, you can visit the following link:

https://deer-run.com/users/hal/linux_passwords_pam.html

Configuring /etc/login.defs

The login program currently performs many functions 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 file named /etc/login.defs.orig is also created to preserve the original file's contents). Issue the following commands as the root user:

install -v -m644 /etc/login.defs /etc/login.defs.orig &&
for FUNCTION in FAIL_DELAY               \
                FAILLOG_ENAB             \
                LASTLOG_ENAB             \
                MAIL_CHECK_ENAB          \
                OBSCURE_CHECKS_ENAB      \
                PORTTIME_CHECKS_ENAB     \
                QUOTAS_ENAB              \
                CONSOLE MOTD_FILE        \
                FTMP_FILE NOLOGINS_FILE  \
                ENV_HZ PASS_MIN_LEN      \
                SU_WHEEL_ONLY            \
                CRACKLIB_DICTPATH        \
                PASS_CHANGE_TRIES        \
                PASS_ALWAYS_WARN         \
                CHFN_AUTH ENCRYPT_METHOD \
                ENVIRON_FILE
do
    sed -i "s/^${FUNCTION}/# &/" /etc/login.defs
done

Configuring the /etc/pam.d/ Files

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 /etc/pam.conf configuration file by using the text from the files below, and supplying the program name as an additional first field for each line.

As the root user, create 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:

'login'

cat > /etc/pam.d/login << "EOF"
# Begin /etc/pam.d/login

# Set failure delay before next prompt to 3 seconds
auth      optional    pam_faildelay.so  delay=3000000

# Check to make sure that the user is allowed to login
auth      requisite   pam_nologin.so

# Check to make sure that root is allowed to login
# Disabled by default. You will need to create /etc/securetty
# file for this module to function. See man 5 securetty.
#auth      required    pam_securetty.so

# Additional group memberships - disabled by default
#auth      optional    pam_group.so

# include system auth settings
auth      include     system-auth

# check access for the user
account   required    pam_access.so

# include system account settings
account   include     system-account

# Set default environment variables for the user
session   required    pam_env.so

# Set resource limits for the user
session   required    pam_limits.so

# Display the message of the day - Disabled by default
#session   optional    pam_motd.so

# Check user's mail - Disabled by default
#session   optional    pam_mail.so      standard quiet

# include system session and password settings
session   include     system-session
password  include     system-password

# End /etc/pam.d/login
EOF

'passwd'

cat > /etc/pam.d/passwd << "EOF"
# Begin /etc/pam.d/passwd

password  include     system-password

# End /etc/pam.d/passwd
EOF

'su'

cat > /etc/pam.d/su << "EOF"
# Begin /etc/pam.d/su

# always allow root
auth      sufficient  pam_rootok.so

# Allow users in the wheel group to execute su without a password
# disabled by default
#auth      sufficient  pam_wheel.so trust use_uid

# include system auth settings
auth      include     system-auth

# limit su to users in the wheel group
# disabled by default
#auth      required    pam_wheel.so use_uid

# include system account settings
account   include     system-account

# Set default environment variables for the service user
session   required    pam_env.so

# include system session settings
session   include     system-session

# End /etc/pam.d/su
EOF

'chpasswd' and 'newusers'

cat > /etc/pam.d/chpasswd << "EOF"
# Begin /etc/pam.d/chpasswd

# always allow root
auth      sufficient  pam_rootok.so

# include system auth and account settings
auth      include     system-auth
account   include     system-account
password  include     system-password

# End /etc/pam.d/chpasswd
EOF

sed -e s/chpasswd/newusers/ /etc/pam.d/chpasswd >/etc/pam.d/newusers

'chage'

cat > /etc/pam.d/chage << "EOF"
# Begin /etc/pam.d/chage

# always allow root
auth      sufficient  pam_rootok.so

# include system auth and account settings
auth      include     system-auth
account   include     system-account

# End /etc/pam.d/chage
EOF

Other shadow utilities

for PROGRAM in chfn chgpasswd chsh groupadd groupdel \
               groupmems groupmod useradd userdel usermod
do
    install -v -m644 /etc/pam.d/chage /etc/pam.d/${PROGRAM}
    sed -i "s/chage/$PROGRAM/" /etc/pam.d/${PROGRAM}
done

Warning

At this point, you should do a simple test to see if 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 not see any errors, then all is well and you should proceed with the rest of the configuration. If you did receive errors, stop 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 to assist you in determining the problem. If you cannot find and fix the error, you should recompile Shadow adding the --without-libpam switch to the configure command in the above instructions (also move the /etc/login.defs.orig backup file to /etc/login.defs). If you fail to do this and the errors remain, you will be unable to log into your system.

Configuring Login Access

Instead of using the /etc/login.access file for 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 following command:

if [ -f /etc/login.access ]; then mv -v /etc/login.access{,.NOUSE}; fi

Configuring Resource Limits

Instead of using the /etc/limits file for limiting usage of system resources, 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:

if [ -f /etc/limits ]; then mv -v /etc/limits{,.NOUSE}; fi

Caution

Be sure to test the login capabilities of the system before logging out. Errors in the configuration can cause a permanent lockout requiring a boot from an external source to correct the problem.

A list of the installed files, along with their short descriptions can be found at ../../../../lfs/view/12.1/chapter08/shadow.html#contents-shadow.

ssh-askpass-9.6p1

Introduction to ssh-askpass

The ssh-askpass is a generic executable name for many packages, with similar names, that provide a interactive X service to grab password for packages requiring administrative privileges to be run. It prompts the user with a window box where the necessary password can be inserted. Here, we choose Damien Miller's package distributed in the OpenSSH tarball.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-9.6p1.tar.gz
Download MD5 sum: 5e90def5af3ffb27e149ca6fff12bef3
Download size: 1.8 MB
Estimated disk space required: 10 MB
Estimated build time: less than 0.1 SBU

ssh-askpass Dependencies

Required

GTK+-3.24.41, Sudo-1.9.15p5 (runtime), Xorg Libraries, and a graphical environment (runtime)

Installation of ssh-askpass

Install ssh-askpass by running the following commands:

cd contrib &&
make gnome-ssh-askpass3

Now, as the root user:

install -v -d -m755                    /usr/libexec/openssh/contrib  &&
install -v -m755    gnome-ssh-askpass3 /usr/libexec/openssh/contrib  &&
ln -sv -f contrib/gnome-ssh-askpass3   /usr/libexec/openssh/ssh-askpass

The use of /usr/libexec/openssh/contrib and a symlink is justified by the eventual necessity of a different program for that service.

Configuring ssh-askpass

Configuration Information

As the root user, configure Sudo-1.9.15p5 to use ssh-askpass:

cat >> /etc/sudo.conf << "EOF" &&
# Path to askpass helper program
Path askpass /usr/libexec/openssh/ssh-askpass
EOF
chmod -v 0644 /etc/sudo.conf

If a given graphical <application> requires administrative privileges, use sudo -A <application> from an x-terminal, from a Window Manager menu and/or replace "Exec=<application> ..." by "Exec=sudo -A <application> ..." in the <application>.desktop file.

Installed Programs: gnome-ssh-askpass3, ssh-askpass (symlink to gnome-ssh-askpass3)

Installed Library: None

Installed Directory: /usr/libexec/openssh/contrib

stunnel-5.72

Introduction to stunnel

The stunnel package contains a program that allows you to encrypt arbitrary TCP connections inside SSL (Secure Sockets Layer) so you can easily communicate with clients over secure channels. stunnel can also be used to tunnel PPP over network sockets without changes to the server package source code.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.stunnel.org/downloads/archive/5.x/stunnel-5.72.tar.gz
Download MD5 sum: 61d35d2df1b96b23ed6fb20cf5ddb613
Download size: 880 KB
Estimated disk space required: 7.5 MB
Estimated build time: less than 0.1 SBU

stunnel Dependencies

Optional

libnsl-2.0.1, netcat (required for tests), tcpwrappers, and TOR

Installation of stunnel

The stunnel daemon will be run in a chroot jail by an unprivileged user. Create the new user and group using the following commands as the root user:

groupadd -g 51 stunnel &&
useradd -c "stunnel Daemon" -d /var/lib/stunnel \
        -g stunnel -s /bin/false -u 51 stunnel

Note

A signed SSL Certificate and a Private Key is necessary to run the stunnel daemon. After the package is installed, there are instructions to generate them. However, if you own or have already created a signed SSL Certificate you wish to use, copy it to /etc/stunnel/stunnel.pem before starting the build (ensure only root has read and write access). The .pem file must be formatted as shown below:

Install stunnel by running the following commands:

./configure --prefix=/usr        \
            --sysconfdir=/etc    \
            --localstatedir=/var \
            --disable-systemd    &&
make

If you have installed the optional netcat application, the regression tests can be run with make check.

Now, as the root user:

make docdir=/usr/share/doc/stunnel-5.72 install

If you do not already have a signed SSL Certificate and Private Key, create the stunnel.pem file in the /etc/stunnel directory using the command below. You will be prompted to enter the necessary information. Ensure you reply to the

Common Name (FQDN of your server) [localhost]:

prompt with the name or IP address you will be using to access the service(s).

To generate a certificate, as the root user, issue:

make cert

Command Explanations

--disable-systemd: This switch disables systemd socket activation support which is not available in BLFS.

make docdir=... install: This command installs the package and changes the documentation installation directory to standard naming conventions.

Configuring stunnel

Config Files

/etc/stunnel/stunnel.conf

Configuration Information

As the root user, create the directory used for the .pid file created when the stunnel daemon starts:

install -v -m750 -o stunnel -g stunnel -d /var/lib/stunnel/run &&
chown stunnel:stunnel /var/lib/stunnel

Next, create a basic /etc/stunnel/stunnel.conf configuration file using the following commands as the root user:

cat > /etc/stunnel/stunnel.conf << "EOF"
; File: /etc/stunnel/stunnel.conf

; Note: The pid and output locations are relative to the chroot location.

pid    = /run/stunnel.pid
chroot = /var/lib/stunnel
client = no
setuid = stunnel
setgid = stunnel
cert   = /etc/stunnel/stunnel.pem

;debug = 7
;output = stunnel.log

;[https]
;accept  = 443
;connect = 80
;; "TIMEOUTclose = 0" is a workaround for a design flaw in Microsoft SSL
;; Microsoft implementations do not use SSL close-notify alert and thus
;; they are vulnerable to truncation attacks
;TIMEOUTclose = 0

EOF

Finally, add the service(s) you wish to encrypt to the configuration file. The format is as follows:

[<service>]
accept  = <hostname:portnumber>
connect = <hostname:portnumber>

For a full explanation of the commands and syntax used in the configuration file, issue man stunnel.

Boot Script

To automatically start the stunnel daemon when the system is booted, install the /etc/rc.d/init.d/stunnel bootscript from the blfs-bootscripts-20240209 package.

make install-stunnel

Installed Programs: stunnel and stunnel3

Installed Library: libstunnel.so

Installed Directories: /{etc,lib,var/lib}/stunnel and /usr/share/doc/stunnel-5.72

Short Descriptions

stunnel	is a program designed to work as an SSL encryption wrapper between remote clients and local or remote servers
stunnel3	is a Perl wrapper script to use stunnel 3.x syntax with stunnel 4.05 or later
`libstunnel.so`	contains the API functions required by stunnel

Sudo-1.9.15p5

Introduction to Sudo

The Sudo package allows a system administrator to give certain users (or groups of users) the ability to run some (or all) commands as root or another user while logging the commands and arguments.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.sudo.ws/dist/sudo-1.9.15p5.tar.gz
Download MD5 sum: 4166279cb188ecb6641c7a2ba5f68270
Download size: 5.1 MB
Estimated disk space required: 53 MB (add 18 MB for tests)
Estimated build time: 0.2 SBU (with parallelism=4; add 0.1 SBU for tests)

Sudo Dependencies

Optional

Linux-PAM-1.6.0, MIT Kerberos V5-1.21.2, OpenLDAP-2.6.7, MTA (that provides a sendmail command), AFS, libaudit, Opie, and Sssd

Installation of Sudo

Install Sudo by running the following commands:

./configure --prefix=/usr              \
            --libexecdir=/usr/lib      \
            --with-secure-path         \
            --with-env-editor          \
            --docdir=/usr/share/doc/sudo-1.9.15p5 \
            --with-passprompt="[sudo] password for %p: " &&
make

To test the results, issue: env LC_ALL=C make check |& tee make-check.log. Check the results with grep failed make-check.log.

Now, as the root user:

make install

Command Explanations

--libexecdir=/usr/lib: This switch controls where private programs are installed. Everything in that directory is a library, so they belong under /usr/lib instead of /usr/libexec.

--with-secure-path: This switch transparently adds /sbin and /usr/sbin directories to the PATH environment variable.

--with-env-editor: This switch enables use of the environment variable EDITOR for visudo.

--with-passprompt: This switch sets the password prompt. The %p will be expanded to the name of the user whose password is being requested.

--without-pam: This switch avoids building Linux-PAM support when Linux-PAM is installed on the system.

--with-all-insults: This switch includes all the sudo insult sets. Insults are printed if the user types a bad password, and if enabled in /etc/sudoers. Use --with-insults to have them enabled by default. Various sets of insults can be selected with some other switches.

Note

There are many options to sudo's configure command. Check the configure --help output for a complete list.

Configuring Sudo

Config File

/etc/sudoers

Configuration Information

The sudoers file can be quite complicated. It is composed of two types of entries: aliases (basically variables) and user specifications (which specify who may run what). The installation installs a default configuration that has no privileges installed for any user.

A couple of common configuration changes are to set the path for the super user and to allow members of the wheel group to execute all commands after providing their own credentials. Use the following commands to create the /etc/sudoers.d/00-sudo configuration file as the root user:

cat > /etc/sudoers.d/00-sudo << "EOF"
Defaults secure_path="/usr/sbin:/usr/bin"
%wheel ALL=(ALL) ALL
EOF

Note

In very simple installations where there is only one user, it may be easier to just edit the /etc/sudoers file directly. In that case, the secure_path entry may not be needed and using sudo -E ... can import the non-privileged user's full environment into the privileged session.

The files in the /etc/sudoers.d directory are parsed in sorted lexical order. Be careful that entries in an added file do not overwrite previous entries.

For details, see man sudoers.

Note

The Sudo developers highly recommend using the visudo program to edit the sudoers file. This will provide basic sanity checking like syntax parsing and file permission to avoid some possible mistakes that could lead to a vulnerable configuration.

If PAM is installed on the system, Sudo is built with PAM support. In that case, issue the following command as the root user to create the PAM configuration file:

cat > /etc/pam.d/sudo << "EOF"
# Begin /etc/pam.d/sudo

# include the default auth settings
auth      include     system-auth

# include the default account settings
account   include     system-account

# Set default environment variables for the service user
session   required    pam_env.so

# include system session defaults
session   include     system-session

# End /etc/pam.d/sudo
EOF
chmod 644 /etc/pam.d/sudo

Installed Programs: cvtsudoers, sudo, sudo_logsrvd, sudo_sendlog, sudoedit (symlink), sudoreplay, and visudo

Installed Libraries: audit_json.so, group_file.so, libsudo_util.so, sudoers.so, sudo_intercept.so, sudo_noexec.so, and system_group.so

Installed Directories: /etc/sudoers.d, /usr/lib/sudo, /usr/share/doc/sudo-1.9.15p5, and /var/lib/sudo

Short Descriptions

cvtsudoers	converts between sudoers file formats
sudo	executes a command as another user as permitted by the `/etc/sudoers` configuration file
sudo_logsrvd	is a sudo event and I/O log server
sudo_sendlog	sends sudo I/O logs to the log server
sudoedit	is a symlink to sudo that implies the `-e` option to invoke an editor as another user
sudoreplay	is used to play back or list the output logs created by sudo
visudo	allows for safer editing of the `sudoers` file

Tripwire-2.4.3.7

Introduction to Tripwire

The Tripwire package contains programs used to verify the integrity of the files on a given system.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/Tripwire/tripwire-open-source/releases/download/2.4.3.7/tripwire-open-source-2.4.3.7.tar.gz
Download MD5 sum: a5cf1bc2f235f5d8ca458f00548db6ee
Download size: 980 KB
Estimated disk space required: 29 MB
Estimated build time: 1.6 SBU (scripting install)

Tripwire Dependencies

Optional

An MTA

Installation of Tripwire

Compile Tripwire by running the following commands:

sed -e '/^CLOBBER/s/false/true/'         \
    -e 's|TWDB="${prefix}|TWDB="/var|'   \
    -e '/TWMAN/ s|${prefix}|/usr/share|' \
    -e '/TWDOCS/s|${prefix}/doc/tripwire|/usr/share/doc/tripwire-2.4.3.7|' \
    -i installer/install.cfg                               &&

find . -name Makefile.am | xargs                           \
    sed -i 's/^[[:alpha:]_]*_HEADERS.*=/noinst_HEADERS =/' &&

sed '/dist/d' -i man/man?/Makefile.am                      &&
autoreconf -fi                                             &&

./configure --prefix=/usr --sysconfdir=/etc/tripwire       &&
make CPPFLAGS=-std=c++11

Note

The default configuration is to use a local MTA. If you don't have an MTA installed and have no wish to install one, modify install/install.cfg to use an SMTP server instead. Otherwise the install will fail.

This package does not come with a test suite.

Now, as the root user:

make install &&
cp -v policy/*.txt /usr/share/doc/tripwire-2.4.3.7

Note

During make install, several questions are asked, including passwords. If you want to make a script, you have to apply a sed before running make install:

sed -i -e 's@installer/install.sh@& -n -s <site-password> -l <local-password>@' Makefile

Of course, you should do this with dummy passwords and change them later.

Another issue when scripting is that the installer exits when the standard input is not a terminal. You may disable this behavior with the following sed:

sed '/-t 0/,+3d' -i installer/install.sh

Command Explanations

sed ... installer/install.cfg: This command tells the package to install the program database and reports in /var/lib/tripwire and sets the proper location for man pages and documentation.

find ..., sed ..., and autoreconf -fi: The build system is unusable as is, and has to be modified for the build to succeed.

CPPFLAGS=-std=c++11: Setting the C++ preprocessor flags to version 11 is necessary to prevent a conflict with the default version which is c++17 in recent version of gcc.

make install: This command creates the Tripwire security keys as well as installing the binaries. There are two keys: a site key and a local key which are stored in /etc/tripwire/.

cp -v policy/*.txt /usr/doc/tripwire-2.4.3.7: This command installs the tripwire sample policy files with the other tripwire documentation.i

Configuring Tripwire

Config Files

/etc/tripwire/*

Configuration Information

Tripwire uses a policy file to determine which files are integrity checked. The default policy file (/etc/tripwire/twpol.txt) is for a default installation and will need to be updated for your system.

Policy files should be tailored to each individual distribution and/or installation. Some example policy files can be found in /usr/share/doc/tripwire/.

If desired, copy the policy file you'd like to try into /etc/tripwire/ instead of using the default policy file, twpol.txt. It is, however, recommended that you edit your policy file. Get ideas from the examples above and read /usr/share/doc/tripwire/policyguide.txt for additional information. twpol.txt is a good policy file for learning about Tripwire as it will note any changes to the file system and can even be used as an annoying way of keeping track of changes for uninstallation of software.

After your policy file has been edited to your satisfaction you may begin the configuration steps (perform as the root) user:

twadmin --create-polfile --site-keyfile /etc/tripwire/site.key \
    /etc/tripwire/twpol.txt &&
tripwire --init

Depending on your system and the contents of the policy file, the initialization phase above can take a relatively long time.

Usage Information

Tripwire will identify file changes in the critical system files specified in the policy file. Using Tripwire while making frequent changes to these directories will flag all these changes. It is most useful after a system has reached a configuration that the user considers stable.

To use Tripwire after creating a policy file to run a report, use the following command:

tripwire --check > /etc/tripwire/report.txt

View the output to check the integrity of your files. An automatic integrity report can be produced by using a cron facility to schedule the runs.

Reports are stored in binary and, if desired, encrypted. View reports, as the root user, with:

twprint --print-report -r /var/lib/tripwire/report/<report-name.twr>

After you run an integrity check, you should examine the report (or email) and then modify the Tripwire database to reflect the changed files on your system. This is so that Tripwire will not continually notify you hat files you intentionally changed are a security violation. To do this you must first ls -l /var/lib/tripwire/report/ and note the name of the newest file which starts with your system name as presented by the command uname -n and ends in .twr. These files were created during report creation and the most current one is needed to update the Tripwire database of your system. As the root user, type in the following command making the appropriate report name:

tripwire --update --twrfile /var/lib/tripwire/report/<report-name.twr>

You will be placed into Vim with a copy of the report in front of you. If all the changes were good, then just type :wq and after entering your local key, the database will be updated. If there are files which you still want to be warned about, remove the 'x' before the filename in the report and type :wq.

Changing the Policy File

If you are unhappy with your policy file and would like to modify it or use a new one, modify the policy file and then execute the following commands as the root user:

twadmin --create-polfile /etc/tripwire/twpol.txt &&
tripwire --init

Installed Programs: siggen, tripwire, twadmin, and twprint

Installed Libraries: None

Installed Directories: /etc/tripwire, /var/lib/tripwire, and /usr/share/doc/tripwire-2.4.3.7

Short Descriptions

siggen	is a signature gathering utility that displays the hash function values for the specified files
tripwire	is the main file integrity checking program
twadmin	administrative and utility tool used to perform certain administrative functions related to Tripwire files and configuration options
twprint	prints Tripwire database and report files in clear text format

Chapter 5. File Systems and Disk Management

Journaling file systems reduce the time needed to recover a file system that was not unmounted properly. While this can be extremely important in reducing downtime for servers, it has also become popular for desktop environments. This chapter contains other journaling file systems you can use instead of the default LFS extended file system (ext2/3/4). It also provides introductory material on managing disk arrays.

About initramfs

The only purpose of an initramfs is to mount the root filesystem. The initramfs is a complete set of directories that you would find on a normal root filesystem. It is bundled into a single cpio archive and compressed with one of several compression algorithms.

At boot time, the boot loader loads the kernel and the initramfs image into memory and starts the kernel. The kernel checks for the presence of the initramfs and, if found, mounts it as / and runs /init. The init program is typically a shell script. Note that the boot process takes longer, possibly significantly longer, if an initramfs is used.

For most distributions, kernel modules are the biggest reason to have an initramfs. In a general distribution, there are many unknowns such as file system types and disk layouts. In a way, this is the opposite of LFS where the system capabilities and layout are known and a custom kernel is normally built. In this situation, an initramfs is rarely needed.

There are only four primary reasons to have an initramfs in the LFS environment: loading the rootfs from a network, loading it from an LVM logical volume, having an encrypted rootfs where a password is required, or for the convenience of specifying the rootfs as a LABEL or UUID. Anything else usually means that the kernel was not configured properly.

Building an initramfs

If you do decide to build an initramfs, the following scripts will provide a basis to do it. The scripts will allow specifying a rootfs via partition UUID or partition LABEL or a rootfs on an LVM logical volume. They do not support an encrypted root file system or mounting the rootfs over a network card. For a more complete capability see the LFS Hints or dracut.

To install these scripts, run the following commands as the root user:

cat > /usr/sbin/mkinitramfs << "EOF"
#!/bin/bash
# This file based in part on the mkinitramfs script for the LFS LiveCD
# written by Alexander E. Patrakov and Jeremy Huntwork.

copy()
{
  local file

  if [ "$2" = "lib" ]; then
    file=$(PATH=/usr/lib type -p $1)
  else
    file=$(type -p $1)
  fi

  if [ -n "$file" ] ; then
    cp $file $WDIR/usr/$2
  else
    echo "Missing required file: $1 for directory $2"
    rm -rf $WDIR
    exit 1
  fi
}

if [ -z $1 ] ; then
  INITRAMFS_FILE=initrd.img-no-kmods
else
  KERNEL_VERSION=$1
  INITRAMFS_FILE=initrd.img-$KERNEL_VERSION
fi

if [ -n "$KERNEL_VERSION" ] && [ ! -d "/usr/lib/modules/$1" ] ; then
  echo "No modules directory named $1"
  exit 1
fi

printf "Creating $INITRAMFS_FILE... "

binfiles="sh cat cp dd killall ls mkdir mknod mount "
binfiles="$binfiles umount sed sleep ln rm uname"
binfiles="$binfiles readlink basename"

# Systemd installs udevadm in /bin. Other udev implementations have it in /sbin
if [ -x /usr/bin/udevadm ] ; then binfiles="$binfiles udevadm"; fi

sbinfiles="modprobe blkid switch_root"

# Optional files and locations
for f in mdadm mdmon udevd udevadm; do
  if [ -x /usr/sbin/$f ] ; then sbinfiles="$sbinfiles $f"; fi
done

# Add lvm if present (cannot be done with the others because it
# also needs dmsetup
if [ -x /usr/sbin/lvm ] ; then sbinfiles="$sbinfiles lvm dmsetup"; fi

unsorted=$(mktemp /tmp/unsorted.XXXXXXXXXX)

DATADIR=/usr/share/mkinitramfs
INITIN=init.in

# Create a temporary working directory
WDIR=$(mktemp -d /tmp/initrd-work.XXXXXXXXXX)

# Create base directory structure
mkdir -p $WDIR/{dev,run,sys,proc,usr/{bin,lib/{firmware,modules},sbin}}
mkdir -p $WDIR/etc/{modprobe.d,udev/rules.d}
touch $WDIR/etc/modprobe.d/modprobe.conf
ln -s usr/bin  $WDIR/bin
ln -s usr/lib  $WDIR/lib
ln -s usr/sbin $WDIR/sbin
ln -s lib      $WDIR/lib64

# Create necessary device nodes
mknod -m 640 $WDIR/dev/console c 5 1
mknod -m 664 $WDIR/dev/null    c 1 3

# Install the udev configuration files
if [ -f /etc/udev/udev.conf ]; then
  cp /etc/udev/udev.conf $WDIR/etc/udev/udev.conf
fi

for file in $(find /etc/udev/rules.d/ -type f) ; do
  cp $file $WDIR/etc/udev/rules.d
done

# Install any firmware present
cp -a /usr/lib/firmware $WDIR/usr/lib

# Copy the RAID configuration file if present
if [ -f /etc/mdadm.conf ] ; then
  cp /etc/mdadm.conf $WDIR/etc
fi

# Install the init file
install -m0755 $DATADIR/$INITIN $WDIR/init

if [  -n "$KERNEL_VERSION" ] ; then
  if [ -x /usr/bin/kmod ] ; then
    binfiles="$binfiles kmod"
  else
    binfiles="$binfiles lsmod"
    sbinfiles="$sbinfiles insmod"
  fi
fi

# Install basic binaries
for f in $binfiles ; do
  ldd /usr/bin/$f | sed "s/\t//" | cut -d " " -f1 >> $unsorted
  copy /usr/bin/$f bin
done

for f in $sbinfiles ; do
  ldd /usr/sbin/$f | sed "s/\t//" | cut -d " " -f1 >> $unsorted
  copy $f sbin
done

# Add udevd libraries if not in /usr/sbin
if [ -x /usr/lib/udev/udevd ] ; then
  ldd /usr/lib/udev/udevd | sed "s/\t//" | cut -d " " -f1 >> $unsorted
elif [ -x /usr/lib/systemd/systemd-udevd ] ; then
  ldd /usr/lib/systemd/systemd-udevd | sed "s/\t//" | cut -d " " -f1 >> $unsorted
fi

# Add module symlinks if appropriate
if [ -n "$KERNEL_VERSION" ] && [ -x /usr/bin/kmod ] ; then
  ln -s kmod $WDIR/usr/bin/lsmod
  ln -s kmod $WDIR/usr/bin/insmod
fi

# Add lvm symlinks if appropriate
# Also copy the lvm.conf file
if  [ -x /usr/sbin/lvm ] ; then
  ln -s lvm $WDIR/usr/sbin/lvchange
  ln -s lvm $WDIR/usr/sbin/lvrename
  ln -s lvm $WDIR/usr/sbin/lvextend
  ln -s lvm $WDIR/usr/sbin/lvcreate
  ln -s lvm $WDIR/usr/sbin/lvdisplay
  ln -s lvm $WDIR/usr/sbin/lvscan

  ln -s lvm $WDIR/usr/sbin/pvchange
  ln -s lvm $WDIR/usr/sbin/pvck
  ln -s lvm $WDIR/usr/sbin/pvcreate
  ln -s lvm $WDIR/usr/sbin/pvdisplay
  ln -s lvm $WDIR/usr/sbin/pvscan

  ln -s lvm $WDIR/usr/sbin/vgchange
  ln -s lvm $WDIR/usr/sbin/vgcreate
  ln -s lvm $WDIR/usr/sbin/vgscan
  ln -s lvm $WDIR/usr/sbin/vgrename
  ln -s lvm $WDIR/usr/sbin/vgck
  # Conf file(s)
  cp -a /etc/lvm $WDIR/etc
fi

# Install libraries
sort $unsorted | uniq | while read library ; do
# linux-vdso and linux-gate are pseudo libraries and do not correspond to a file
# libsystemd-shared is in /lib/systemd, so it is not found by copy, and
# it is copied below anyway
  if [[ "$library" == linux-vdso.so.1 ]] ||
     [[ "$library" == linux-gate.so.1 ]] ||
     [[ "$library" == libsystemd-shared* ]]; then
    continue
  fi

  copy $library lib
done

if [ -d /usr/lib/udev ]; then
  cp -a /usr/lib/udev $WDIR/usr/lib
fi
if [ -d /usr/lib/systemd ]; then
  cp -a /usr/lib/systemd $WDIR/usr/lib
fi
if [ -d /usr/lib/elogind ]; then
  cp -a /usr/lib/elogind $WDIR/usr/lib
fi

# Install the kernel modules if requested
if [ -n "$KERNEL_VERSION" ]; then
  find \
     /usr/lib/modules/$KERNEL_VERSION/kernel/{crypto,fs,lib}                      \
     /usr/lib/modules/$KERNEL_VERSION/kernel/drivers/{block,ata,nvme,md,firewire} \
     /usr/lib/modules/$KERNEL_VERSION/kernel/drivers/{scsi,message,pcmcia,virtio} \
     /usr/lib/modules/$KERNEL_VERSION/kernel/drivers/usb/{host,storage}           \
     -type f 2> /dev/null | cpio --make-directories -p --quiet $WDIR

  cp /usr/lib/modules/$KERNEL_VERSION/modules.{builtin,order} \
            $WDIR/usr/lib/modules/$KERNEL_VERSION
  if [ -f /usr/lib/modules/$KERNEL_VERSION/modules.builtin.modinfo ]; then
    cp /usr/lib/modules/$KERNEL_VERSION/modules.builtin.modinfo \
            $WDIR/usr/lib/modules/$KERNEL_VERSION
  fi

  depmod -b $WDIR $KERNEL_VERSION
fi

( cd $WDIR ; find . | cpio -o -H newc --quiet | gzip -9 ) > $INITRAMFS_FILE

# Prepare early loading of microcode if available
if ls /usr/lib/firmware/intel-ucode/* >/dev/null 2>&1 ||
   ls /usr/lib/firmware/amd-ucode/*   >/dev/null 2>&1; then

# first empty WDIR to reuse it
  rm -r $WDIR/*

  DSTDIR=$WDIR/kernel/x86/microcode
  mkdir -p $DSTDIR

  if [ -d /usr/lib/firmware/amd-ucode ]; then
    cat /usr/lib/firmware/amd-ucode/microcode_amd*.bin > $DSTDIR/AuthenticAMD.bin
  fi

  if [ -d /usr/lib/firmware/intel-ucode ]; then
    cat /usr/lib/firmware/intel-ucode/* > $DSTDIR/GenuineIntel.bin
  fi

  ( cd $WDIR; find . | cpio -o -H newc --quiet ) > microcode.img
  cat microcode.img $INITRAMFS_FILE > tmpfile
  mv tmpfile $INITRAMFS_FILE
  rm microcode.img
fi

# Remove the temporary directories and files
rm -rf $WDIR $unsorted
printf "done.\n"

EOF

chmod 0755 /usr/sbin/mkinitramfs

mkdir -p /usr/share/mkinitramfs &&
cat > /usr/share/mkinitramfs/init.in << "EOF"
#!/bin/sh

PATH=/usr/bin:/usr/sbin
export PATH

problem()
{
   printf "Encountered a problem!\n\nDropping you to a shell.\n\n"
   sh
}

no_device()
{
   printf "The device %s, which is supposed to contain the\n" $1
   printf "root file system, does not exist.\n"
   printf "Please fix this problem and exit this shell.\n\n"
}

no_mount()
{
   printf "Could not mount device %s\n" $1
   printf "Sleeping forever. Please reboot and fix the kernel command line.\n\n"
   printf "Maybe the device is formatted with an unsupported file system?\n\n"
   printf "Or maybe filesystem type autodetection went wrong, in which case\n"
   printf "you should add the rootfstype=... parameter to the kernel command line.\n\n"
   printf "Available partitions:\n"
}

do_mount_root()
{
   mkdir /.root
   [ -n "$rootflags" ] && rootflags="$rootflags,"
   rootflags="$rootflags$ro"

   case "$root" in
      /dev/*    ) device=$root ;;
      UUID=*    ) eval $root; device="/dev/disk/by-uuid/$UUID" ;;
      PARTUUID=*) eval $root; device="/dev/disk/by-partuuid/$PARTUUID" ;;
      LABEL=*   ) eval $root; device="/dev/disk/by-label/$LABEL" ;;
      ""        ) echo "No root device specified." ; problem ;;
   esac

   while [ ! -b "$device" ] ; do
       no_device $device
       problem
   done

   if ! mount -n -t "$rootfstype" -o "$rootflags" "$device" /.root ; then
       no_mount $device
       cat /proc/partitions
       while true ; do sleep 10000 ; done
   else
       echo "Successfully mounted device $root"
   fi
}

do_try_resume()
{
   case "$resume" in
      UUID=* ) eval $resume; resume="/dev/disk/by-uuid/$UUID"  ;;
      LABEL=*) eval $resume; resume="/dev/disk/by-label/$LABEL" ;;
   esac

   if $noresume || ! [ -b "$resume" ]; then return; fi

   ls -lH "$resume" | ( read x x x x maj min x
       echo -n ${maj%,}:$min > /sys/power/resume )
}

init=/sbin/init
root=
rootdelay=
rootfstype=auto
ro="ro"
rootflags=
device=
resume=
noresume=false

mount -n -t devtmpfs devtmpfs /dev
mount -n -t proc     proc     /proc
mount -n -t sysfs    sysfs    /sys
mount -n -t tmpfs    tmpfs    /run

read -r cmdline < /proc/cmdline

for param in $cmdline ; do
  case $param in
    init=*      ) init=${param#init=}             ;;
    root=*      ) root=${param#root=}             ;;
    rootdelay=* ) rootdelay=${param#rootdelay=}   ;;
    rootfstype=*) rootfstype=${param#rootfstype=} ;;
    rootflags=* ) rootflags=${param#rootflags=}   ;;
    resume=*    ) resume=${param#resume=}         ;;
    noresume    ) noresume=true                   ;;
    ro          ) ro="ro"                         ;;
    rw          ) ro="rw"                         ;;
  esac
done

# udevd location depends on version
if [ -x /sbin/udevd ]; then
  UDEVD=/sbin/udevd
elif [ -x /lib/udev/udevd ]; then
  UDEVD=/lib/udev/udevd
elif [ -x /lib/systemd/systemd-udevd ]; then
  UDEVD=/lib/systemd/systemd-udevd
else
  echo "Cannot find udevd nor systemd-udevd"
  problem
fi

${UDEVD} --daemon --resolve-names=never
udevadm trigger
udevadm settle

if [ -f /etc/mdadm.conf ] ; then mdadm -As                       ; fi
if [ -x /sbin/vgchange  ] ; then /sbin/vgchange -a y > /dev/null ; fi
if [ -n "$rootdelay"    ] ; then sleep "$rootdelay"              ; fi

do_try_resume # This function will not return if resuming from disk
do_mount_root

killall -w ${UDEVD##*/}

exec switch_root /.root "$init" "$@"

EOF

Using an initramfs

Required Runtime Dependency

cpio-2.15

Other Runtime Dependencies

LVM2-2.03.23 and/or mdadm-4.2 must be installed before generating the initramfs, if the system partition uses them.

To build an initramfs, run the following as the root user:

mkinitramfs [KERNEL VERSION]

The optional argument is the directory where the appropriate kernel modules are located. This must be a subdirectory of /lib/modules. If no modules are specified, then the initramfs is named initrd.img-no-kmods. If a kernel version is specified, the initrd is named initrd.img-$KERNEL_VERSION and is only appropriate for the specific kernel specified. The output file will be placed in the current directory.

If early loading of microcode is needed (see the section called “Microcode updates for CPUs”), you can install the appropriate blob or container in /lib/firmware. It will be automatically added to the initrd when running mkinitramfs.

After generating the initrd, copy it to the /boot directory.

Now edit /boot/grub/grub.cfg and add a new menuentry. Below are several examples.

# Generic initramfs and root fs identified by UUID
menuentry "LFS Dev (LFS-7.0-Feb14) initrd, Linux 3.0.4"
{
  linux  /vmlinuz-3.0.4-lfs-20120214 root=UUID=54b934a9-302d-415e-ac11-4988408eb0a8 ro
  initrd /initrd.img-no-kmods
}

# Generic initramfs and root fs on LVM partition
menuentry "LFS Dev (LFS-7.0-Feb18) initrd lvm, Linux 3.0.4"
{
  linux  /vmlinuz-3.0.4-lfs-20120218 root=/dev/mapper/myroot ro
  initrd /initrd.img-no-kmods
}

# Specific initramfs and root fs identified by LABEL
menuentry "LFS Dev (LFS-7.1-Feb20) initrd label, Linux 3.2.6"
{
  linux  /vmlinuz-3.2.6-lfs71-120220 root=LABEL=lfs71 ro
  initrd /initrd.img-3.2.6-lfs71-120220
}

Finally, reboot the system and select the desired system.

btrfs-progs-6.7.1

Introduction to btrfs-progs

The btrfs-progs package contains administration and debugging tools for the B-tree file system (btrfs).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/btrfs-progs-v6.7.1.tar.xz
Download MD5 sum: 3898c68efdc0fe4e3a6a1bd90b3b4fa4
Download size: 2.4 MB
Estimated disk space required: 62 MB (transient files created during tests need up to 10 GB)
Estimated build time: 0.3 SBU (with parallelism=4; add 4.6 SBU for tests, up to 14 SBU on slow disks)

Btrfs-progs Dependencies

Required

LZO-2.10

Optional

LVM2-2.03.23 (dmsetup is used in tests), sphinx-7.2.6 and sphinx_rtd_theme-2.0.0 (required to build documentation), and reiserfsprogs (for tests).

Kernel Configuration

Enable the following option in the kernel configuration and recompile the kernel:

File systems --->
  <*/M> Btrfs filesystem support                                      [BTRFS_FS]

In addition to the above and to the options required for LVM2-2.03.23, the following options must be enabled for running tests:

File systems --->
  <*/M> Btrfs filesystem support                                      [BTRFS_FS]
  [*]     Btrfs POSIX Access Control Lists                  [BTRFS_FS_POSIX_ACL]

Installation of btrfs-progs

Install btrfs-progs by running the following commands:

./configure --prefix=/usr           \
            --disable-static        \
            --disable-documentation &&
make

Note

Some tests require grep built with perl regular expressions. To obtain this, rebuild grep with the LFS Chapter 8 instructions after installing pcre2-10.42.

Before running tests, build a support program:

make fssum

To test the results, issue (as the root user):

pushd tests
   ./fsck-tests.sh
   ./mkfs-tests.sh
   ./cli-tests.sh
   ./convert-tests.sh
   ./misc-tests.sh
   ./fuzz-tests.sh
popd

Note

If the above mentioned kernel options are not enabled, some tests fail, and prevent all the remaining tests from running because the test disk image is not cleanly unmounted.

Install the package as the root user:

make install

If you have passed --disable-documentation to configure and you need the manual pages, install them by running, as the root user:

for i in 5 8; do
   install Documentation/*.$i /usr/share/man/man$i
done

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--disable-documentation: This switch disables rebuilding the manual pages, because it requires sphinx-7.2.6.

Installed Programs: btrfs, btrfs-convert, btrfs-find-root, btrfs-image, btrfs-map-logical, btrfs-select-super, btrfsck (link to btrfs), btrfstune, fsck.btrfs, and mkfs.btrfs

Installed Libraries: libbtrfs.so and libbtrfsutil.so

Installed Directories: /usr/include/btrfs

Short Descriptions

btrfs	is the main interface into btrfs filesystem operations
btrfs-convert	converts from an ext2/3/4 or reiserfs filesystem to btrfs
btrfs-find-root	is a filter to find btrfs root
btrfs-map-logical	maps btrfs logical extent to physical extent
btrfs-select-super	overwrites the primary superblock with a backup copy
btrfstune	tunes various filesystem parameters
fsck.btrfs	does nothing, but is present for consistency with fstab
mkfs.btrfs	creates a btrfs file system

dosfstools-4.2

Introduction to dosfstools

The dosfstools package contains various utilities for use with the FAT family of file systems.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/dosfstools/dosfstools/releases/download/v4.2/dosfstools-4.2.tar.gz
Download MD5 sum: 49c8e457327dc61efab5b115a27b087a
Download size: 314 KB
Estimated disk space required: 4.5 MB (with tests)
Estimated build time: less than 0.1 SBU

Kernel Configuration

Enable the following option in the kernel configuration and recompile the kernel if you need to mount a FAT-family filesystem:

File systems --->
  DOS/FAT/EXFAT/NT Filesystems --->
    < /*/M> MSDOS fs support                                          [MSDOS_FS]
    <*/M>   VFAT (Windows-95) fs support                               [VFAT_FS]

Note that CONFIG_MSDOS_FS deliberately unsupport long file names. CONFIG_VFAT_FS should be used instead unless you really want to enforce the DOS-style “8.3” file names.

You can mount a FAT-family filesystem once the kernel supports it. If you don't need to create, check, or relabel a FAT-family system, you may skip this package.

Installation of dosfstools

Install dosfstools by running the following commands:

./configure --prefix=/usr            \
            --enable-compat-symlinks \
            --mandir=/usr/share/man  \
            --docdir=/usr/share/doc/dosfstools-4.2 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-compat-symlinks: This switch creates the dosfsck, dosfslabel, fsck.msdos, fsck.vfat, mkdosfs, mkfs.msdos, and mkfs.vfat symlinks required by some programs.

Installed Programs: fatlabel, fsck.fat, and mkfs.fat

Short Descriptions

fatlabel	sets or gets a MS-DOS filesystem label from a given device
fsck.fat	checks and repairs MS-DOS filesystems
mkfs.fat	creates an MS-DOS filesystem under Linux

Fuse-3.16.2

Introduction to Fuse

FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. Fuse also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libfuse/libfuse/releases/download/fuse-3.16.2/fuse-3.16.2.tar.gz
Download MD5 sum: b00bf08b27ead4a9411578777e94a1cc
Download size: 14 MB
Estimated disk space required: 222 MB (with tests and documentation)
Estimated build time: 0.2 SBU (add 0.3 SBU for tests)

Fuse Dependencies

Optional

Doxygen-1.10.0 (to rebuild the API documentation), pytest-8.0.0 (required for tests), and looseversion (for tests)

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel if necessary:

File systems --->
  <*/M> FUSE (Filesystem in Userspace) support                         [FUSE_FS]

Character devices in userspace should be enabled too for running the tests:

File systems --->
  <*/M> FUSE (Filesystem in Userspace) support                         [FUSE_FS]
  <*/M>   Character device in Userspace support                           [CUSE]

Installation of Fuse

Install Fuse by running the following commands:

sed -i '/^udev/,$ s/^/#/' util/meson.build &&

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

The API documentation is included in the package, but if you have Doxygen-1.10.0 installed and wish to rebuild it, issue:

pushd .. &&
  doxygen doc/Doxyfile &&
popd

To test the results, issue the following commands (as the root user):

python3 -m venv --system-site-packages testenv &&
source testenv/bin/activate                    &&
pip3 install looseversion                      &&
python3 -m pytest
deactivate

The pytest-8.0.0 Python module is required for the tests. One test named test_cuse will fail if the CONFIG_CUSE configuration item was not enabled when the kernel was built. One test, test/util.py, will output a warning due to the usage of an unknown mark in pytest. One test named test_notify_inval_entry[True-expire_entries] may fail under certain circumstances.

Now, as the root user:

ninja install                  &&
chmod u+s /usr/bin/fusermount3 &&

cd ..                          &&
cp -Rv doc/html -T /usr/share/doc/fuse-3.16.2 &&
install -v -m644   doc/{README.NFS,kernel.txt} \
                   /usr/share/doc/fuse-3.16.2

Command Explanations

sed ... util/meson.build: This command disables the installation of a boot script and udev rule that are not needed.

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Configuring fuse

Config Files

Some options regarding mount policy can be set in the file /etc/fuse.conf. To install the file run the following command as the root user:

cat > /etc/fuse.conf << "EOF"
# Set the maximum number of FUSE mounts allowed to non-root users.
# The default is 1000.
#
#mount_max = 1000

# Allow non-root users to specify the 'allow_other' or 'allow_root'
# mount options.
#
#user_allow_other
EOF

Additional information about the meaning of the configuration options are found in the man page.

Installed Programs: fusermount3 and mount.fuse3

Installed Libraries: libfuse3.so

Installed Directory: /usr/include/fuse3 and /usr/share/doc/fuse-3.16.2

Short Descriptions

fusermount3	is a suid root program to mount and unmount Fuse filesystems
mount.fuse3	is the command mount calls to mount a Fuse filesystem
`libfuse3.so`	contains the FUSE API functions

jfsutils-1.1.15

Introduction to jfsutils

The jfsutils package contains administration and debugging tools for the jfs file system.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://jfs.sourceforge.net/project/pub/jfsutils-1.1.15.tar.gz
Download MD5 sum: 8809465cd48a202895bc2a12e1923b5d
Download size: 532 KB
Estimated disk space required: 8.9 MB
Estimated build time: 0.1 SBU

Additional Downloads

Required patch to fix issues exposed by GCC 10 and later: https://www.linuxfromscratch.org/patches/blfs/12.1/jfsutils-1.1.15-gcc10_fix-1.patch

Kernel Configuration

Enable the following option in the kernel configuration and recompile the kernel:

File systems --->
  <*/M> JFS filesystem support                                          [JFS_FS]

Installation of jfsutils

First, fix some issues exposed by GCC 10 and later:

patch -Np1 -i ../jfsutils-1.1.15-gcc10_fix-1.patch

Install jfsutils by running the following commands:

sed -i "/unistd.h/a#include <sys/types.h>"    fscklog/extract.c &&
sed -i "/ioctl.h/a#include <sys/sysmacros.h>" libfs/devices.c   &&

./configure &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

sed ...: Fixes building with glibc 2.28.

Installed Programs: fsck.jfs, jfs_debugfs, jfs_fsck, jfs_fscklog, jfs_logdump, jfs_mkfs, jfs_tune, mkfs.jfs

Installed Libraries: None

Installed Directories: None

Short Descriptions

fsck.jfs	is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found
jfs_fsck	is a hard link to fsck.jfs
mkfs.jfs	constructs an JFS file system
jfs_mkfs	is a hard link to mkfs.jfs
jfs_debugfs	is a program which can be used to perform various low-level actions on a JFS formatted device
jfs_fscklog	extracts a JFS fsck service log into a file and/or formats and displays the extracted file
jfs_logdump	dumps the contents of the journal log from the specified JFS formatted device into output file ./jfslog.dmp
jfs_tune	adjusts tunable file system parameters on JFS file systems

LVM2-2.03.23

Introduction to LVM2

The LVM2 package is a set of tools that manage logical partitions. It allows spanning of file systems across multiple physical disks and disk partitions and provides for dynamic growing or shrinking of logical partitions, mirroring and low storage footprint snapshots.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://sourceware.org/ftp/lvm2/LVM2.2.03.23.tgz
Download MD5 sum: 0535b5e638b6f0b48f7b259e0ec0ba65
Download size: 2.7 MB
Estimated disk space required: 39 MB (add 20 MB for tests; transient files can grow up to around 300 MB in the /tmp directory during tests)
Estimated build time: 0.1 SBU (using parallelism=4; add 9 to 48 SBU for tests, depending on disk speed and whether ram block device is enabled in the kernel)

LVM2 Dependencies

Required

libaio-0.3.113

Optional

mdadm-4.2, Valgrind-3.22.0, Which-2.21, xfsprogs-6.6.0 (all four may be used, but are not required, for tests), reiserfsprogs, thin-provisioning-tools, and vdo

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel:

Note

There are several other Device Mapper options in the kernel beyond those listed below. In order to get reasonable results if running the regression tests, all must be enabled either internally or as a module. The tests will all time out if Magic SysRq key is not enabled.

Device Drivers --->
  [*] Block devices --->                                               [BLK_DEV]
    <*/M> RAM block device support                                 [BLK_DEV_RAM]
  [*] Multiple devices driver support (RAID and LVM) --->                   [MD]
    <*/M> Device mapper support                                     [BLK_DEV_DM]
    <*/M>   Crypt target support                                      [DM_CRYPT]
    <*/M>   Snapshot target                                        [DM_SNAPSHOT]
    <*/M>   Thin provisioning target                      [DM_THIN_PROVISIONING]
    <*/M>   Cache target (EXPERIMENTAL)                               [DM_CACHE]
    <*/M>   Mirror target                                            [DM_MIRROR]
    <*/M>   Zero target                                                [DM_ZERO]
    <*/M>   I/O delaying target                                       [DM_DELAY]

Kernel hacking --->
  Generic Kernel Debugging Instruments --->
    [*] Magic SysRq key                                            [MAGIC_SYSRQ]

Installation of LVM2

Install LVM2 by running the following commands:

PATH+=:/usr/sbin                \
./configure --prefix=/usr       \
            --enable-cmdlib     \
            --enable-pkgconfig  \
            --enable-udev_sync  &&
make

The tests use udev for logical volume synchronization, so the LVM udev rules and some utilities need to be installed before running the tests. If you are installing LVM2 for the first time, and do not want to install the full package before running the tests, the minimal set of utilities can be installed by running the following instructions as the root user:

make -C tools install_tools_dynamic &&
make -C udev  install               &&
make -C libdm install

To test the results, issue, as the root user:

LC_ALL=en_US.UTF-8 make check_local

Some tests may hang. In this case they can be skipped by adding S=<testname> to the make command. Other targets are available and can be listed with make -C test help. The test timings are very dependent on the speed of the disk(s), and on the number of enabled kernel options.

The tests do not implement the “expected fail” possibility, and a small number of test failures is expected by upstream. More failures may happen because some kernel options are missing. For example, the lack of the dm-delay device mapper target explains some failures. Some tests may fail if there is insufficient free space available in the partition with the /tmp directory. At least one test fails if 16 TB is not available. Some tests are flagged “warned” if thin-provisioning-tools are not installed. A workaround is to add the following flags to configure:

     --with-thin-check=    \
     --with-thin-dump=     \
     --with-thin-repair=   \
     --with-thin-restore=  \
     --with-cache-check=   \
     --with-cache-dump=    \
     --with-cache-repair=  \
     --with-cache-restore= \

Some tests may hang. They can be removed if necessary, for example: rm test/shell/lvconvert-raid-reshape.sh. The tests generate a lot of kernel messages, which may clutter your terminal. You can disable them by issuing dmesg -D before running the tests (do not forget to issue dmesg -E when tests are done).

Note

The checks create device nodes in the /tmp directory. The tests will fail if /tmp is mounted with the nodev option.

Now, as the root user:

make install
rm -fv /usr/lib/udev/rules.d/69-dm-lvm.rules

Command Explanations

PATH+=:/usr/sbin: The path must contain /usr/sbin for proper system tool detection by the configure script. This instruction ensures that PATH is properly set even if you build as an unprivileged user.

--enable-cmdlib: This switch enables building of the shared command library. It is required when building the event daemon.

--enable-pkgconfig: This switch enables installation of pkg-config support files.

--enable-udev_sync: This switch enables synchronisation with Udev processing.

--enable-dmeventd: This switch enables building of the Device Mapper event daemon.

rm .../69-dm-lvm.rules: Under certain circumstances, this udev rule calls systemd-run, which is not available on sysv. It performs actions that are done by another boot script anyway, so it is not needed.

Installed Programs: blkdeactivate, dmeventd (optional), dmsetup, fsadm, lvm, lvmdump, and lvm_import_vdo. There are also numerous symbolic links to lvm that implement specific functionalities

Installed Libraries: libdevmapper.so and liblvm2cmd.so; optional: libdevmapper-event.so, libdevmapper-event-lvm2.so, libdevmapper-event-lvm2mirror.so, libdevmapper-event-lvm2raid.so, libdevmapper-event-lvm2snapshot.so, libdevmapper-event-lvm2thin.so, and libdevmapper-event-lvm2vdo.so

Installed Directories: /etc/lvm and /usr/lib/device-mapper (optional)

Short Descriptions

blkdeactivate	is a utility to deactivate block devices
dmeventd	(optional) is the Device Mapper event daemon
dmsetup	is a low level logical volume management tool
fsadm	is a utility used to resize or check filesystem on a device
lvm	provides the command-line tools for LVM2. Commands are implemented via symbolic links to this program to manage physical devices (pv), volume groups (vg) and logical volumes (lv*)
lvmdump	is a tool used to dump various information concerning LVM2
vgimportclone	is used to import a duplicated VG (e.g. hardware snapshot)
`libdevmapper.so`	contains the Device Mapper API functions

About Logical Volume Management (LVM)

LVM manages disk drives. It allows multiple drives and partitions to be combined into larger volume groups, assists in making backups through a snapshot, and allows for dynamic volume resizing. It can also provide mirroring similar to a RAID 1 array.

A complete discussion of LVM is beyond the scope of this introduction, but basic concepts are presented below.

To run any of the commands presented here, the LVM2-2.03.23 package must be installed. All commands must be run as the root user.

Management of disks with lvm is accomplished using the following concepts:

physical volumes: These are physical disks or partitions such as /dev/sda3 or /dev/sdb.
volume groups: These are named groups of physical volumes that can be manipulated by the administrator. The number of physical volumes that make up a volume group is arbitrary. Physical volumes can be dynamically added or removed from a volume group.
logical volumes: Volume groups may be subdivided into logical volumes. Each logical volume can then be individually formatted as if it were a regular Linux partition. Logical volumes may be dynamically resized by the administrator according to need.

To give a concrete example, suppose that you have two 2 TB disks. Also suppose a really large amount of space is required for a very large database, mounted on /srv/mysql. This is what the initial set of partitions would look like:

Partition  Use    Size      Partition Type
/dev/sda1  /boot  100MB     83 (Linux)
/dev/sda2  /       10GB     83 (Linux)
/dev/sda3  swap     2GB     82 (Swap)
/dev/sda4  LVM    remainder 8e (LVM)
/dev/sdb1  swap     2GB     82 (Swap)
/dev/sdb2  LVM    remainder 8e (LVM)

First initialize the physical volumes:

pvcreate /dev/sda4 /dev/sdb2

Note

A full disk can be used as part of a physical volume, but beware that the pvcreate command will destroy any partition information on that disk.

Next create a volume group named lfs-lvm:

vgcreate lfs-lvm /dev/sda4  /dev/sdb2

The status of the volume group can be checked by running the command vgscan. Now create the logical volumes. Since there is about 3900 GB available, leave about 900 GB free for expansion. Note that the logical volume named mysql is larger than any physical disk.

lvcreate --name mysql --size 2500G lfs-lvm
lvcreate --name home  --size  500G lfs-lvm

Finally the logical volumes can be formatted and mounted. In this example, the jfs file system (jfsutils-1.1.15) is used for demonstration purposes.

mkfs -t ext4 /dev/lfs-lvm/home
mkfs -t jfs  /dev/lfs-lvm/mysql
mount /dev/lfs-lvm/home /home
mkdir -p /srv/mysql
mount /dev/lfs-lvm/mysql /srv/mysql

It may be needed to activate those logical volumes, for them to appear in /dev. They can all be activated at the same time by issuing, as the root user:

vgchange -a y

The LFS boot scripts automatically make these logical volumes available to the system in the udev script. Edit the /etc/fstab file as required to automatically mount them.

A LVM logical volume can host a root filesystem, but requires the use of an initramfs (initial RAM file system). The initramfs proposed in the section called “About initramfs” allows to pass the lvm volume in the root= switch of the kernel command line.

For more information about LVM, see the LVM HOWTO and the lvm man pages. A good in-depth guide is available from RedHat^®, although it makes sometimes reference to proprietary tools.

About RAID

The storage technology known as RAID (Redundant Array of Independent Disks) combines multiple physical disks into a logical unit. The drives can generally be combined to provide data redundancy or to extend the size of logical units beyond the capability of the physical disks or both. The technology also allows for providing hardware maintenance without powering down the system.

The types of RAID organization are described in the RAID Wiki.

Note that while RAID provides protection against disk failures, it is not a substitute for backups. A file deleted is still deleted on all the disks of a RAID array. Modern backups are generally done via rsync-3.2.7.

There are three major types of RAID implementation: Hardware RAID, BIOS-based RAID, and Software RAID.

Hardware RAID

Hardware based RAID provides capability through proprietary hardware and data layouts. The control and configuration is generally done via firmware in conjunction with executable programs made available by the device manufacturer. The capabilities are generally supplied via a PCI card, although there are some instances of RAID components integrated in to the motherboard. Hardware RAID may also be available in a stand-alone enclosure.

One advantage of hardware-based RAID is that the drives are offered to the operating system as a logical drive and no operating system dependent configuration is needed.

Disadvantages include difficulties in transferring drives from one system to another, updating firmware, or replacing failed RAID hardware.

BIOS-based RAID

Some computers offer a hardware-like RAID implementation in the system BIOS. Sometime this is referred to as 'fake' RAID as the capabilities are generally incorporated into firmware without any hardware acceleration.

The advantages and disadvantages of BIOS-based RAID are generally the same as hardware RAID with the additional disadvantage that there is no hardware acceleration.

In some cases, BIOS-based RAID firmware is enabled by default (e.g. some DELL systems). If software RAID is desired, this option must be explicitly disabled in the BIOS.

Software RAID

Software based RAID is the most flexible form of RAID. It is easy to install and update and provides full capability on all or part of any drives available to the system. In BLFS, the RAID software is found in mdadm-4.2.

Configuring a RAID device is straightforward using mdadm. Generally devices are created in the /dev directory as /dev/mdx where x is an integer.

The first step in creating a RAID array is to use partitioning software such as fdisk or parted-3.6 to define the partitions needed for the array. Usually, there will be one partition on each drive participating in the RAID array, but that is not strictly necessary. For this example, there will be four disk drives: /dev/sda, /dev/sdb, /dev/sdc, and /dev/sdd. They will be partitioned as follows:

Partition Size     Type                Use
sda1:     100 MB   fd Linux raid auto  /boot    (RAID 1) /dev/md0
sda2:      10 GB   fd Linux raid auto  /        (RAID 1) /dev/md1
sda3:       2 GB   83 Linux swap       swap
sda4      300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2

sdb1:     100 MB   fd Linux raid auto  /boot    (RAID 1) /dev/md0
sdb2:      10 GB   fd Linux raid auto  /        (RAID 1) /dev/md1
sdb3:       2 GB   83 Linux swap       swap
sdb4      300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2

sdc1:      12 GB   fd Linux raid auto  /usr/src (RAID 0) /dev/md3
sdc2:     300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2

sdd1:      12 GB   fd Linux raid auto  /usr/src (RAID 0) /dev/md3
sdd2:     300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2

In this arrangement, a separate boot partition is created as the first small RAID array and a root filesystem as the secong RAID array, both mirrored. The third partition is a large (about 1TB) array for the /home directory. This provides an ability to stripe data across multiple devices, improving speed for both reading and writing large files. Finally, a fourth array is created that concatenates two partitions into a larger device.

Note

All mdadm commands must be run as the root user.

To create these RAID arrays the commands are:

/sbin/mdadm -Cv /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
/sbin/mdadm -Cv /dev/md1 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
/sbin/mdadm -Cv /dev/md3 --level=0 --raid-devices=2 /dev/sdc1 /dev/sdd1
/sbin/mdadm -Cv /dev/md2 --level=5 --raid-devices=4 \
        /dev/sda4 /dev/sdb4 /dev/sdc2 /dev/sdd2

The devices created can be examined by device. For example, to see the details of /dev/md1, use /sbin/mdadm --detail /dev/md1:

        Version : 1.2
  Creation Time : Tue Feb  7 17:08:45 2012
     Raid Level : raid1
     Array Size : 10484664 (10.00 GiB 10.74 GB)
  Used Dev Size : 10484664 (10.00 GiB 10.74 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Tue Feb  7 23:11:53 2012
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : core2-blfs:0  (local to host core2-blfs)
           UUID : fcb944a4:9054aeb2:d987d8fe:a89121f8
         Events : 17

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1

From this point, the partitions can be formatted with the filesystem of choice (e.g. ext3, ext4, xfsprogs-6.6.0, etc). The formatted partitions can then be mounted. The /etc/fstab file can use the devices created for mounting at boot time and the linux command line in /boot/grub/grub.cfg can specify root=/dev/md1.

Note

The swap devices should be specified in the /etc/fstab file as normal. The kernel normally stripes swap data across multiple swap files and should not be made part of a RAID array.

For further options and management details of RAID devices, refer to man mdadm.

Additional details for monitoring RAID arrays and dealing with problems can be found at the Linux RAID Wiki.

mdadm-4.2

Introduction to mdadm

The mdadm package contains administration tools for software RAID.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-4.2.tar.xz
Download MD5 sum: a304eb0a978ca81045620d06547050a6
Download size: 444 KB
Estimated disk space required: 5.0 MB
Estimated build time: 0.1 SBU

mdadm Dependencies

Optional

A MTA

Caution

Kernel versions in series 4.1 through 4.4.1 have a broken RAID implementation. Use a kernel with version at or above 4.4.2.

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel, if necessary. Only the RAID types desired are required.

Device Drivers --->
  [*] Multiple devices driver support (RAID and LVM) --->                   [MD]
    <*/M>   RAID support                                            [BLK_DEV_MD]
    [*]       Autodetect RAID arrays during kernel boot          [MD_AUTODETECT]
    # Only the RAID types desired are required:
    < /*/M> RAID-0 (striping) mode                                    [MD_RAID0]
    < /*/M> RAID-1 (mirroring) mode                                   [MD_RAID1]
    < /*/M> RAID-10 (mirrored striping) mode                         [MD_RAID10]
    < /*/M> RAID-4/RAID-5/RAID-6 mode                               [MD_RAID456]

Installation of mdadm

Build mdadm by running the following command:

make

This package does not come with a working test suite.

Now, as the root user:

make BINDIR=/usr/sbin install

Command Explanations

make everything: This optional target creates extra programs, particularly a statically-linked version of mdadm. This needs to be manually installed.

Installed Programs: mdadm and mdmon

Installed Libraries: None

Installed Directory: None

Short Descriptions

mdadm	manages MD devices aka Linux Software RAID
mdmon	monitors MD external metadata arrays

ntfs-3g-2022.10.3

Introduction to Ntfs-3g

Note

A new read-write driver for NTFS, called NTFS3, has been added into the Linux kernel since the 5.15 release. The performance of NTFS3 is much better than ntfs-3g. To enable NTFS3, enable the following options in the kernel configuration and recompile the kernel if necessary:

File systems --->
  DOS/FAT/EXFAT/NT Filesystems --->
    <*/M> NTFS Read-Write file system support                         [NTFS3_FS]

To ensure the mount command uses NTFS3 for ntfs partitions, create a wrapper script:

cat > /usr/sbin/mount.ntfs << "EOF" &&
#!/bin/sh
exec mount -t ntfs3 "$@"
EOF
chmod -v 755 /usr/sbin/mount.ntfs

With the kernel support available, ntfs-3g is only needed if you need the utilities from it (for example, to create NTFS filesystems).

The Ntfs-3g package contains a stable, read-write open source driver for NTFS partitions. NTFS partitions are used by most Microsoft operating systems. Ntfs-3g allows you to mount NTFS partitions in read-write mode from your Linux system. It uses the FUSE kernel module to be able to implement NTFS support in userspace. The package also contains various utilities useful for manipulating NTFS partitions.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://tuxera.com/opensource/ntfs-3g_ntfsprogs-2022.10.3.tgz
Download MD5 sum: a038af61be7584b79f8922ff11244090
Download size: 1.3 MB
Estimated disk space required: 22 MB
Estimated build time: 0.2 SBU

Ntfs-3g Dependencies

Optional

fuse 2.x (this disables user mounts)

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel if necessary:

File systems --->
  <*/M> FUSE (Filesystem in Userspace) support                         [FUSE_FS]

Note that it is only needed for mounting NTFS partitions with ntfs-3g. If you will use the in-kernel NTFS3 driver for mounting NTFS partitions (as the BLFS editors recommend) instead, you can skip this configuration item.

Installation of Ntfs-3g

Install Ntfs-3g by running the following commands:

./configure --prefix=/usr        \
            --disable-static     \
            --with-fuse=internal \
            --docdir=/usr/share/doc/ntfs-3g-2022.10.3 &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&

It's recommended to use the in-kernel NTFS3 driver for mounting NTFS filesystems, instead of ntfs-3g (see the note at the start of this page). However, if you want to use ntfs-3g to mount the NTFS filesystems anyway, create a symlink for the mount command:

ln -sv ../bin/ntfs-3g /usr/sbin/mount.ntfs &&
ln -sv ntfs-3g.8 /usr/share/man/man8/mount.ntfs.8

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--with-fuse=internal: This switch dynamically forces ntfs-3g to use an internal copy of the fuse-2.x library. This is required if you wish to allow users to mount NTFS partitions.

--disable-ntfsprogs: Disables installation of various utilities used to manipulate NTFS partitions.

chmod -v 4755 /usr/bin/ntfs-3g: Making mount.ntfs setuid root allows non root users to mount NTFS partitions.

Using Ntfs-3g

To mount a Windows partition at boot time, put a line like this in /etc/fstab:

/dev/sda1 /mnt/windows auto defaults 0 0

To allow users to mount a usb stick with an NTFS filesystem on it, put a line similar to this (change sdc1 to whatever a usb stick would be on your system) in /etc/fstab:

/dev/sdc1 /mnt/usb auto user,noauto,umask=0,utf8 0 0

In order for a user to be able to mount the usb stick, they will need to be able to write to /mnt/usb, so as the root user:

chmod -v 777 /mnt/usb

Installed Programs: lowntfs-3g, mkfs.ntfs, mkntfs, mount.lowntfs-3g, mount.ntfs, mount.ntfs-3g, ntfs-3g, ntfs-3g.probe, ntfscat, ntfsclone, ntfscluster, ntfscmp, ntfscp, ntfsfix, ntfsinfo, ntfslabel, ntfsls, ntfsresize and ntfsundelete

Installed Library: libntfs-3g.so

Installed Directories: /usr/include/ntfs-3g and /usr/share/doc/ntfs-3g

Short Descriptions

lowntfs-3g	is similar to ntfs-3g but uses the Fuse low-level interface
mkfs.ntfs	is a symlink to mkntfs
mkntfs	creates an NTFS file system
mount.lowntfs-3g	is a symlink to lowntfs-3g
mount.ntfs	mounts an NTFS filesystem
mount.ntfs-3g	is a symbolic link to ntfs-3g
ntfs-3g	is an NTFS driver, which can create, remove, rename, move files, directories, hard links, and streams. It can also read and write files, including streams, sparse files and transparently compressed files. It can also handle special files like symbolic links, devices, and FIFOs; moreover it provides standard management of file ownership and permissions, including POSIX ACLs
ntfs-3g.probe	tests if an NTFS volume is mountable read only or read-write, and exits with a status value accordingly. The volume can be a block device or image file
ntfscluster	identifies files in a specified region of an NTFS volume
ntfscp	copies a file to an NTFS volume
ntfsfix	fixes common errors and forces Windows to check an NTFS partition
ntfsls	lists directory contents on an NTFS filesystem
ntfscat	prints NTFS files and streams on the standard output
ntfsclone	clones an NTFS filesystem
ntfscmp	compares two NTFS filesystems and shows the differences
ntfsinfo	dumps a file's attributes
ntfslabel	displays or changes the label on an ntfs file system
ntfsresize	resizes an NTFS filesystem without data loss
ntfsundelete	recovers a deleted file from an NTFS volume
`libntfs-3g.so`	contains the Ntfs-3g API functions

gptfdisk-1.0.10

Introduction to gptfdisk

The gptfdisk package is a set of programs for creation and maintenance of GUID Partition Table (GPT) disk drives. A GPT partitioned disk is required for drives greater than 2 TB and is a modern replacement for legacy PC-BIOS partitioned disk drives that use a Master Boot Record (MBR). The main program, gdisk, has an interface similar to the classic fdisk program.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/gptfdisk/gptfdisk-1.0.10.tar.gz
Download MD5 sum: 1970269eb7a97560e238611524b7797a
Download size: 216 KB
Estimated disk space required: 2.4 MB
Estimated build time: less than 0.1 SBU (add 0.2 SBU for tests)

Additional Downloads

Recommended patch: https://www.linuxfromscratch.org/patches/blfs/12.1/gptfdisk-1.0.10-convenience-1.patch

gptfdisk Dependencies

Required

popt-1.19

Optional

ICU-74.2

Installation of gptfdisk

The gptfdisk package comes with a rudimentary Makefile. First we update it to provide a simple build and install interface and fix the location of a header file and fix some minor location issues. Install gptfdisk by running the following commands:

patch -Np1 -i ../gptfdisk-1.0.10-convenience-1.patch &&
sed -i 's|ncursesw/||' gptcurses.cc &&
sed -i 's|sbin|usr/sbin|' Makefile  &&

make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

patch -Np1 ...: This patch modifies the Makefile file so that it provides an “install” target.

Installed Programs: cgdisk, gdisk, fixparts, and sgdisk

Short Descriptions

cgdisk	is an ncurses-based tool for manipulating GPT partitions
gdisk	is an interactive text-mode tool for manipulating GPT partitions
fixparts	repairs mis-formatted MBR based disk partitions
sgdisk	is a partition manipulation program for GPT partitions similar to sfdisk

parted-3.6

Introduction to parted

The Parted package is a disk partitioning and partition resizing tool.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/parted/parted-3.6.tar.xz
Download MD5 sum: 93d2d8f22baebc5eb65b85da05a79e4e
Download size: 1.8 MB
Estimated disk space required: 29 MB (additional 3 MB for the tests and additional 2 MB for optional PDF and Postscript documentation)
Estimated build time: 0.3 SBU (additional 3.6 SBU for the tests)

Parted Dependencies

Optional

dosfstools-4.2, texlive-20230313 (or install-tl-unx), and Digest::CRC (for tests)

Optional Kernel Configuration for Tests

About 20 % more tests are run if the following kernel module is built:

Device Drivers --->
  SCSI device support --->
    [*] SCSI low-level drivers --->                              [SCSI_LOWLEVEL]
      <M> SCSI debugging host and device simulator                  [SCSI_DEBUG]

Installation of parted

Install Parted by running the following commands:

./configure --prefix=/usr --disable-static &&
make &&

make -C doc html                                       &&
makeinfo --html      -o doc/html       doc/parted.texi &&
makeinfo --plaintext -o doc/parted.txt doc/parted.texi

If you have texlive-20230313 installed and wish to create PDF and Postscript documentation issue the following commands:

cp build-aux/texinfo.tex doc               &&
texi2pdf -o doc/parted.pdf doc/parted.texi &&
texi2dvi -o doc/parted.dvi doc/parted.texi &&
dvips    -o doc/parted.ps  doc/parted.dvi

To test the results, issue, as the root user:

make check

Note

Many tests are skipped if not run as the root user.

Now, as the root user:

make install &&
install -v -m755 -d /usr/share/doc/parted-3.6/html &&
install -v -m644    doc/html/* \
                    /usr/share/doc/parted-3.6/html &&
install -v -m644    doc/{FAT,API,parted.{txt,html}} \
                    /usr/share/doc/parted-3.6

Install the optional PDF and Postscript documentation by issuing the following command as the root user:

install -v -m644 doc/FAT doc/API doc/parted.{pdf,ps,dvi} \
                    /usr/share/doc/parted-3.6

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--disable-device-mapper: This option disables device mapper support. Add this parameter if you have not installed LVM2.

Installed Programs: parted and partprobe

Installed Libraries: libparted.so and libparted-fs-resize.so

Installed Directories: /usr/include/parted and /usr/share/doc/parted-3.6

Short Descriptions

parted	is a partition manipulation program
partprobe	informs the OS of partition table changes
`libparted.so`	contains the Parted API functions

smartmontools-7.4

Introduction to smartmontools

The smartmontools package contains utility programs (smartctl, smartd) to control/monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (S.M.A.R.T.) built into most modern ATA and SCSI disks.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/smartmontools/smartmontools-7.4.tar.gz
Download MD5 sum: 178d31a6ff5256c093227ab45a3f52aa
Download size: 1 MB
Estimated disk space required: 27 MB
Estimated build time: 0.2 SBU

smartmontools Dependencies

Optional (runtime)

cURL-8.6.0 or Lynx-2.8.9rel.1 or Wget-1.21.4 (download tools), and GnuPG-2.4.4 (encrypted hard disks)

Installation of smartmontools

Install smartmontools by running the following commands:

./configure --prefix=/usr           \
            --sysconfdir=/etc       \
            --with-initscriptdir=no \
            --with-libsystemd=no    \
            --docdir=/usr/share/doc/smartmontools-7.4 &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--with-initscriptdir=no: This switch suppresses the default initialization script. See below for the BLFS script.

--with-libsystemd=no: This switch disables support for the sd-notify notification system provided by systemd.

Configuring smartmontools

Config File

/etc/smartd.conf

Configuration Information

See the embedded comments in /etc/smartd.conf for detailed instructions on customizing the smartd daemon.

Boot Script

If you want the smartd daemon to start automatically when the system is booted, install the /etc/rc.d/init.d/smartd init script included in the blfs-bootscripts-20240209 package.

make install-smartd

Installed Programs: smartctl, smartd, and update-smart-drivedb

Installed Libraries: None

Installed Directories: /usr/share/smartmontools, /usr/share/doc/smartmontools-7.4, and /etc/smartd_warning.d

Short Descriptions

smartctl	is the control and monitor utility for SMART Disks
smartd	is the SMART disk monitoring daemon
update-smart-drivedb	is the update tool for the smartmontools drive database

sshfs-3.7.3

Introduction to Sshfs

The Sshfs package contains a filesystem client based on the SSH File Transfer Protocol. This is useful for mounting a remote computer that you have ssh access to as a local filesystem. This allows you to drag and drop files or run shell commands on the remote files as if they were on your local computer.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libfuse/sshfs/releases/download/sshfs-3.7.3/sshfs-3.7.3.tar.xz
Download MD5 sum: f704f0d1800bdb5214030a1603e8c6d6
Download size: 56 KB
Estimated disk space required: 0.9 MB
Estimated build time: less than 0.1 SBU

Sshfs Dependencies

Required

Fuse-3.16.2, GLib-2.78.4, and OpenSSH-9.6p1.

Optional

docutils-0.20.1 (required to build the man page)

Installation of Sshfs

Install Sshfs by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Using Sshfs

To mount an ssh server you need to be able to log into the server. For example, to mount your remote home folder to the local ~/examplepath (the directory must exist and you must have permissions to write to it):

sshfs example.com:/home/userid ~/examplepath

When you've finished work and want to unmount it again:

fusermount3 -u ~/example

You can also mount an sshfs filesystem at boot by adding an entry similar to the following in the /etc/fstab file:

userid@example.com:/path /media/path fuse.sshfs _netdev,IdentityFile=/home/userid/.ssh/id_rsa 0 0

See man 1 sshfs and man 8 mount.fuse3 for all available mount options.

Installed Program: sshfs

Installed Libraries: None

Installed Directories: None

Short Descriptions

sshfs

mounts an ssh server as a local file system

xfsprogs-6.6.0

Introduction to xfsprogs

The xfsprogs package contains administration and debugging tools for the XFS file system.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-6.6.0.tar.xz
Download MD5 sum: c008a752fae65aaf761096eb4698df86
Download size: 1.3 MB
Estimated disk space required: 56 MB
Estimated build time: 0.3 SBU (Using parallelism=4)

xfsprogs Dependencies

Required

inih-58 and liburcu-0.14.0

Optional

ICU-74.2 (for unicode name scanning in xfs_scrub)

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel:

File systems --->
  <*/M> XFS filesystem support                                          [XFS_FS]

Installation of xfsprogs

Install xfsprogs by running the following commands:

make DEBUG=-DNDEBUG     \
     INSTALL_USER=root  \
     INSTALL_GROUP=root

This package does not come with a test suite.

Now, as the root user:

make PKG_DOC_DIR=/usr/share/doc/xfsprogs-6.6.0 install     &&
make PKG_DOC_DIR=/usr/share/doc/xfsprogs-6.6.0 install-dev &&

rm -rfv /usr/lib/libhandle.{a,la}

Command Explanations

DEBUG=-DNDEBUG: Turns off debugging symbols.

INSTALL_USER=root INSTALL_GROUP=root: This sets the owner and group of the installed files.

OPTIMIZER="...": Adding this parameter to the end of the make command overrides the default optimization settings.

Installed Programs: fsck.xfs, mkfs.xfs, xfs_admin, xfs_bmap, xfs_copy, xfs_db, xfs_estimate, xfs_freeze, xfs_fsr, xfs_growfs, xfs_info, xfs_io, xfs_logprint, xfs_mdrestore, xfs_metadump, xfs_mkfile, xfs_ncheck, xfs_quota, xfs_repair, xfs_rtcp, xfs_scrub, xfs_scrub_all, and xfs_spaceman

Installed Libraries: libhandle.so

Installed Directories: /usr/include/xfs, /usr/lib/xfsprogs, /usr/share/xfsprogs, and /usr/share/doc/xfsprogs-6.6.0

Short Descriptions

fsck.xfs	simply exits with a zero status, since XFS partitions are checked at mount time
mkfs.xfs	constructs an XFS file system
xfs_admin	changes the parameters of an XFS file system
xfs_bmap	prints block mapping for an XFS file
xfs_copy	copies the contents of an XFS file system to one or more targets in parallel
xfs_estimate	for each directory argument, estimates the space that directory would take if it were copied to an XFS filesystem (does not cross mount points)
xfs_db	is used to debug an XFS file system
xfs_freeze	suspends access to an XFS file system
xfs_fsr	applicable only to XFS filesystems, improves the organization of mounted filesystems, the reorganization algorithm operates on one file at a time, compacting or otherwise improving the layout of the file extents (contiguous blocks of file data)
xfs_growfs	expands an XFS file system
xfs_info	is equivalent to invoking xfs_growfs, but specifying that no change to the file system is to be made
xfs_io	is a debugging tool like xfs_db, but is aimed at examining the regular file I/O path rather than the raw XFS volume itself
xfs_logprint	prints the log of an XFS file system
xfs_mdrestore	restores an XFS metadump image to a filesystem image
xfs_metadump	copies XFS filesystem metadata to a file
xfs_mkfile	creates an XFS file, padded with zeroes by default
xfs_ncheck	generates pathnames from inode numbers for an XFS file system
xfs_quota	is a utility for reporting and editing various aspects of filesystem quotas
xfs_repair	repairs corrupt or damaged XFS file systems
xfs_rtcp	copies a file to the real-time partition on an XFS file system
xfs_scrub	checks and repairs the contents of a mounted XFS file system
xfs_scrub_all	scrubs all mounted XFS file systems
xfs_spaceman	reports and controls free space usage in an XFS file system
`libhandle.so`	contains XFS-specific functions that provide a way to perform certain filesystem operations without using a file descriptor to access filesystem objects

Packages for UEFI Boot

efivar-39

Introduction to efivar

The efivar package provides tools and libraries to manipulate EFI variables.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/rhboot/efivar/archive/39/efivar-39.tar.gz
Download MD5 sum: a8fc3e79336cd6e738ab44f9bc96a5aa
Download size: 456 KB
Estimated disk space required: 21 MB
Estimated build time: less than 0.1 SBU

efivar Dependencies

Installation of efivar

Note

This package cannot function properly on a 32-bit system with a 64-bit UEFI implementation. Don't install this package (or efibootmgr) on 32-bit system unless you are absolutely sure you have a 32-bit UEFI implementation, which is very rare in practice.

Build efivar with the following commands:

make

The test suite of this package is dangerous. Running it may trigger firmware bugs and make your system unusable without using some special hardware to reprogram the firmware.

Now, as the root user:

make install LIBDIR=/usr/lib

Command Explanations

LIBDIR=/usr/lib: This option overrides the default library directory of the package (/usr/lib64, which is not used by LFS).

ENABLE_DOCS=0: Disable the generation of man pages. Append this option after the make and make install commands if you don't need the man pages to allow building this package without mandoc-1.14.6 installed.

Installed Programs: efisecdb and efivar

Installed Libraries: libefiboot.so, libefisec.so, and libefivar.so

Installed Directories: /usr/include/efivar

Short Descriptions

efisecdb	is an utility for managing UEFI signature lists
efivar	is a tool to manipulate UEFI variables
`libefiboot.so`	is a library used by efibootmgr
`libefisec.so`	is a library for managing UEFI signature lists
`libefivar.so`	is a library for the manipulation of EFI variables

efibootmgr-18

Introduction to efibootmgr

The efibootmgr package provides tools and libraries to manipulate EFI variables.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/rhboot/efibootmgr/archive/18/efibootmgr-18.tar.gz
Download MD5 sum: e170147da25e1d5f72721ffc46fe4e06
Download size: 48 KB
Estimated disk space required: 1.1 MB
Estimated build time: less than 0.1 SBU

efibootmgr Dependencies

Required

efivar-39 and popt-1.19

Installation of efibootmgr

Build efibootmgr with the following commands:

make EFIDIR=LFS EFI_LOADER=grubx64.efi

This package does not have a test suite.

Now, as the root user:

make install EFIDIR=LFS

Command Explanations

EFIDIR=LFS: This option specifies the distro's subdirectory name under /boot/efi/EFI. The building system of this package needs it to be set explicitly.

EFI_LOADER=grubx64.efi: This option specifies the name of the default EFI boot loader. It is set to match the EFI boot loader provided by GRUB .

Installed Programs: efibootdump and efibootmgr

Short Descriptions

efibootdump	is a tool to display individual UEFI boot options, from a file or an UEFI variable
efibootmgr	is a tool to manipulate the UEFI Boot Manager

GRUB-2.12 for EFI

Introduction to GRUB

The GRUB package provides GRand Unified Bootloader. In this page it will be built with UEFI support, which is not enabled for GRUB built in LFS.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/grub/grub-2.12.tar.xz
Download MD5 sum: 60c564b1bdc39d8e43b3aab4bc0fb140
Download size: 6.4 MB
Estimated disk space required: 183 MB
Estimated build time: 0.4 SBU (on 64-bit LFS, using parallelism=4)

Additional Downloads

Unicode font data used to display GRUB menu

Download (HTTP): https://unifoundry.com/pub/unifont/unifont-15.1.04/font-builds/unifont-15.1.04.pcf.gz
Download MD5 sum: 72f95e7ecb47a4c7ed610babe6959ead
Download size: 1.3 MB

GCC (only needed if building on 32-bit LFS)

Refer to GCC-13.2.0 page for download info.

GRUB Dependencies

Optional

LVM2-2.03.23

Installation of GRUB

First, install font data as the root user:

mkdir -pv /usr/share/fonts/unifont &&
gunzip -c ../unifont-15.1.04.pcf.gz > /usr/share/fonts/unifont/unifont.pcf

Warning

Unset any environment variables which may affect the build:

unset {C,CPP,CXX,LD}FLAGS

Don't try “tuning” this package with custom compilation flags: this package is a bootloader, with low-level operations in the source code which is likely to be broken by some aggressive optimizations.

Add a file missing from the release tarball:

echo depends bli part_gpt > grub-core/extra_deps.lst

If you are running a 32-bit LFS, prepare a 64-bit compiler:

case $(uname -m) in i?86 )
    tar xf ../gcc-13.2.0.tar.xz
    mkdir gcc-13.2.0/build
    pushd gcc-13.2.0/build
        ../configure --prefix=$PWD/../../x86_64-gcc \
                     --target=x86_64-linux-gnu      \
                     --with-system-zlib             \
                     --enable-languages=c,c++       \
                     --with-ld=/usr/bin/ld
        make all-gcc
        make install-gcc
    popd
    export TARGET_CC=$PWD/x86_64-gcc/bin/x86_64-linux-gnu-gcc
esac

Build GRUB with the following commands:

./configure --prefix=/usr        \
            --sysconfdir=/etc    \
            --disable-efiemu     \
            --enable-grub-mkfont \
            --with-platform=efi  \
            --target=x86_64      \
            --disable-werror     &&
unset TARGET_CC &&
make

This package does not have a test suite providing meaningful results.

Now, as the root user:

make install &&
mv -v /etc/bash_completion.d/grub /usr/share/bash-completion/completions

Command Explanations

--enable-grub-mkfont: Build the tool named grub-mkfont to generate the font file for the boot loader from the font data we've installed.

Warning

If the recommended dependency FreeType-2.13.2 is not installed, it is possible to omit this option and build GRUB. However, if grub-mkfont is not built, or the unicode font data is not available at the time GRUB is built, GRUB won't install any font for the boot loader. The GRUB boot menu will be displayed using a coarse font or in a smaller region on the screen.

--with-platform=efi: Ensures building GRUB with EFI enabled.

--target=x86_64: Ensures building GRUB for x86_64 even if building on a 32-bit LFS system. Most EFI firmware on x86_64 does not support 32-bit bootloaders.

--target=i386: A few 32-bit x86 platforms have EFI support. And, some x86_64 platforms have a 32-bit EFI implementation, but they are very old and rare. Use this instead of --target=x86_64 if you are absolutely sure that LFS is running on such a system.

Configuring GRUB

Using GRUB to make the LFS system bootable on UEFI platform will be discussed in Using GRUB to Set Up the Boot Process with UEFI.

See the page for GRUB in LFS book.

Using GRUB to Set Up the Boot Process with UEFI

Turn Off Secure Boot

BLFS does not have the essential packages to support Secure Boot. To set up the boot process with GRUB and UEFI in BLFS, Secure Boot must be turned off from the configuration interface of the firmware. Read the documentation provided by the manufacturer of your system to find out how.

Kernel Configuration for UEFI support

Enable the following options in the kernel configuration and recompile the kernel if necessary:

Processor type and features --->
  [*] EFI runtime service support                                          [EFI]
  [*]   EFI stub support                                              [EFI_STUB]

-*- Enable the block layer --->                                          [BLOCK]
  Partition Types --->
    [ /*] Advanced partition selection                      [PARTITION_ADVANCED]
    [*]     EFI GUID Partition support                           [EFI_PARTITION]

Device Drivers --->
  Firmware Drivers --->
    [*] Mark VGA/VBE/EFI FB as generic system framebuffer       [SYSFB_SIMPLEFB]
  Graphics support --->
    <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
                                                                      ...  [DRM]
    [*] Enable legacy fbdev support for your modesetting driver
                                                      ...  [DRM_FBDEV_EMULATION]
    <*> Simple framebuffer driver                                [DRM_SIMPLEDRM]
    Console display driver support --->
      [*] Framebuffer Console support                      [FRAMEBUFFER_CONSOLE]

File systems --->
  DOS/FAT/EXFAT/NT Filesystems --->
    <*/M> VFAT (Windows-95) fs support                                 [VFAT_FS]
  Pseudo filesystems --->
    <*/M> EFI Variable filesystem                                    [EFIVAR_FS]
  -*- Native language support --->                                         [NLS]
    <*/M> Codepage 437 (United States, Canada)                [NLS_CODEPAGE_437]
    <*/M> NLS ISO 8859-1  (Latin 1; Western European Languages)  [NLS_ISO8859_1]

The meaning of the configuration options:

CONFIG_PARTITION_ADVANCED: If it's not enabled, CONFIG_EFI_PARTITION will be enabled automatically. But when it's enabled, you must set CONFIG_EFI_PARTITION to enabled as well.
CONFIG_SYSFB_SIMPLEFB, CONFIG_DRM, CONFIG_DRM_FBDEV_EMULATION, CONFIG_DRM_SIMPLEDRM, CONFIG_FB, and CONFIG_FRAMEBUFFER_CONSOLE: The combination of these options provides the Linux console support on top of the UEFI framebuffer. To allow the kernel to print debug messages at an early boot stage, they shouldn't be built as kernel modules unless an initramfs will be used.

Create an Emergency Boot Disk

Ensure that an emergency boot disk is ready to “rescue” the system in case the system becomes un-bootable. To make an emergency boot disk with GRUB for an EFI based system, find a spare USB flash drive and create a vfat file system on it. Install dosfstools-4.2 first, then as the root user:

Warning

The following command will erase all directories and files in the partition. Make sure your USB flash drive contains no data which will be needed, and change sdx1 to the device node corresponding to the first partition of the USB flash drive. Be careful not to overwrite your hard drive with a typo!

mkfs.vfat /dev/sdx1

Still as the root user, use the fdisk utility to set the first partition of the USB flash drive to be an “EFI system” partition (change sdx to the device node corresponding to your USB flash drive):

fdisk /dev/sdx

Welcome to fdisk (util-linux 2.39.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): t
Partition number (1-9, default 9): 1
Partition type or alias (type L to list all): uefi
Changed type of partition 'Linux filesystem' to 'EFI System'.

Command (m for help): w
The partition table has been altered.
Syncing disks.

Still as the root user, create a mount point for the EFI partition on the USB flash drive and mount it:

mount --mkdir -v -t vfat /dev/sdx1 -o codepage=437,iocharset=iso8859-1 \
      /mnt/rescue

Install GRUB for EFI on the partition:

grub-install --target=x86_64-efi --removable \
             --efi-directory=/mnt/rescue --boot-directory=/mnt/rescue

Unmount the partition:

umount /mnt/rescue

Now the USB flash drive can be used as an emergency boot disk on any x86-64 UEFI platform. It will boot the system and show the GRUB shell. Then you can type commands to boot your operating system from the hard drive. To learn how to select the boot device, read the manual of your motherboard or laptop.

Find or Create the EFI System Partition

On EFI based systems, the bootloaders are installed in a special FAT32 partition called an EFI System Partition (ESP). If your system supports EFI, and a recent version of some Linux distribution or Windows is pre-installed, it's likely that the ESP has already been created. As the root user, list all the partitions on your hard drive (replace sda with the device corresponding to the appropriate hard drive):

fdisk -l /dev/sda

The “Type” column of the ESP should be EFI System.

If the system or the hard drive is new, or it's the first installation of a UEFI-booted OS on the system, the ESP may not exist. In that case, install dosfstools-4.2 first. Then create a new partition, make a vfat file system on it, and set the partition type to “EFI system”. See the instructions for the emergency boot device above as a reference.

Warning

Some (old) UEFI implementations may require the ESP to be the first partition on the disk.

Now, as the root user, create the mount point for the ESP, and mount it (replace sda1 with the device node corresponding to the ESP):

mount --mkdir -v -t vfat /dev/sda1 -o codepage=437,iocharset=iso8859-1 \
      /boot/efi

If you want to mount the ESP automatically during system boot, as the root user, add an entry for the ESP into /etc/fstab:

cat >> /etc/fstab << EOF
/dev/sda1 /boot/efi vfat codepage=437,iocharset=iso8859-1 0 1
EOF

Minimal Boot Configuration with GRUB and EFI

On UEFI based systems, GRUB works by installing an EFI application (a special kind of executable) into the ESP. The EFI firmware will search boot loaders in EFI applications from boot entries recorded in EFI variables, and additionally a hardcoded path EFI/BOOT/BOOTX64.EFI. Normally, a boot loader should be installed into a custom path and the path should be recorded in the EFI variables. The use of the hardcoded path should be avoided if possible. However, in some cases we have to use the hardcoded path:

The system is not booted with EFI yet, making EFI variables inaccessible.
The EFI firmware is 64-bit but the LFS system is 32-bit, making EFI variables inaccessible because the kernel cannot invoke EFI runtime services with a different virtual address length.
LFS is built for a Live USB, so we cannot rely on EFI variables, which are stored in NVRAM or EEPROM on the local machine.
You are unable or unwilling to install the efibootmgr for manipulating boot entries in EFI variables.

In these cases, follow these instructions to install the GRUB EFI application into the hardcoded path and make a minimal boot configuration. Otherwise it's better to skip ahead and set up the boot configuration normally.

To install GRUB with the EFI application in the hardcoded path EFI/BOOT/BOOTX64.EFI, first ensure the boot partition is mounted at /boot and the ESP is mounted at /boot/efi. Then, as the root user, run the command:

Note

This command will overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI. It may break a bootloader already installed there. Back it up if you are not sure.

grub-install --target=x86_64-efi --removable

This command will install the GRUB EFI application into the hardcoded path /boot/efi/EFI/BOOT/BOOTX64.EFI, so the EFI firmware can find and load it. The remaining GRUB files are installed in the /boot/grub directory and will be loaded by BOOTX64.EFI during system boot.

Note

The EFI firmware usually prefers the EFI applications with a path stored in EFI variables to the EFI application at the hardcoded path. So you may need to invoke the boot selection menu or firmware setting interface to select the newly installed GRUB manually on the next boot. Read the manual of your motherboard or laptop to learn how.

If you've followed the instructions in this section and set up a minimal boot configuration, now skip ahead to “Creating the GRUB Configuration File”.

Mount the EFI Variable File System

The installation of GRUB on a UEFI platform requires that the EFI Variable file system, efivarfs, is mounted. As the root user, mount it if it's not already mounted:

mountpoint /sys/firmware/efi/efivars || mount -v -t efivarfs efivarfs /sys/firmware/efi/efivars

Now add an entry for the efivarfs in /etc/fstab so it will be mounted automatically during system boot:

cat >> /etc/fstab << EOF
efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 0
EOF

Warning

If the system is not booted with UEFI, the directory /sys/firmware/efi will be missing. In this case you should boot the system in UEFI mode with the emergency boot disk or using a minimal boot configuration created as above, then mount efivarfs and continue.

Setting Up the Configuration

On UEFI based systems, GRUB works by installing an EFI application (a special kind of executable) into /boot/efi/EFI/[id]/grubx64.efi, where /boot/efi is the mount point of the ESP, and [id] is replaced with an identifier specified in the grub-install command line. GRUB will create an entry in the EFI variables containing the path EFI/[id]/grubx64.efi so the EFI firmware can find grubx64.efi and load it.

grubx64.efi is very lightweight (136 KB with GRUB-2.06) so it will not use much space in the ESP. A typical ESP size is 100 MB (for Windows boot manager, which uses about 50 MB in the ESP). Once grubx64.efi has been loaded by the firmware, it will load GRUB modules from the boot partition. The default location is /boot/grub.

As the root user, install the GRUB files into /boot/efi/EFI/LFS/grubx64.efi and /boot/grub. Then set up the boot entry in the EFI variables:

grub-install --bootloader-id=LFS --recheck

If the installation is successful, the output should be:

Installing for x86_64-efi platform.
Installation finished. No error reported.

Issue the efibootmgr | cut -f 1 command to recheck the EFI boot configuration. An example of the output is:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0005,0000,0002,0001,0003,0004
Boot0000* ARCH
Boot0001* UEFI:CD/DVD Drive
Boot0002* Windows Boot Manager
Boot0003* UEFI:Removable Device
Boot0004* UEFI:Network Device
Boot0005* LFS

Note that 0005 is the first in the BootOrder, and Boot0005 is LFS. This means that on the next boot, the version of GRUB installed by LFS will be used to boot the system.

Creating the GRUB Configuration File

Generate /boot/grub/grub.cfg to configure the boot menu of GRUB:

cat > /boot/grub/grub.cfg << EOF
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5

insmod part_gpt
insmod ext2
set root=(hd0,2)

insmod all_video
if loadfont /boot/grub/fonts/unicode.pf2; then
  terminal_output gfxterm
fi

menuentry "GNU/Linux, Linux 6.7.4-lfs-12.1"  {
  linux   /boot/vmlinuz-6.7.4-lfs-12.1 root=/dev/sda2 ro
}

menuentry "Firmware Setup" {
  fwsetup
}
EOF

Refer to the LFS book for the basic knowledge about the grub.cfg file. (hd0,2), sda2, and 6.4.10-lfs-12.0 must match your configuration.

The insmod all_video directive loads various modules for video support. It's needed to initialize the EFI framebuffer for the kernel to print messages correctly before the kernel GPU driver initialization.

The terminal_output gfxterm directive changes the display resolution of the GRUB menu to match your display device. It will break the rendering if the unicode.pf2 font data file is not loaded, so it's guarded by a if directive.

Note

From GRUB's perspective, the files are relative to the partitions used. If you used a separate /boot partition, remove /boot from the above paths (to kernel and to unicode.pf2). You will also need to change the "set root" line to point to the boot partition.

The Firmware Setup entry can be used to enter the configuration interface provided by the firmware (sometimes called “BIOS configuration”).

Dual-booting with Windows

Add a menu entry for Windows into grub.cfg:

cat >> /boot/grub/grub.cfg << EOF
# Begin Windows addition

menuentry "Windows 11" {
  insmod fat
  insmod chain
  set root=(hd0,1)
  chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
EOF

(hd0,1) should be replaced with the GRUB designated name for the ESP. The chainloader directive can be used to tell GRUB to run another EFI executable, in this case the Windows Boot Manager. You may put more usable tools in EFI executable format (for example, an EFI shell) into the ESP and create GRUB entries for them, as well.

Chapter 6. Text Editors

This chapter is referenced in the LFS book for those wishing to use other editors on their LFS system. You're also shown how some LFS installed programs benefit from being recompiled after GUI libraries have been installed.

Bluefish-2.2.14

Introduction to Bluefish

Bluefish is a GTK+ text editor targeted towards programmers and web designers, with many options to write websites, scripts and programming code. Bluefish supports many programming and markup languages, and it focuses on editing dynamic and interactive websites.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.bennewitz.com/bluefish/stable/source/bluefish-2.2.14.tar.bz2
Download MD5 sum: c99b6b1ba3e3e70b032936182bb0b387
Download size: 4.5 MB
Estimated disk space required: 53 MB
Estimated build time: 0.3 SBU

Bluefish Dependencies

Required

GTK+-3.24.41

Optional

enchant-2.6.7 (for spell checking), Gucharmap-15.1.2, PCRE-8.45 and Jing

Installation of Bluefish

Install Bluefish by running the following commands:

./configure --prefix=/usr --docdir=/usr/share/doc/bluefish-2.2.14 &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Note

This package installs icon files into the /usr/share/icons/hicolor hierarchy and desktop files into the /usr/share/applications hierarchy. You can improve system performance and memory usage by updating /usr/share/icons/hicolor/icon-theme.cache and /usr/share/applications/mimeinfo.cache. To perform the update you must have desktop-file-utils-0.27 (for the desktop cache) and issue the following commands as the root user:

gtk-update-icon-cache -t -f --include-image-data /usr/share/icons/hicolor &&
update-desktop-database

Installed Program: bluefish

Installed Libraries: several under /usr/lib/bluefish/

Installed Directories: /usr/lib/bluefish, /usr/share/bluefish, /usr/share/doc/bluefish-2.2.14, and /usr/share/xml/bluefish

Short Descriptions

bluefish

is a GTK+ text editor for markup and programming

Ed-1.20.1

Introduction to Ed

Ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. Ed isn't something which many people use. It's described here because it can be used by the patch program if you encounter an ed-based patch file. This happens rarely because diff-based patches are preferred these days.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/ed/ed-1.20.1.tar.lz
Download MD5 sum: f9e7c445acebf6c49ccb7f86a5b17f5d
Download size: 68 KB
Estimated disk space required: 1.0 MB
Estimated build time: less than 0.1 SBU

Ed Dependencies

Required to uncompress the tarball

libarchive-3.7.2 (for bsdtar)

Installation of Ed

Install Ed by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Programs: ed and red

Installed Libraries: None

Installed Directories: None

Short Descriptions

ed	is a line-oriented text editor
red	is a restricted ed—it can only edit files in the current directory and cannot execute shell commands

Emacs-29.2

Introduction to Emacs

The Emacs package contains an extensible, customizable, self-documenting real-time display editor.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/emacs/emacs-29.2.tar.xz
Download MD5 sum: 0690e2fb9b9f271652f19ddccf1dd3f3
Download size: 50 MB
Estimated disk space required: 526 MB
Estimated build time: 0.7 SBU (Using parallelism=4)

Emacs Dependencies

Optional

a graphical environment, alsa-lib-1.2.11, Cairo-1.18.0, dbus-1.14.10, gobject-introspection-1.78.1, gsettings-desktop-schemas-45.0, GPM-1.20.7, GTK+-3.24.41, ImageMagick-7.1.1-28, Little CMS-2.14, libjpeg-turbo-3.0.1, libpng-1.6.42, librsvg-2.57.1, libseccomp-2.5.5, libwebp-1.3.2, libxml2-2.12.5, MIT Kerberos V5-1.21.2, SQLite-3.45.1, Valgrind-3.22.0, intlfonts, libungif, libotf, and m17n-lib - to correctly display such complex scripts as Indic and Khmer, and also for scripts that require Arabic shaping support (Arabic and Farsi), mailutils, and libXaw3d

Installation of Emacs

Install Emacs by running the following commands:

./configure --prefix=/usr &&
make

This package does not come with a test suite. If make succeeds, you can test the result by running src/emacs -Q, which is the program that will be installed, with its auxiliary files. This should start and display the application opening screen.

Now, as the root user:

make install &&
chown -v -R root:root /usr/share/emacs/29.2 &&
rm -vf /usr/lib/systemd/user/emacs.service

Note

This package installs icon files into the /usr/share/icons/hicolor hierarchy and you can improve system performance and memory usage by updating /usr/share/icons/hicolor/index.theme. To perform the update you must have GTK+-3.24.41 installed and issue the following command as the root user:

gtk-update-icon-cache -qtf /usr/share/icons/hicolor

Command Explanations

--with-imagemagick: Use this if you have installed ImageMagick-7.1.1-28 and wish to link against it.

--with-gif=no: Use this if you have not installed giflib-5.2.1 or libungif.

--with-tiff=no: Use this if you have not installed libtiff-4.6.0.

--with-gnutls=no: Use this if you have not installed GnuTLS-3.8.3.

--without-harfbuzz: Use this if you have not installed HarfBuzz-8.3.0.

--with-json=no: Use this if you have not installed jansson-2.14.

Installed Programs: ctags, ebrowse, emacs (symlink), emacs-29.2, emacsclient, and etags

Installed Libraries: None

Installed Directories: /usr/libexec/emacs and /usr/share/emacs

Short Descriptions

ctags	creates cross-reference tagfile database files for source code
ebrowse	permits browsing of C++ class hierarchies from within emacs
emacs	is an editor
emacsclient	attaches an emacs session to an already running emacsserver instance
etags	is another program to generate source code cross-reference tagfiles

Gedit-46.2

Introduction to Gedit

The Gedit package contains a lightweight UTF-8 text editor for the GNOME Desktop.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/gedit/46/gedit-46.2.tar.xz
Download MD5 sum: 01327f0d35778d8f3a914fffb69e8cd6
Download size: 2.6 MB
Estimated disk space required: 66 MB (with tests)
Estimated build time: 0.2 SBU (using parallelism=4; with tests)

Gedit Dependencies

Required

gsettings-desktop-schemas-45.0, itstool-2.0.7, libpeas-1.36.0, libgeditsourceview-299.0.4, and tepl-6.8.0

Optional

GTK-Doc-1.33.2, Vala-0.56.14, and zeitgeist

Installation of Gedit

Install Gedit by running the following commands:

mkdir gedit-build &&
cd    gedit-build &&

meson setup --prefix=/usr       \
            --buildtype=release \
            -Dgtk_doc=false     \
            .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Note

If you installed the package to your system using a “DESTDIR” method, /usr/share/glib-2.0/schemas/gschemas.compiled was not updated/created. Create (or update) the file using the following command as the root user:

glib-compile-schemas /usr/share/glib-2.0/schemas

Command Explanations

-Dgtk_doc=false: This switch disables generating the API documentation. Omit this switch if you have GTK-Doc-1.33.2 installed and wish to generate the API documentation.

Installed Program: gedit

Installed Libraries: libgedit-46.so

Installed Directories: /usr/include/gedit-46 and /usr/{lib,share,share/help/*}/gedit

Short Descriptions

gedit

is a lightweight text editor integrated with the GNOME Desktop

JOE-4.6

Introduction to JOE

JOE (Joe's own editor) is a small text editor capable of emulating WordStar, Pico, and Emacs.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/joe-editor/joe-4.6.tar.gz
Download MD5 sum: 9017484e6116830d846678b625ea5c43
Download size: 1.8 MB
Estimated disk space required: 22 MB
Estimated build time: 0.2 SBU

Installation of JOE

Install JOE by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --docdir=/usr/share/doc/joe-4.6 &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&

install -vm 755 joe/util/{stringify,termidx,uniproc} /usr/bin

Configuring JOE

Config Files

/etc/joe/jmacsrc, /etc/joe/joerc, /etc/joe/jpicorc, /etc/joe/jstarrc, /etc/joe/rjoerc, and ~/.joerc

Installed Programs: jmacs, joe, jpico, jstar, rjoe, stringify, termidx, and uniproc

Installed Libraries: None

Installed Directories: /etc/joe, /usr/share/joe, and /usr/share/doc/joe-4.6

Short Descriptions

jmacs	is a symbolic link to joe used to launch Emacs emulation mode
joe	is a small text editor capable of emulating WordStar, Pico, and Emacs
jpico	is a symbolic link to joe used to launch Pico emulation mode
jstar	is a symbolic link to joe used to launch WordStar emulation mode
rjoe	is a symbolic link to joe that restricts JOE to editing only files which are specified on the command-line
stringify	is a program used by joe to convert rc and .jsf files into a C file (see /usr/share/doc/joe-4.6/util/README)
termidx	is a program used by joe to generate the termcap index file (see /usr/share/doc/joe-4.6/util/README)
uniproc	is a program used by joe to generate joe's unicode database file unicat.c from Blocks.txt CaseFolding.txt EastAsianWidth.txt and UnicodeData.txt (find them at /usr/share/doc/joe-4.6/util; see usr/share/doc/joe-4.6/util/README)

Kate-23.08.5

Introduction to Kate

The Kate package contains an advanced KF5 based graphical text editor.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.kde.org/stable/release-service/23.08.5/src/kate-23.08.5.tar.xz
Download MD5 sum: 46323fc33eea7a38816277b47b1fa08a
Download size: 7.7 MB
Estimated disk space required: 217 MB
Estimated build time: 0.7 SBU (using parallelism=4)

Kate Dependencies

Required

KDE Frameworks-5.115.0

Optional

libgit2

Installation of Kate

Install Kate by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=$KF5_PREFIX  \
      -DCMAKE_BUILD_TYPE=Release          \
      -DBUILD_TESTING=OFF                 \
      -Wno-dev .. &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: kate and kwrite

Installed Libraries: Several plugins under $KF5_PREFIX/lib/plugins

Installed Directories: $KF5_PREFIX/lib/plugins/ktexteditor, $KF5_PREFIX/lib/plugins/plasma/dataengine, $KF5_PREFIX/share/doc/HTML/*/{kate,katepart,kwrite}, $KF5_PREFIX/share/{kateproject,katexmltools}, and $KF5_PREFIX/share/plasma/plasmoids/org.kde.plasma.katesessions

Short Descriptions

kate	is an advanced text editor for kde
kwrite	is a text editor for KDE, that is a light version of kate

Mousepad-0.6.2

Introduction to Mousepad

Mousepad is a simple GTK+ 3 text editor for the Xfce desktop environment.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://archive.xfce.org/src/apps/mousepad/0.6/mousepad-0.6.2.tar.bz2
Download MD5 sum: 3ad46198202d2696cac27d5a0f08bab0
Download size: 1.3 MB
Estimated disk space required: 16 MB
Estimated build time: 0.1 SBU

Mousepad Dependencies

Required

gtksourceview4-4.8.4

Optional

DConf-0.40.0 (runtime) and dbus-glib-0.112

Installation of Mousepad

Install Mousepad by running the following commands:

./configure --prefix=/usr           \
            --enable-gtksourceview4 \
            --enable-keyfile-settings &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--enable-keyfile-settings: Use the GSettings keyfile backend rather than the default DConf-0.40.0.

Installed Program: mousepad

Installed Libraries: None

Installed Directories: None

Short Descriptions

mousepad

is a simple GTK+ 3 text editor

Nano-7.2

Introduction to Nano

The Nano package contains a small, simple text editor which aims to replace Pico, the default editor in the Pine package.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.nano-editor.org/dist/v7/nano-7.2.tar.xz
Download MD5 sum: 13742c686c6ddb0b7b294634f0c13cec
Download size: 1.5 MB
Estimated disk space required: 20 MB
Estimated build time: 0.2 SBU

Installation of Nano

Install Nano by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --enable-utf8     \
            --docdir=/usr/share/doc/nano-7.2 &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&
install -v -m644 doc/{nano.html,sample.nanorc} /usr/share/doc/nano-7.2

Command Explanations

--enable-utf8: This switch enables unicode support in Nano.

Configuring nano

Config Files

/etc/nanorc and ~/.nanorc

Configuration Information

Example configuration (create as a system-wide /etc/nanorc or a personal ~/.nanorc file)

set autoindent
set constantshow
set fill 72
set historylog
set multibuffer
set nohelp
set positionlog
set quickblank
set regexp

Check the sample.nanorc file in the installed documentation directory. It includes color configurations and has some documentation included in the comments.

Syntax highlighting is provided for several file types, in /usr/share/nano/ directory. E.g., for shell scripts, you can insert include /usr/share/nano/sh.nanorc in the personal or global configuration file. If you wish highlighting for all supported files, use include /usr/share/nano/*.nanorc. This include does not descend into the extra directory. Move required files one level up.

Installed Programs: nano and rnano (symlink)

Installed Libraries: None

Installed Directories: /usr/share/nano and /usr/share/doc/nano-7.2

Short Descriptions

nano	is a small, simple text editor which aims to replace Pico, the default editor in the Pine package
rnano	is a restricted mode for nano

Vim-9.1.0041

Introduction to Vim

The Vim package, which is an abbreviation for VI IMproved, contains a vi clone with extra features as compared to the original vi.

The default LFS instructions install vim as a part of the base system. If you would prefer to link vim against X, you should recompile vim to enable GUI mode. There is no need for special instructions since X support is automatically detected.

Note

The version of vim changes daily. To get the latest version, go to https://github.com/vim/vim/releases.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/vim/vim/archive/v9.1.0041/vim-9.1.0041.tar.gz
Download MD5 sum: 79dfe62be5d347b1325cbd5ce2a1f9b3
Download size: 17 MB
Estimated disk space required: 125 MB (add 67 MB for tests)
Estimated build time: 0.3 SBU (with parallelism=4; add 3.0 SBU for tests)

Vim Dependencies

Optional

GPM-1.20.7, Lua-5.4.6, Ruby-3.3.0, and rsync-3.2.7

Installation of Vim

Note

If you recompile Vim to link against X and your X libraries are not on the root partition, you will no longer have an editor for use in emergencies. You may choose to install an additional editor, not link Vim against X, or move the current vim executable to the /bin directory under a different name such as vi.

Install Vim by running the following commands:

Note

If you intend to run the tests and have not installed Xorg in /usr, append LDFLAGS='-L$XORG_PREFIX/lib' to the configure line below.

echo '#define SYS_VIMRC_FILE  "/etc/vimrc"' >>  src/feature.h &&
echo '#define SYS_GVIMRC_FILE "/etc/gvimrc"' >> src/feature.h &&

./configure --prefix=/usr        \
            --with-features=huge \
            --enable-gui=gtk3    \
            --with-tlib=ncursesw &&
make

Note

If the global configuration file /etc/vimrc references the VIMRUNTIME environment variable, some tests may complain about being unable to find the corresponding directory and wait for user input. If this is the case, this file should be saved and removed before running the tests. Or if bubblewrap-0.8.0 is installed, it's also possible to create a lightweight container environment where this file is hidden and run the tests in the container.

To test the results, issue: make -j1 test, or bwrap --dev-bind / / --dev-bind /dev/null /etc/vimrc make -j1 test if running the tests with bubblewrap-0.8.0 and /etc/vimrc hidden. Even if one of the tests fails to produce the file test.out in src/testdir, the remaining tests will still be executed. If all goes well, the log will report ALL DONE. Some tests labelled as “flaky” may fail occasionally and can be ignored. The tests are known to fail if the output is redirected to a file, and also if they are run in a 'screen' session.

Note

Some color tests expect to be executed under the xterm terminal emulator.

Now, as the root user:

make install

By default, Vim's documentation is installed in /usr/share/vim. The following symlink allows the documentation to be accessed via /usr/share/doc/vim-9.1.0041, making it consistent with the location of documentation for other packages:

ln -snfv ../vim/vim91/doc /usr/share/doc/vim-9.1.0041

If you wish to update the runtime files, issue the following command (requires rsync-3.2.7) to download it:

rsync -avzcP --exclude="/dos/" --exclude="/spell/" \
    ftp.nluug.nl::Vim/runtime/ ./runtime/

And then install the updated runtime files and regenerate the tags file, as the root user issue:

make -C src installruntime &&
vim -c ":helptags /usr/share/doc/vim-9.1.0041" -c ":q"

Command Explanations

--with-features=huge: This switch enables all the additional features available in Vim, including support for multibyte characters.

--with-tlib=ncursesw: This switch forces Vim to link against the libncursesw library.

--enable-gui=no: This will prevent compilation of the GUI. Vim will still link against X, so that some features such as the client-server model or the x11-selection (clipboard) are still available.

--without-x: If you prefer not to link Vim against X, use this switch.

--enable-luainterp, --enable-perlinterp, --enable-python3interp=dynamic, --enable-tclinterp --with-tclsh=tclsh, --enable-rubyinterp: These options include the Lua, Perl, Python3, Tcl, or Ruby interpreters that allow using other application code in vim scripts. All the --enable-* options can accept =dynamic to dynamically load the interpreter when needed. This is required for Python 3 to prevent segmentation faults. For tcl, it is necessary to indicate the name of the tclsh executable, since configure only searches versioned names with old versions.

Configuring Vim

Config Files

/etc/vimrc and ~/.vimrc

Configuration Information

Vim has an integrated spell checker which you can enable by issuing the following in a vim window:

:setlocal spell spelllang=ru

This setting will enable spell checking for the Russian language for the current session.

By default, Vim only installs spell files for the English language. If a spell file is not available for a language, then Vim will call the $VIMRUNTIME/plugin/spellfile.vim plugin and will try to obtain the *.spl and optionally *.sug from the vim ftp server, by using the $VIMRUNTIME/plugin/netrwPlugin.vim plugin.

Alternatively you can manually download the *.spl and *.sug files from: ftp://ftp.vim.org/pub/vim/runtime/spell/ and save them to ~/.vim/spell or in /usr/share/vim/vim91/spell/.

To find out what's new in Vim-9.1.0041 issue the following command:

:help version-9.1.0041

For additional information on setting up Vim configuration files, see The vimrc Files and https://vim.fandom.com/wiki/Example_vimrc.

A list of the reinstalled files, along with their short descriptions can be found in the LFS Vim Installation Instructions.

Installed Programs: gview, gvim, gvimdiff, gvimtutor, rgview, and rgvim

Installed Libraries: None

Installed Directory: /usr/share/vim

Short Descriptions

gview	starts gvim in read-only mode
gvim	is the editor that runs under X and includes a GUI
gvimdiff	edits two or three versions of a file with gvim and shows the differences
gvimtutor	teaches the basic keys and commands of gvim
rgview	is a restricted version of gview
rgvim	is a restricted version of gvim

Chapter 7. Shells

We are all familiar with the Bourne Again SHell, but there are two other user interfaces that are considered useful modern shells – the Berkeley Unix C shell and the Korn shell. This chapter installs packages compatible with these additional shell types.

Dash-0.5.12

Introduction to Dash

Dash is a POSIX compliant shell. It can be installed as /bin/sh or as the default shell for either root or a second user with a userid of 0. It depends on fewer libraries than the Bash shell and is therefore less likely to be affected by an upgrade problem or disk failure. Dash is also useful for checking that a script is completely compatible with POSIX syntax.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://gondor.apana.org.au/~herbert/dash/files/dash-0.5.12.tar.gz
Download MD5 sum: 57222b768b84003ea4b801e5d5e0e52b
Download size: 244 KB
Estimated disk space required: 2.9 MB
Estimated build time: less than 0.1 SBU

Dash Dependencies

Optional

libedit (command line editor library)

Installation of Dash

Install Dash by running the following commands:

./configure --bindir=/bin --mandir=/usr/share/man &&
make

This package does not come with a test suite.

Now, as the root user:

make install

If you would like to make dash the default sh, recreate the /bin/sh symlink as the root user:

Note

If you create the symbolic link from dash to sh, you will need to reset the link to bash to build LFS.

ln -svf dash /bin/sh

Command Explanations

--bindir=/bin: This parameter places the dash binary into the root filesystem.

--with-libedit: To compile Dash with libedit support.

Configuring Dash

Config Files

Dash sources /etc/profile and ~/.profile

Configuration Information

Update /etc/shells to include the Dash shell by issuing the following command as the root user:

cat >> /etc/shells << "EOF"
/bin/dash
EOF

Installed Program: dash

Installed Libraries: None

Installed Directories: None

Short Description

dash

is a POSIX compliant shell

Tcsh-6.24.10

Introduction to Tcsh

The Tcsh package contains “an enhanced but completely compatible version of the Berkeley Unix C shell (csh)”. This is useful as an alternative shell for those who prefer C syntax to that of the bash shell, and also because some programs require the C shell in order to perform installation tasks.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://astron.com/pub/tcsh/tcsh-6.24.10.tar.gz
Download MD5 sum: 8fe4421f3cac3f230b3fe88df6ccff5f
Download size: 936 KB
Estimated disk space required: 11 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Installation of Tcsh

Install Tcsh by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install install.man &&

ln -v -sf tcsh   /bin/csh &&
ln -v -sf tcsh.1 /usr/share/man/man1/csh.1

Command Explanations

ln -v -sf tcsh /bin/csh: The FHS states that if there is a C shell installed, there should be a symlink from /bin/csh to it. This creates that symlink.

Configuring Tcsh

Config Files

There are numerous configuration files for the C shell. Examples of these are /etc/csh.cshrc, /etc/csh.login, /etc/csh.logout, ~/.tcshrc, ~/.cshrc, ~/.history, ~/.cshdirs, ~/.login, and ~/.logout. More information on these files can be found in the tcsh(1) man page.

Configuration Information

Update /etc/shells to include the C shell program names (as the root user):

cat >> /etc/shells << "EOF"
/bin/tcsh
/bin/csh
EOF

The following ~/.cshrc provides two alternative colour prompts and coloured ls output. If you prefer a global modification, issue the command as the root user, replacing ~/.cshrc by /etc/csh.cshrc.

cat > ~/.cshrc << "EOF"
# Original at:
# https://www.cs.umd.edu/~srhuang/teaching/code_snippets/prompt_color.tcsh.html

# Modified by the BLFS Development Team.

# Add these lines to your ~/.cshrc (or to /etc/csh.cshrc).

# Colors!
set     red="%{\033[1;31m%}"
set   green="%{\033[0;32m%}"
set  yellow="%{\033[1;33m%}"
set    blue="%{\033[1;34m%}"
set magenta="%{\033[1;35m%}"
set    cyan="%{\033[1;36m%}"
set   white="%{\033[0;37m%}"
set     end="%{\033[0m%}" # This is needed at the end...

# Setting the actual prompt.  Two separate versions for you to try, pick
# whichever one you like better, and change the colors as you want.
# Just don't mess with the ${end} guy in either line...  Comment out or
# delete the prompt you don't use.

set prompt="${green}%n${blue}@%m ${white}%~ ${green}%%${end} "
set prompt="[${green}%n${blue}@%m ${white}%~ ]${end} "

# This was not in the original URL above
# Provides coloured ls
alias ls ls --color=always

# Clean up after ourselves...
unset red green yellow blue magenta cyan yellow white end
EOF

Installed Program: tcsh

Installed Libraries: None

Installed Directory: None

Short Descriptions

tcsh

is an enhanced but completely compatible version of the Berkeley Unix C shell, csh. It is usable as both an interactive shell and a script processor

zsh-5.9

Introduction to zsh

The zsh package contains a command interpreter (shell) usable as an interactive login shell and as a shell script command processor. Of the standard shells, zsh most closely resembles ksh but includes many enhancements.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.zsh.org/pub/zsh-5.9.tar.xz
Download MD5 sum: 182e37ca3fe3fa6a44f69ad462c5c30e
Download size: 3.2 MB
Estimated disk space required: 48 MB (includes documentation and tests)
Estimated build time: 1.6 SBU (Using parallelism=4; includes documentation and tests)

Note

When there is a new zsh release, the old files shown above are moved to a new server directory: https://www.zsh.org/pub/old/.

zsh Dependencies

Optional

PCRE-8.45, Valgrind-3.22.0, and yodl

Installation of zsh

Adapt the documentation build system for texinfo-7.0 or later:

sed -e 's/set_from_init_file/texinfo_&/' \
    -i Doc/Makefile.in

The documentation files contain references to zsh configuration files in /etc, but we'll use /etc/zsh to hold these configuration files instead. The building system will fix up those references if the yodl package is available, but it's out of the scope of BLFS. So we need to fix up the references manually:

sed 's|/etc/z|/etc/zsh/z|g' -i Doc/*.*

Install zsh by running the following commands:

./configure --prefix=/usr            \
            --sysconfdir=/etc/zsh    \
            --enable-etcdir=/etc/zsh \
            --enable-cap             \
            --enable-gdbm                      &&
make                                           &&

makeinfo  Doc/zsh.texi --html      -o Doc/html &&
makeinfo  Doc/zsh.texi --plaintext -o zsh.txt  &&
makeinfo  Doc/zsh.texi --html --no-split --no-headers -o zsh.html

If you have texlive-20230313 installed, you can build PDF format of the documentation by issuing the following command:

texi2pdf  Doc/zsh.texi -o Doc/zsh.pdf

To test the results, issue: make check.

Now, as the root user:

make install                                                    &&
make infodir=/usr/share/info install.info                       &&
make htmldir=/usr/share/doc/zsh-5.9/html install.html           &&
install -v -m644 zsh.{html,txt} Etc/FAQ /usr/share/doc/zsh-5.9

If you built the PDF format of the documentation, install it by issuing the following command as the root user:

install -v -m644 Doc/zsh.pdf /usr/share/doc/zsh-5.9

Command Explanations

--sysconfdir=/etc/zsh and --enable-etcdir=/etc/zsh: These parameters are used so that all the zsh configuration files are consolidated into the /etc/zsh directory. Omit these parameters if you wish to retain historical compatibility by having all the files located in the /etc directory.

--enable-cap: This option enables POSIX capabilities.

--enable-gdbm: This option enables the use of the GDBM library.

--enable-pcre: This option allows zsh to use the PCRE regular expression library in shell builtins.

Configuring zsh

Config Files

There are a whole host of configuration files for zsh including /etc/zsh/zshenv, /etc/zsh/zprofile, /etc/zsh/zshrc, /etc/zsh/zlogin and /etc/zsh/zlogout. You can find more information on these in the zsh(1) and related manual pages.

The first time zsh is executed, you will be prompted by messages asking several questions. The answers will be used to create a ~/.zshrc file. If you wish to run these questions again, run zsh /usr/share/zsh/5.9/functions/zsh-newuser-install -f.

There are several built-in advanced prompts. In the zsh shell, start advanced prompt support with autoload -U promptinit, then promptinit. Available prompt names are listed with prompt -l. Select a particular one with prompt <prompt-name>. Display all available prompts with prompt -p. Except for the list and display commands above, you can insert the other ones in ~/.zshrc to be automatically executed at shell start, with the prompt you chose.

Configuration Information

Update /etc/shells to include the zsh shell program names (as the root user):

cat >> /etc/shells << "EOF"
/bin/zsh
EOF

Installed Programs: zsh and zsh-5.9 (hardlinked to each other)

Installed Libraries: Numerous plugin helper modules under /usr/lib/zsh/5.9/

Installed Directories: /usr/{lib,share}/zsh and /usr/share/doc/zsh-5.9

Short Description

zsh

is a shell which has command-line editing, built-in spelling correction, programmable command completion, shell functions (with autoloading), a history mechanism, and a host of other features

Chapter 8. Virtualization

Virtualization allows running a complete operating system, or virtual machine (VM), within another operating environment as a task. There are several commercial and open source environments that either emulate another processor or utilize the hardware virtualization features of the host processor.

qemu-8.2.1

Introduction to qemu

qemu is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.qemu.org/qemu-8.2.1.tar.xz
Download MD5 sum: bda54248d773be2599df66f8995f10e1
Download size: 124 MB
Estimated disk space required: 2.2 GB (373 MB installed)
Estimated build time: 1.3 SBU (add 0.8 SBU for tests, both using parallelism=4)

Qemu Dependencies

Note

This optional dependencies list is not comprehensive. See the output of ./configure --help for a more complete list.

Editor Notes: https://wiki.linuxfromscratch.org/blfs/wiki/qemu

KVM Prerequisites

Before building qemu, check to see if your processor supports Virtualization Technology (VT):

grep -E '^flags.*(vmx|svm)' /proc/cpuinfo

If you get any output, you have VT technology (vmx for Intel processors and svm for AMD processors). You then need to go into your system BIOS and ensure it is enabled. After enabling, reboot back to your LFS instance.

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel if necessary:

[*] Virtualization --->                                         [VIRTUALIZATION]
  <*/M>   Kernel-based Virtual Machine (KVM) support                       [KVM]
  # Enable the option for your CPU:
  < /*/M>   KVM for Intel (and compatible) processors support        [KVM_INTEL]
  < /*/M>   KVM for AMD processors support                             [KVM_AMD]

The Intel or AMD settings are not both required, but the one matching your system processor is required.

To use the “bridge” network device, as explained below, check that bridge-utils-1.7.1 is installed and the following options in the kernel configuration are enabled:

[*] Networking support --->                                                [NET]
  Networking options --->
    <*/M> 802.1d Ethernet Bridging                                      [BRIDGE]

Device Drivers --->
  [*] Network device support --->                                   [NETDEVICES]
    [*]   Network core driver support                                 [NET_CORE]
    <*/M>   Universal TUN/TAP device driver support                        [TUN]

Installation of qemu

The udev rule of LFS only allows the root user, the users owning a local login session supported by the optional runtime dependency elogind-252.9 , or the users in the kvm group to use the KVM device. As the root user, add any non-root users that might use the KVM device either without elogind-252.9 installed or remotely (via a SSH connection) to the kvm group:

usermod -a -G kvm <username>

Install qemu by running the following commands:

Note

Qemu is capable of running many targets. The build process is also capable of building multiple targets at one time in a comma delimited list assigned to --target-list. Run ./configure --help to get a complete list of available targets.

if [ $(uname -m) = i686 ]; then
   QEMU_ARCH=i386-softmmu
else
   QEMU_ARCH=x86_64-softmmu
fi


mkdir -vp build &&
cd        build &&

../configure --prefix=/usr               \
             --sysconfdir=/etc           \
             --localstatedir=/var        \
             --target-list=$QEMU_ARCH    \
             --audio-drv-list=alsa       \
             --disable-pa                \
             --enable-slirp              \
             --docdir=/usr/share/doc/qemu-8.2.1 &&

unset QEMU_ARCH &&

make

qemu uses ninja as a subprocess when building. To run the tests, issue: ninja test. Two tests, bios-tables-test and migration-test, are known to fail.

Now, as the root user:

make install

Change the permissions and ownership of a helper script, which is needed when using the “bridge” network device (see below). Again as the root user, issue:

Note

You need to add any users who might use the “bridge” network device into the kvm group even if elogind-252.9 is installed.

chgrp kvm  /usr/libexec/qemu-bridge-helper &&
chmod 4750 /usr/libexec/qemu-bridge-helper

Note

For convenience you may want to create a symbolic link to run the installed program. For instance (as the root user):

ln -sv qemu-system-`uname -m` /usr/bin/qemu

Command Explanations

--audio-drv-list=alsa: This switch sets the audio driver to ALSA. See below for enabling other audio drivers.

--disable-pa: even if pa is not in --audio-drv-list list, the pulseaudio driver is built, unless disabled by this parameter.

--enable-slirp: This switch forces the building system to check for Libslirp-4.7.0. Remove it if you don't need the -netdev user support.

--audio-drv-list=pa --disable-alsa: This switch sets the audio driver to pulseaudio. For other drivers see the --audio-drv-list choices in the output of ./configure --help. The default audio driver is OSS. To enable support for both alsa and pulseaudio, use --audio-drv-list=alsa,pa.

Using Qemu

Since using qemu means using a virtual computer, the steps to set up the virtual machine are in close analogy with those to set up a real computer. You'll need to decide about CPU, memory, disk, USB devices, network card(s), screen size, etc. Once the “hardware” is decided, you'll have for example to choose how to connect the machine to internet, and/or to install an OS. In the following, we show basic ways of performing those steps. But qemu is much more than this, and it is strongly advised to read the qemu documentation in /usr/share/doc/qemu-8.2.1/qemu-doc.html.

Note

It is standard practice to name the computer running qemu “host” and the emulated machine running under qemu the “guest”. We'll use those notations in the following.

Note

The following instructions assume the optional symbolic link, qemu, has been created. Additionally, qemu should be run in a graphical environment. But it is possible to use qemu “headless” or through SSH. See the documentation for the various possibilities.

Disk

A virtual disk may be set up in the following way:

VDISK_SIZE=50G
VDISK_FILENAME=vdisk.img
qemu-img create -f qcow2 $VDISK_FILENAME $VDISK_SIZE

The virtual disk size and filename should be adjusted as desired. The actual size of the file will be less than specified, but will expand as needed, so it is safe to put a high value.

Operating System

To install an operating system, download an iso image from your preferred Linux distribution. For the purposes of this example, we'll use Fedora-16-x86_64-Live-LXDE.iso in the current directory. Run the following:

qemu -enable-kvm                           \
     -drive file=$VDISK_FILENAME           \
     -cdrom Fedora-16-x86_64-Live-LXDE.iso \
     -boot d                               \
     -m 1G

Follow the normal installation procedures for the chosen distribution. The -boot option specifies the boot order of drives as a string of drive letters. Valid drive letters are: a, b (floppy 1 and 2), c (first hard disk), d (first CD-ROM). The -m option is the amount of memory to use for the virtual machine. The choice depends on the load of the host. Modern distributions should be comfortable with 1GB. The -enable-kvm option allows hardware acceleration. Without this switch, the emulation is much slower.

Defining the virtual hardware

The virtual machine hardware is defined by the qemu command line. An example command is given below:

qemu -enable-kvm                     \
     -smp 4                          \
     -cpu host                       \
     -m 1G                           \
     -drive file=$VDISK_FILENAME     \
     -cdrom grub-img.iso             \
     -boot order=c,once=d,menu=on    \
     -net nic,netdev=net0            \
     -netdev user,id=net0            \
     -device ac97                    \
     -vga std                        \
     -serial mon:stdio               \
     -name "fedora-16"

Meaning of the command line options

-enable-kvm: enable full KVM virtualization support. On some hardware, it may be necessary to add the undocumented -machine smm=off option in order to enable KVM.

-smp <N>: enable symmetric multiprocessing with <N> CPUs.

-cpu <model>: simulate CPU <model>. the list of supported models can be obtained with -cpu help.

-drive file=<filename>: defines a virtual disk whose image is stored in <filename>.

-cdrom grub-img.iso: defines an iso formatted file to use as a cdrom. Here we use a grub rescue disk, which may turn handy when something goes wrong at boot time.

-boot order=c,once=d,menu=on: defines the boot order for the virtual BIOS.

-net nic,netdev=<netid>: defines a network card connected to the network device with id <netid>.

-netdev user,id=<netid>: defines the network “user” device. This is a virtual local network with addresses 10.0.2.0/24, where the host has address 10.0.2.2 and acts as a gateway to internet, and with a name server at address 10.0.2.3, and an smb server at address 10.0.2.4. A builtin DHCP server can allocate addresses between 10.0.2.15 and 10.0.2.31.

-soundhw <model>: defines the soundcard model. The list may be obtained with -soundhw help.

-vga <type>: defines the type of VGA card to emulate. For -vga std, if you are building a Linux kernel for the guest, it's recommended to enable CONFIG_DRM_BOCHS (as a part of the kernel or a kernel module) to drive all the features of the emulated VGA card, and CONFIG_FB to display the Linux console on it. The other <type> values are not tested by the editors and may require additional dependencies.

-serial mon:stdio: sends the serial port of the guest (/dev/ttyS0 on linux guests), multiplexed with the qemu monitor, to the standard input and output of the qemu process.

-name <name>: sets the name of the guest. This name is displayed in the guest window caption. It may be useful if you run several guests at the same time.

-drive if=pflash,format=raw,readonly=on,file=/usr/share/qemu/edk2-x86_64-code.fd: Load a pre-built EDK2 UEFI firmware, instead of the default PC BIOS. Use this option if you want to boot the guest OS with UEFI.

-drive file=<filename>,if=virtio: Provide Virtio interface to the guest kernel for accessing the disk image, instead of simulating a real disk hardware. This can improve disk I/O performance, but it requires a Virtio driver in guest kernel. Use it instead of a plain -drive if the guest kernel supports Virtio. To build a Linux kernel with Virtio support for the guest, use make defconfig && make kvm_guest.config to create an initial kernel configuration with the Virtio drives enabled, then make your customization. And, if the guest kernel is Linux, the virtual disks using Virtio interface will be named vdx in the devtmpfs, instead of sdx.

-net nic,netdev=net0,model=virtio-net-pci: Provide Virtio interface to the guest kernel for accessing the network interface, instead of simulating a real network interface card. This can improve network I/O performance, but it requires a Virtio driver in guest kernel. Use it instead of a plain -net if the guest kernel supports Virtio.

Controlling the Emulated Display

To set the resolution of the emulated display for a Xorg server running in the guest Linux system, read the section called “Fine Tuning Display Settings”.

Networking

The above solution for networking allows the guest to access the local network through the host (and possibly to access internet through the local routers), but the converse is not true. Not even the host can access the guest, unless port forwarding is enabled. And in the case several guests are running, they cannot communicate with each other. Other network devices can be used for this purpose. For example, there is the “socket” device, which allows several guests to share a common virtual network. In the following, we describe in more details how to set up the “bridge” device, which allows the guests to appear as if connected to the local network. All the commands below should be run as the root user.

Set up bridging with bridge-utils-1.7.1. Only the physical interface(s) should be set up at boot. The virtual interface(s) will be added as needed when qemu is started.

Set up a required configuration file:

install -vdm 755 /etc/qemu &&
echo allow br0 > /etc/qemu/bridge.conf

In the qemu command line above, replace the switch -netdev user,... with -netdev bridge,....

Installed Programs: elf2dmp, qemu (symlink), qemu-edid, qemu-ga, qemu-img, qemu-io, qemu-keymap, qemu-nbd, qemu-pr-helper, qemu-storage-daemon, and qemu-system-<arch>

Installed Library: None

Installed Directories: /usr/share/qemu and /usr/share/doc/qemu-8.2.1 (optional)

Short Description

elf2dmp	Converts files from elf to dmp format
qemu-edid	is a test tool for the qemu EDID generator
qemu-ga	implements support for QMP (QEMU Monitor Protocol) commands and events that terminate and originate respectively within the guest using an agent built as part of QEMU
qemu-img	provides commands to manage QEMU disk images
qemu-io	is a diagnostic and manipulation program for (virtual) memory media. It is still at an early stage of development
qemu-keymap	generates qemu reverse keymaps from xkb keymaps, which can be used with the qemu "-k" command line switch
qemu-nbd	exports Qemu disk images using the QEMU Disk Network Block Device (NBD) protocol
qemu-pr-helper	Implements the persistent reservation helper for QEMU
qemu-storage-daemon	allows to modify disk images using the QEMU Monitor Protocol (QMP) without running a VM
qemu-system-x86_64	is the QEMU PC System emulator

Part III. General Libraries and Utilities

Chapter 9. General Libraries

Libraries contain code which is often required by more than one program. This has the advantage that each program doesn't need to duplicate code (and risk introducing bugs), it just has to call functions from the libraries installed on the system. The most obvious example of a set of libraries is Glibc which is installed during the LFS book. This contains all of the C library functions which programs use.

There are two types of libraries: static and shared. Shared libraries (usually libXXX.so) are loaded into memory from the shared copy at runtime (hence the name). Static libraries ( libXXX.a) are actually linked into the program executable file itself, thus making the program file larger. Quite often, you will find both static and shared copies of the same library on your system.

Generally, you only need to install libraries when you are installing software that needs the functionality they supply. In the BLFS book, each package is presented with a list of (known) dependencies. Thus, you can figure out which libraries you need to have before installing that program. If you are installing something without using BLFS instructions, usually the README or INSTALL file will contain details of the program's requirements.

There are certain libraries which nearly everyone will need at some point. In this chapter these and some others are listed and it is explained why you may want to install them.

AppStream-1.0.1

Introduction to AppStream

The AppStream package contains a library and tool that is useful for retrieving software metadata and making it easily accessible to programs which need it.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/appstream/releases/AppStream-1.0.1.tar.xz
Download MD5 sum: a1122ba2d3c41ba694f00844c84dddd7
Download size: 2.6 MB
Estimated disk space required: 34 MB
Estimated build time: 0.3 SBU (Using parallelism=4)

AppStream Dependencies

Required

cURL-8.6.0, elogind-252.9, itstool-2.0.7, libxml2-2.12.5, libxmlb-0.3.15, and libyaml-0.2.5

Optional

Gi-DocGen-2023.3, (Qt-5.15.12 or qt-alternate-5.15.12), Qt-6.6.2, DAPS, and libstemmer

Installation of AppStream

Install AppStream by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr       \
            --buildtype=release \
            -Dapidocs=false     \
            -Dstemming=false    .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install &&
mv -v /usr/share/doc/appstream{,-1.0.1}

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dapidocs=false: This switch disables building the API documentation. Remove it if you have Gi-DocGen-2023.3 installed and wish to regenerate the API documentation. When the API documentation is not regenerated, a pre-built copy is installed anyway.

-Dstemming=false: This switch disables stemming support. Remove this switch if you have libstemmer installed and want faster searches.

-Dqt5=true: Use this option if you have (Qt-5.15.12 or qt-alternate-5.15.12) installed and you want to build support for Qt-5 applications into this package.

-Dqt=true: Use this option if you have Qt-6.6.2 installed and you want to build support for Qt6 applications into this package. This option conflicts with -Dqt5=true.

Configuring AppStream

Config Files

/usr/share/metainfo/org.linuxfromscratch.lfs.xml

Configuration Information

AppStream expects an operating system metainfo file describing the GNU/Linux distribution. As the root user, create the file describing LFS:

install -vdm755 /usr/share/metainfo &&
cat > /usr/share/metainfo/org.linuxfromscratch.lfs.xml << EOF
<?xml version="1.0" encoding="UTF-8"?>
<component type="operating-system">
  <id>org.linuxfromscratch.lfs</id>
  <name>Linux From Scratch</name>
  <summary>A customized Linux system built entirely from source</summary>
  <description>
    <p>
      Linux From Scratch (LFS) is a project that provides you with
      step-by-step instructions for building your own customized Linux
      system entirely from source.
    </p>
  </description>
  <url type="homepage">https://www.linuxfromscratch.org/lfs/</url>
  <metadata_license>MIT</metadata_license>
  <developer id='linuxfromscratch.org'>
    <name>The Linux From Scratch Editors</name>
  </developer>

  <releases>
    <release version="12.2" type="development" date="2024-09-01">
      <description>
        <p>The next release of Linux From Scratch.</p>
      </description>
    </release>

    <release version="12.1" type="stable" date="2024-03-01">
      <description>
        <p>Now contains Binutils 2.42, GCC-13.2.0, Glibc-2.39, and Linux
        kernel 6.7.</p>
      </description>
    </release>
  </releases>
</component>
EOF

Installed Programs: appstreamcli

Installed Libraries: libappstream.so

Installed Directories: /usr/include/appstream, /usr/share/doc/appstream-12.1, and /usr/share/installed-tests/appstream

Short Descriptions

appstreamcli	queries information from AppStream metadata and from the AppStream component index
`libappstream.so`	contains functions that handle AppStream metadata queries and request information from the AppStream component index

Apr-1.7.4

Introduction to Apr

The Apache Portable Runtime (APR) is a supporting library for the Apache web server. It provides a set of application programming interfaces (APIs) that map to the underlying Operating System (OS). Where the OS doesn't support a particular function, APR will provide an emulation. Thus programmers can use the APR to make a program portable across different platforms.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://archive.apache.org/dist/apr/apr-1.7.4.tar.bz2
Download MD5 sum: f8a62f3984898ba0ea8b6f26b851cb99
Download size: 876 KB
Estimated disk space required: 11 MB (additional 4 MB for the tests)
Estimated build time: 0.1 SBU (add 1.4 SBU for tests)

Installation of Apr

Install Apr by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --with-installbuilddir=/usr/share/apr-1/build &&
make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: apr-1-config

Installed Library: libapr-1.so

Installed Directories: /usr/include/apr-1 and /usr/share/apr-1

Short Descriptions

apr-1-config	is a shell script used to retrieve information about the apr library in the system. It is typically used to compile and link against the library
`libapr-1.so`	is the Apache Portable Runtime library

Apr-Util-1.6.3

Introduction to Apr Util

The Apache Portable Runtime Utility Library provides a predictable and consistent interface to underlying client library interfaces. This application programming interface assures predictable if not identical behavior regardless of which libraries are available on a given platform.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://archive.apache.org/dist/apr/apr-util-1.6.3.tar.bz2
Download MD5 sum: b6e8c9b31d938fe5797ceb0d1ff2eb69
Download size: 423 KB
Estimated disk space required: 7.6 MB (add 1.4 MB for tests)
Estimated build time: less than 0.1 SBU (add 0.3 SBU for tests)

Apr Util Dependencies

Required

Apr-1.7.4

Optional

FreeTDS, MariaDB-10.11.7 or MySQL, OpenLDAP-2.6.7, PostgreSQL-16.2, SQLite-3.45.1, unixODBC-2.3.12, and Berkeley DB (deprecated)

Installation of Apr Util

Install Apr Util by running the following commands:

./configure --prefix=/usr       \
            --with-apr=/usr     \
            --with-gdbm=/usr    \
            --with-openssl=/usr \
            --with-crypto &&
make

To test the results, issue: make -j1 test. One test, testdbm, is known to fail.

Now, as the root user:

make install

Command Explanations

--with-gdbm=/usr: This switch enables the apr_dbm_gdbm-1.so plugin.

--with-openssl=/usr --with-crypto: These switches enable the apr_crypto_openssl-1.so plugin.

--with-berkeley-db=/usr: If you have installed Berkeley DB (deprecated), use this switch to compile the apr_dbm_db-1.so plugin.

--with-ldap: If you have installed OpenLDAP-2.6.7, use this switch to compile the apr_ldap.so plugin.

Installed Program: apu-1-config

Installed Library: libaprutil-1.so

Installed Directory: /usr/lib/apr-util-1

Short Descriptions

apu-1-config	is an APR-util script designed to allow easy command line access to APR-util configuration parameters
`libaprutil-1.so`	contains functions that provide a predictable and consistent interface to underlying client library interfaces

Aspell-0.60.8.1

Introduction to Aspell

The Aspell package contains an interactive spell checking program and the Aspell libraries. Aspell can either be used as a library or as an independent spell checker.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/aspell/aspell-0.60.8.1.tar.gz
Download MD5 sum: 187bd142f522ada555c7aa6b9cbf56e6
Download size: 3.4 MB
Estimated disk space required: 41 MB (Additional 8 MB for EN dictionary)
Estimated build time: 0.4 SBU

Additional Downloads

You'll need to download at least one dictionary. The English dictionary is given as an example below. Dictionaries in many other languages can be found at https://ftp.gnu.org/gnu/aspell/dict.

Aspell English dictionary: https://ftp.gnu.org/gnu/aspell/dict/en/aspell6-en-2020.12.07-0.tar.bz2

Aspell Dependencies

Required

Which-2.21 (for the dictionaries)

Installation of Aspell

Install Aspell by running the following commands:

./configure --prefix=/usr &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&
ln -svfn aspell-0.60 /usr/lib/aspell &&

install -v -m755 -d /usr/share/doc/aspell-0.60.8.1/aspell{,-dev}.html &&

install -v -m644 manual/aspell.html/* \
    /usr/share/doc/aspell-0.60.8.1/aspell.html &&

install -v -m644 manual/aspell-dev.html/* \
    /usr/share/doc/aspell-0.60.8.1/aspell-dev.html

If you do not plan to install Ispell, then copy the wrapper script ispell:

install -v -m 755 scripts/ispell /usr/bin/

If you do not plan to install Spell, then copy the wrapper script spell:

install -v -m 755 scripts/spell /usr/bin/

Command Explanations

ln -svfn aspell-0.60 /usr/lib/aspell: This command is useful for configuration of other applications, such as enchant-2.6.7.

Configuring Aspell

Configuration Information

After Aspell is installed, you must set up at least one dictionary. Install the English dictionary by running the following commands:

tar xf ../aspell6-en-2020.12.07-0.tar.bz2 &&
cd aspell6-en-2020.12.07-0                &&

./configure &&
make

Now, as the root user:

make install

Other dictionaries can be installed with the same instructions.

Installed Programs: aspell, aspell-import, precat, preunzip, prezip, prezip-bin, pspell-config, run-with-aspell, word-list-compress and optionally, ispell and spell.

Installed Libraries: libaspell.so and libpspell.so

Installed Directories: /usr/include/pspell and /usr/lib/aspell-0.60

Short Descriptions

aspell	is a utility that can function as an ispell -a replacement, as an independent spell checker, as a test utility to test out Aspell features, and as a utility for managing dictionaries
ispell	is a wrapper around aspell to invoke it in ispell compatible mode
spell	is a wrapper around aspell to invoke it in spell compatible mode
aspell-import	imports old personal dictionaries into Aspell
precat	decompresses a prezipped file to stdout
preunzip	decompresses a prezipped file
prezip	is a prefix delta compressor, used to compress sorted word lists or other similar text files
prezip-bin	is called by the various wrapper scripts to perform the actual compressing and decompressing
pspell-config	displays information about the `libpspell` installation, mostly for use in build scripts
run-with-aspell	is a script to help use Aspell as an ispell replacement
word-list-compress	compresses or decompresses sorted word lists for use with the Aspell spell checker
`libaspell.so`	contains spell checking API functions
`libpspell.so`	is an interface to the `libaspell` library. All the spell checking functionality is now in `libaspell` but this library is included for backward compatibility

Boost-1.84.0

Introduction to Boost

Boost provides a set of free peer-reviewed portable C++ source libraries. It includes libraries for linear algebra, pseudorandom number generation, multithreading, image processing, regular expressions and unit testing.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/boostorg/boost/releases/download/boost-1.84.0/boost-1.84.0.tar.xz
Download MD5 sum: 893b5203b862eb9bbd08553e24ff146a
Download size: 90 MB
Estimated disk space required: 1.1 GB (199 MB installed)
Estimated build time: 1.7 SBU (Using parallelism=4; add 0.1 SBU for tests)

Boost Dependencies

Optional

ICU-74.2 and Open MPI

Editor Notes: https://wiki.linuxfromscratch.org/blfs/wiki/boost

Installation of Boost

This package can be built with several jobs running in parallel. In the instructions below, <N> stands for the number of jobs. Install Boost by running the following commands:

./bootstrap.sh --prefix=/usr --with-python=python3 &&
./b2 stage -j<N> threading=multi link=shared

To run Boost.Build's regression tests, issue pushd tools/build/test; python3 test_all.py; popd. With python-3.11.x all 169 tests should pass. With Python-3.12.2, 7 tests fail for undetermined reasons.

To run every library's regression tests, issue pushd status; ../b2; popd. A few tests may fail. They take a very long time (over 119 SBU at -j4) and use a very large amount of disk space (46 GB). You should use the -jN switch to speed them up.

Note

Boost installs many versioned directories in /usr/lib/cmake. If a new version of Boost is installed over a previous version, the older cmake directories need to be explicitly removed. To do this, run as the root user:

rm -rf /usr/lib/cmake/[Bb]oost*

before installing the new version.

Now, as the root user:

./b2 install threading=multi link=shared

Command Explanations

threading=multi: This parameter ensures that Boost is built with multithreading support.

link=shared: This parameter ensures that only shared libraries are created, except for libboost_exception and libboost_test_exec_monitor which are created as static. Most people will not need the static libraries, and most programs using Boost only use the headers. Omit this parameter if you do need static libraries.

--with-python=python3: This switch ensures Python3 is used if Python2 is installed.

-jN: This switch may be added to the b2 command lines, to run up to N processes in parallel.

Installed Programs: None

Installed Libraries: libboost_atomic.so, libboost_chrono.so, libboost_container.so, libboost_context.so, libboost_contract.so, libboost_coroutine.so, libboost_date_time.so, libboost_exception.a, libboost_fiber.so, libboost_filesystem.so, libboost_graph.so, libboost_iostreams.so, libboost_json.so, libboost_locale.so, libboost_log_setup.so, libboost_log.so, libboost_math_c99.so, libboost_math_c99f.so, libboost_math_c99l.so, libboost_math_tr1.so, libboost_math_tr1f.so, libboost_math_tr1l.so, libboost_nowide.so, libboost_numpy312.so, libboost_prg_exec_monitor.so, libboost_program_options.so, libboost_python312.so, libboost_random.so, libboost_regex.so, libboost_serialization.so, libboost_stacktrace_addr2line.so, libboost_stacktrace_basic.so, libboost_stacktrace_noop.so, libboost_system.so, libboost_test_exec_monitor.a, libboost_thread.so, libboost_timer.so, libboost_type_erasure.so, libboost_unit_test_framework.so, libboost_url.so, libboost_wave.so, and libboost_wserialization.so

Installed Directory: /usr/include/boost

brotli-1.1.0

Introduction to Brotli

Brotli provides a general-purpose lossless compression algorithm that compresses data using a combination of a modern variant of the LZ77 algorithm, Huffman coding and 2nd order context modeling. Its libraries are particularly used for WOFF2 fonts on webpages.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/google/brotli/archive/v1.1.0/brotli-1.1.0.tar.gz
Download MD5 sum: 3a6a3dba82a3604792d3cb0bd41bca60
Download size: 500 KB
Estimated disk space required: 33 MB (with python3 bindings)
Estimated build time: 0.3 SBU (with python3 bindings; parallelism=4)

Brotli Dependencies

Required

Optional

pytest-8.0.0 (for testing Python3 bindings)

Installation of Brotli

Install brotli by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      ..  &&
make

To test the results, issue: make test.

Now, as the root user:

make install

If desired, build the Python3 bindings:

cd .. &&
sed "/c\/.*\.[ch]'/d;\
     /include_dirs=\[/\
     i libraries=['brotlicommon','brotlidec','brotlienc']," \
    -i setup.py &&
pip3 wheel -w dist --no-build-isolation --no-deps --no-cache-dir $PWD

Install the Python3 bindings as the root user:

pip3 install --no-index --find-links=dist --no-cache-dir --no-user Brotli

To test the Python3 binding, issue: pytest.

Command Explanations

sed ... -i setup.py: Stop setup.py from rebuilding the entire package all over again, use the already installed libraries for the Python3 binding instead.

Installed Programs: brotli

Installed Libraries: libbrotlicommon.so, libbrotlidec.so, and libbrotlienc.so

Installed Directories: /usr/include/brotli and /usr/lib/python3.12/site-packages/Brotli-1.1.0.dist-info (if you built and installed the Python3 bindings)

Short Descriptions

brotli	can compress or decompress files, or test the integrity of compressed files
`libbrotlicommon{-static.a,.so}`	is the Brotli common dictionary library
`libbrotlidec{-static.a,.so}`	is the Brotli decoder library
`libbrotlienc{-static.a,.so}`	is the Brotli common encoder library

CLucene-2.3.3.4

Introduction to CLucene

CLucene is a C++ version of Lucene, a high performance text search engine.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/clucene/clucene-core-2.3.3.4.tar.gz
Download MD5 sum: 48d647fbd8ef8889e5a7f422c1bfda94
Download size: 2.2 MB
Estimated disk space required: 78 MB
Estimated build time: 0.8 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/clucene-2.3.3.4-contribs_lib-1.patch

CLucene Dependencies

Required

Installation of CLucene

Install CLucene by running the following commands:

patch -Np1 -i ../clucene-2.3.3.4-contribs_lib-1.patch &&

sed -i '/Misc.h/a #include <ctime>' src/core/CLucene/document/DateTools.cpp &&

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DBUILD_CONTRIBS_LIB=ON .. &&
make

Now, as the root user:

make install

Command Explanations

-DBUILD_CONTRIBS_LIB=ON: This cmake variable enables building the CLucene contribs library necessary for running applications that use language specific text analyzers like LibreOffice for example.

Installed Programs: None

Installed Libraries: libclucene-contribs-lib.so, libclucene-core.so, and libclucene-shared.so

Installed Directories: /usr/include/CLucene and /usr/lib/CLuceneConfig.cmake

dbus-glib-0.112

Introduction to D-Bus GLib

The D-Bus GLib package contains GLib interfaces to the D-Bus API.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://dbus.freedesktop.org/releases/dbus-glib/dbus-glib-0.112.tar.gz
Download MD5 sum: 021e6c8a288df02c227e4aafbf7e7527
Download size: 700 KB
Estimated disk space required: 12 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

D-Bus GLib Dependencies

Required

dbus-1.14.10 and GLib-2.78.4

Optional

Installation of D-Bus GLib

Install D-Bus GLib by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --disable-static &&
make

To test the results, issue: make check. Note that more comprehensive tests can be run by following the same method used in D-Bus instructions, which requires building the package twice.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Program: dbus-binding-tool

Installed Library: libdbus-glib-1.so

Installed Directories: /usr/share/gtk-doc/html/dbus-glib

Short Descriptions

dbus-binding-tool	is a tool used to interface with the D-Bus API
`libdbus-glib-1.so`	contains GLib interface functions to the D-Bus API

Double-conversion-3.3.0

Introduction to Double-conversion

The Double-conversion package contains a library that facilitates binary-to-decimal and decimal-to-binary routines for IEEE doubles.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/google/double-conversion/archive/v3.3.0/double-conversion-3.3.0.tar.gz
Download MD5 sum: b344abb64084a4a1d98a43e67752989b
Download size: 6.7 MB
Estimated disk space required: 62 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Double-conversion Dependencies

Required

Installation of Double-conversion

Install Double-conversion by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DBUILD_SHARED_LIBS=ON      \
      -DBUILD_TESTING=ON          \
      ..                          &&
make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

-DBUILD_SHARED_LIBS=ON: This switch forces cmake to build a shared version of the library instead of the static version.

-DBUILD_TESTING=ON: This switch builds the test programs.

Installed Programs: None

Installed Libraries: libdouble-conversion.so

Installed Directories: /usr/include/double-conversion

Short Descriptions

libdouble-conversion.so

provides binary-to-decimal and decimal-to-binary routines for IEEE doubles

duktape-2.7.0

Introduction to duktape

duktape is an embeddable Javascript engine, with a focus on portability and compact footprint.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://duktape.org/duktape-2.7.0.tar.xz
Download MD5 sum: b3200b02ab80125b694bae887d7c1ca6
Download size: 1003 KB
Estimated disk space required: 25 MB
Estimated build time: 0.3 SBU

Installation of duktape

Install duktape by running the following commands:

sed -i 's/-Os/-O2/' Makefile.sharedlibrary
make -f Makefile.sharedlibrary INSTALL_PREFIX=/usr

Now, as the root user:

make -f Makefile.sharedlibrary INSTALL_PREFIX=/usr install

Installed Programs: None

Installed Libraries: libduktape.so and libduktaped.so

Installed Directories: None

Short Descriptions

libduktape.so

is an embeddable Javascript engine

enchant-2.6.7

Introduction to enchant

The enchant package provides a generic interface into various existing spell checking libraries.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/AbiWord/enchant/releases/download/v2.6.7/enchant-2.6.7.tar.gz
Download MD5 sum: 250e0b07d8dd80d9f2ed0046a6cc2933
Download size: 4.3 MB
Estimated disk space required: 19 MB (add 70 MB for tests)
Estimated build time: 0.1 SBU (add 0.7 SBU for tests)

enchant Dependencies

Required

Optional

dbus-glib-0.112, Doxygen-1.10.0, Hspell, Hunspell, Nuspell, Voikko, and unittest-cpp (required for tests)

Installation of enchant

Install enchant by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir /usr/share/doc/enchant-2.6.7 &&
make

To run tests, unittest-cpp must be installed and the --enable-relocatable option passed to configure above. If these conditions are present, the tests may be run with make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Configuring enchant

Config Files

~/.enchant and /usr/share/enchant/enchant.ordering

Configuration Information

You can test your installation and configuration by creating a test file and running the following commands (you can replace the en_GB dictionary by any other downloaded when installing Aspell-0.60.8.1):

cat > /tmp/test-enchant.txt << "EOF"
Tel me more abot linux
Ther ar so many commads
EOF

enchant-2 -d en_GB -l /tmp/test-enchant.txt &&
enchant-2 -d en_GB -a /tmp/test-enchant.txt

You will see a list of the misspelled words followed by a list of alternatives for them.

See more details in the enchant manual page.

Installed Programs: enchant-2 and enchant-lsmod-2

Installed Libraries: libenchant-2.so

Installed Directories: /usr/include/enchant-2, /usr/lib/enchant-2, /usr/share/enchant, and /usr/share/doc/enchant-2.6.7

Short Descriptions

enchant-2	is a spellchecker
enchant-lsmod-2	lists available backends, languages, and dictionaries
`libenchant-2.so`	contains spell checking interface API functions

Exempi-2.6.5

Introduction to Exempi

Exempi is an implementation of XMP (Adobe's Extensible Metadata Platform).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://libopenraw.freedesktop.org/download/exempi-2.6.5.tar.xz
Download MD5 sum: 51fe14c2a5fa44816ba8187c6ad87d78
Download size: 2.7 MB
Estimated disk space required: 289 MB (add 236 MB for tests)
Estimated build time: 0.4 SBU (add 0.6 SBU for tests; both using parallelism=4)

Exempi Dependencies

Required

Boost-1.84.0

Optional

Valgrind-3.22.0

Installation of Exempi

If you intend to run the regression tests, first remove a test that depends on an apparently proprietary Adobe SDK:

sed -i -r '/^\s?testadobesdk/d' exempi/Makefile.am &&
autoreconf -fiv

Install Exempi by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: exempi

Installed Library: libexempi.so

Installed Directory: /usr/include/exempi-2.0

Short Descriptions

exempi	is a command line tool to manipulate XMP metadata
`libexempi.so`	is a library used to parse XMP metadata

fftw-3.3.10

Introduction to fftw

FFTW is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data (as well as of even/odd data, i.e. the discrete cosine/sine transforms or DCT/DST).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.fftw.org/fftw-3.3.10.tar.gz
Download MD5 sum: 8ccbf6a5ea78a16dbc3e1306e234cc5c
Download size: 4.0 MB
Estimated disk space required: 59 MB
Estimated build time: 1.6 SBU (add 3.4 SBU for tests, both using parallelism=4)

Installation of fftw

Note

We build fftw three times for different libraries in different numerical precisions: the default double precision floating point, the older 32-bit (single precision) version named float which sacrifices precision for speed, and the long double which offers increased precision at the cost of slower execution.

The first build is for double precision arithmetic. Install fftw by running the following commands:

./configure --prefix=/usr    \
            --enable-shared  \
            --disable-static \
            --enable-threads \
            --enable-sse2    \
            --enable-avx     \
            --enable-avx2    &&
make

To test the results, issue: make check. On 32-bit systems, the tests can take substantially longer than they would on 64-bit machines.

Now, as the root user:

make install

Now build single precision:

make clean &&

./configure --prefix=/usr    \
            --enable-shared  \
            --disable-static \
            --enable-threads \
            --enable-sse2    \
            --enable-avx     \
            --enable-avx2    \
            --enable-float   &&
make

As the root user:

make install

Finally, build long double precision:

make clean &&

./configure --prefix=/usr    \
            --enable-shared  \
            --disable-static \
            --enable-threads \
            --enable-long-double &&
make

As the root user:

make install

Command Explanations

--enable-shared --disable-static: Use shared libs instead of static libs.

--enable-threads: This enables libfftw3_threads.so to be compiled. It is used by e.g. the gimp plugin from G'MIC.

--enable-{sse2,avx,avx2}: These enables building the optimized routines using SSE2, AVX, and AVX2 instructions. FFTW will check if these routines can be really used on the current CPU when the FFTW library is loaded, so a FFTW build with these routines enabled can still run on a CPU without SSE2, AVX, or AVX512. These options are not compatible with --enable-long-double.

--enable-float: This enables building the library that uses single precision floating point arithmetic. It is faster but less precise than the default double precision library. The library will be called libfftw3f.so needed by PulseAudio-17.0.

--enable-long-double: This enables building the library that uses higher precision long-double floating point arithmetic. The library will be called libfftw3l.so.

--enable-avx512: This enables building the optimized routines using AVX512F instructions. FFTW will check if these routines can be really used on the current CPU when the FFTW library is loaded, so a FFTW build with these routines enabled can still run on a CPU without AVX512F. Use this option if the FFTW build will be used on a CPU with AVX512F. This option is not compatible with --enable-long-double.

Installed Programs: fftw-wisdom and fftw-wisdom-to-conf

Installed Libraries: libfftw3.so, libfftw3_threads.so, libfftw3f.so, libfftw3f_threads.so, libfftw3l.so and libfftw3l_threads.so

Installed Directories: None

Short Descriptions

fftw-wisdom	is a utility to generate FFTW wisdom files, which contain saved information about how to optimally compute (Fourier) transforms of various sizes
fftw-wisdom-to-conf	is a utility to generate C configuration routines from FFTW wisdom files, where the latter contain saved information about how to optimally compute (Fourier) transforms of various sizes
`libfftw3.so`	is the Fast Fourier Transform library
`libfftw3_threads.so`	is the threaded Fast Fourier Transform library
`libfftw3f.so`	is the single-precision Fast Fourier Transform library, described as “float” for historic reasons
`libfftw3f_threads.so`	is the threaded single-precision Fast Fourier Transform library
`libfftw3l.so`	is the long double Fast Fourier Transform library
`libfftw3l_threads.so`	is the threaded long double Fast Fourier Transform library

fmt-10.2.1

Introduction to fmt

The fmt package is an open-source formatting library providing a fast and safe alternative to C stdio and C++ iostreams.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/fmtlib/fmt/archive/refs/tags/10.2.1/fmt-10.2.1.tar.gz
Download MD5 sum: dc09168c94f90ea890257995f2c497a5
Download size: 836 KB
Estimated disk space required: 4.5 MB (add 40 MB for tests)
Estimated build time: less than 0.1 SBU (add 0.2 SBU for tests)

Installation of fmt

Install fmt by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr     \
      -DCMAKE_INSTALL_LIBDIR=/usr/lib \
      -DBUILD_SHARED_LIBS=ON          \
      -DFMT_TEST=OFF                  \
      -G Ninja ..                     &&
ninja

If you have enabled tests, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

-DFMT_TEST=OFF: This switch initializes the package tests. Set to ON if you wish to run tests.

Installed Programs: None

Installed Libraries: libfmt.so

Installed Directories: /usr/include/fmt and /usr/lib/cmake/fmt

GLib-2.78.4

Introduction to GLib

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.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/glib/2.78/glib-2.78.4.tar.xz
Download MD5 sum: 0781e889cab64f1f7dbb6e8357c6a95f
Download size: 5.1 MB
Estimated disk space required: 130 MB (add 20 MB for tests)
Estimated build time: 0.8 SBU (add 0.5 SBU for tests; both using parallelism=4)

Additional Downloads

Optional patch: https://www.linuxfromscratch.org/patches/blfs/12.1/glib-skip_warnings-1.patch

GLib Dependencies

Optional

dbus-1.14.10 (for some tests), Fuse-3.16.2 and bindfs (both needed for one test), GDB-14.1 (for bindings), docbook-xml-4.5, docbook-xsl-nons-1.79.2, GTK-Doc-1.33.2 (to build API documentation), glib-networking-2.78.0 (for some tests, but this is a circular dependency), and sysprof

Additional Runtime Dependencies

gobject-introspection-1.78.1 (should be installed before gtk+, atk, etc.)

Quoted directly from the INSTALL file: “Some of the mimetype-related functionality in GIO requires the update-mime-database and update-desktop-database utilities”, which are part of shared-mime-info-2.4 and desktop-file-utils-0.27, respectively. These two utilities are also needed for some tests.

Installation of GLib

If desired, apply the optional patch. In many cases, applications that use this library, either directly or indirectly via other libraries such as GTK+-3.24.41, output numerous warnings when run from the command line. This patch enables the use of an environment variable, GLIB_LOG_LEVEL, that suppresses unwanted messages. The value of the variable is a digit that corresponds to:

1 Alert

2 Critical

3 Error

4 Warning

5 Notice

For instance export GLIB_LOG_LEVEL=4 will skip output of Warning and Notice messages (and Info/Debug messages if they are turned on). If GLIB_LOG_LEVEL is not defined, normal message output will not be affected.

patch -Np1 -i ../glib-skip_warnings-1.patch

Warning

If a previous version of glib is installed, move the headers out of the way so that later packages do not encounter conflicts:

if [ -e /usr/include/glib-2.0 ]; then
    rm -rf /usr/include/glib-2.0.old &&
    mv -vf /usr/include/glib-2.0{,.old}
fi

Install GLib by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Dman=true          &&
ninja

Note

If libxslt-1.1.39 is installed, the above command may indicate several (about 33) errors that start with "Error: no ID for constraint linkend:" when generating the man pages. These are harmless.

The GLib test suite requires desktop-file-utils for some tests. However, desktop-file-utils requires GLib in order to compile; therefore, you must first install GLib and then run the test suite.

Now, as the root user:

ninja install &&

mkdir -p /usr/share/doc/glib-2.78.4 &&
cp -r ../docs/reference/{gio,glib,gobject} /usr/share/doc/glib-2.78.4

You should now install desktop-file-utils-0.27 and shared-mime-info-2.4 and proceed to run the test suite.

Warning

Do not run the test suite as root or some tests will fail unexpectedly and leave some non-FHS-compliant directories in the /usr hierarchy.

To test the results, after having installed the package, issue: LC_ALL=C ninja test as a non-root user.

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dman=true: This switch causes the build to create and install the package man pages.

-Dgtk_doc=true: This switch causes the build to create and install the API documentation.

Installed Programs: gapplication, gdbus, gdbus-codegen, gio, gio-querymodules, glib-compile-resources, glib-compile-schemas, glib-genmarshal, glib-gettextize, glib-mkenums, gobject-query, gresource, gsettings, gtester, and gtester-report

Installed Libraries: libgio-2.0.so, libglib-2.0.so, libgmodule-2.0.so, libgobject-2.0.so, and libgthread-2.0.so

Installed Directories: /usr/include/gio-unix-2.0, /usr/include/glib-2.0, /usr/lib/gio, /usr/lib/glib-2.0, /usr/share/glib-2.0, /usr/share/doc/{glib-2.0,glib-2.78.4}, and /usr/share/gtk-doc/html/{gio,glib,gobject} (optional)

Short Descriptions

gapplication	can be used to start applications and to send messages to already-running instances of other applications
gdbus	is a simple tool used for working with D-Bus objects
gdbus-codegen	is used to generate code and/or documentation for one or more D-Bus interfaces
gio	is a utility that makes many GIO features available from the command line
gio-querymodules	is used to create a `giomodule.cache` file in the listed directories. This file lists the implemented extension points for each module that has been found
glib-compile-resources	is used to read the resource description from a file and the files that it references to create a binary resource bundle that is suitable for use with the GResource API
glib-compile-schemas	is used to compile all the GSettings XML schema files in a directory into a binary file with the name `gschemas.compiled` that can be used by GSettings
glib-genmarshal	is a C code marshaller generation utility for GLib closures
glib-gettextize	is a variant of the gettext internationalization utility
glib-mkenums	is a C language enum description generation utility
gobject-query	is a small utility that draws a tree of types
gresource	offers a simple command line interface to GResource
gsettings	offers a simple command line interface to GSettings
gtester	is a test running utility
gtester-report	is a test report formatting utility
GLib libraries	contain low-level core libraries for the GIMP Toolkit

GLibmm-2.66.5

Introduction to GLibmm

The GLibmm package is a set of C++ bindings for GLib.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/glibmm/2.66/glibmm-2.66.5.tar.xz
Download MD5 sum: b6c2c8ba36abf6c5e43cee459a74b8a1
Download size: 7.3 MB
Estimated disk space required: 80 MB (with tests)
Estimated build time: 0.5 SBU (Using parallelism=4; with tests)

GLibmm Dependencies

Required

GLib-2.78.4 and libsigc++-2.12.1

Optional

Doxygen-1.10.0, glib-networking-2.78.0 (for tests), GnuTLS-3.8.3 (for tests), libxslt-1.1.39, and mm-common

Installation of GLibmm

Install GLibmm by running the following commands:

mkdir bld &&
cd    bld &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Installed Programs: None

Installed Libraries: libgiomm-2.4.so, libglibmm-2.4.so and libglibmm_generate_extra_defs-2.4.so

Installed Directories: /usr/lib/g{io,lib}mm-2.4 and /usr/include/g{io,lib}mm-2.4

Short Descriptions

`libgiomm-2.4.so`	contains the GIO API classes
`libglibmm-2.4.so`	contains the GLib API classes

GMime-3.2.7

Introduction to GMime

The GMime package contains a set of utilities for parsing and creating messages using the Multipurpose Internet Mail Extension (MIME) as defined by the applicable RFCs. See the GMime web site for the RFCs resourced. This is useful as it provides an API which adheres to the MIME specification as closely as possible while also providing programmers with an extremely easy to use interface to the API functions.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/gmime/3.2/gmime-3.2.7.tar.xz
Download MD5 sum: 7ecd9aa75e0cd2e8668206b1d53df874
Download size: 2.1 MB
Estimated disk space required: 25 MB (with tests)
Estimated build time: 0.3 SBU (with tests)

GMime Dependencies

Required

GLib-2.78.4 and libgpg-error-1.47

Optional

DocBook-utils-0.6.14, GPGME-1.23.2, GTK-Doc-1.33.2, libnsl-2.0.1, Vala-0.56.14, and Gtk# (requires Mono)

Installation of GMime

Install GMime by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: None

Installed Library: libgmime-3.0.so

Installed Directories: /usr/include/gmime-3.0 and /usr/share/gtk-doc/html/gmime-3.0

Short Descriptions

libgmime-3.0.so

contains API functions used by programs that need to comply to the MIME standards

gobject-introspection-1.78.1

Introduction to GObject Introspection

The GObject Introspection is used to describe the program APIs and collect them in a uniform, machine readable format.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/gobject-introspection/1.78/gobject-introspection-1.78.1.tar.xz
Download MD5 sum: da2677e6b9c91b33c036d2233a96cec3
Download size: 1.0 MB
Estimated disk space required: 48 MB (with tests)
Estimated build time: 0.3 SBU (With tests; both using parallelism=4)

GObject Introspection Dependencies

Required

Optional

Cairo-1.18.0 (required for the tests), Gjs-1.78.4 (to satisfy one test), GTK-Doc-1.33.2, Mako-1.3.2, and Markdown-3.4.1

Installation of GObject Introspection

Install GObject Introspection by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, fix an incompatibility of the test suite with Python 3.12 or later and then run the test suite:

sed "/PYTHONPATH/a'/usr/lib/python3.12'," -i ../tests/warn/meson.build &&
ninja test

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dgtk_doc=true: Build and install the documentation.

Installed Program: g-ir-annotation-tool, g-ir-compiler, g-ir-doc-tool, g-ir-generate, g-ir-inspect, and g-ir-scanner

Installed Libraries: libgirepository-1.0.so and _giscanner.cpython-312-<arch>-linux-gnu.so

Installed Directories: /usr/include/gobject-introspection-1.0, /usr/lib/girepository-1.0, /usr/lib/gobject-introspection, /usr/share/gir-1.0, and /usr/share/gobject-introspection-1.0

Short Descriptions

g-ir-annotation-tool	creates or extracts annotation data from GI typelibs
g-ir-compiler	converts one or more GIR files into one or more typelib
g-ir-doc-tool	generates Mallard files that can be viewed with yelp or rendered to HTML with yelp-build from yelp-tools
g-ir-inspect	is a utility that gives information about a GI typelib
g-ir-generate	is a GIR generator that uses the repository API
g-ir-scanner	is a tool which generates GIR XML files by parsing headers and introspecting GObject based libraries
`libgirepository-1.0.so`	provides an API to access the typelib metadata

Gsl-2.7.1

Introduction to Gsl

The GNU Scientific Library (GSL) is a numerical library for C and C++ programmers. It provides a wide range of mathematical routines such as random number generators, special functions and least-squares fitting.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/gsl/gsl-2.7.1.tar.gz
Download MD5 sum: 36aee97e67f64dbdab7afae197e3483b
Download size: 7.2 MB
Estimated disk space required: 213 MB (with tests, without docs)
Estimated build time: 1.2 SBU (Using parallelism=4; with tests, without docs)

Gsl Dependencies

Optional

sphinx_rtd_theme-2.0.0

Installation of Gsl

Install Gsl by running the following commands:

./configure --prefix=/usr --disable-static &&
make

If you have sphinx_rtd_theme-2.0.0 installed, build the documentation with:

make html

To test the results, issue: make check.

Now, as the root user:

make install

If you built the documentation, install it (as root) with:

mkdir                   /usr/share/doc/gsl-2.7.1 &&
cp -R doc/_build/html/* /usr/share/doc/gsl-2.7.1

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: gsl-config, gsl-histogram, and gsl-randist

Installed Libraries: libgslcblas.so and libgsl.so

Installed Directory: /usr/include/gsl and /usr/share/doc/gsl-2.7.1

Short Descriptions

gsl-config	is a shell script to get the version number and compiler flags of the installed Gsl library
gsl-histogram	is a demonstration program for the GNU Scientific Library that computes a histogram from data taken from stdin
gsl-randist	is a demonstration program for the GNU Scientific Library that generates random samples from various distributions
`libgslcblas.so`	contains functions that implement a C interface to Basic Linear Algebra Subprograms
`libgsl.so`	contains functions that provide a collection of numerical routines for scientific computing

gspell-1.12.2

Introduction to gspell

The gspell package provides a flexible API to add spell checking to a GTK+ application.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/gspell/1.12/gspell-1.12.2.tar.xz
Download MD5 sum: f1e5f02695aee20ba543352889c28ff5
Download size: 436 KB
Estimated disk space required: 11 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

gspell Dependencies

Required

enchant-2.6.7, ICU-74.2, and GTK+-3.24.41

Optional

gobject-introspection-1.78.1, GTK-Doc-1.33.2, Vala-0.56.14, and Valgrind-3.22.0

Installation of gspell

Install gspell by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check. The tests must be run in an X session. One test, test-checker, is known to fail if the external package Hunspell is not installed.

Now, as the root user:

make install

The libtool archive file from this package is referring to the libraries from ICU-74.2. Such a reference may cause packages depending on this package to be unnecessary linked against the ICU libraries and increase the burden to rebuild packages if ICU is updated to a new major version. As we've explained in Libtool archive (.la) files, these libtool archive files are unneeded anyway. So as the root user, remove the libtool archive file now:

rm -v /usr/lib/libgspell-1.la

Installed Programs: gspell-app1

Installed Libraries: libgspell-1.so

Installed Directories: /usr/include/gspell-1 and /usr/share/gtk-doc/html/gspell-1.0

Short Descriptions

gspell-app1	checks the spelling of a text entered in a window
`libgspell-1.so`	is the gspell API library

ICU-74.2

Introduction to 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 the same results on all platforms.

Warning

Upgrading this package to a new major version (for example, from 72.1 to 74.2) will require rebuilding of many other packages. If some packages that use the libraries built by icu4c-74 are rebuilt, they will use the new libraries while current packages will use the previous libraries. If the Linux application loader (/usr/lib/ld-linux-x86-64.so.2) determines that both the old and new libraries are needed, and a symbol (name of data or function) exists in both versions of the library, all references to the symbol will be resolved to the version appearing earlier in the breadth-first sequence of the dependency graph. This may result in the application failing if the definition of the data or the behavior of the function referred by the symbol differs in two versions. To avoid the issue, users will need to rebuild every package linked to an ICU library as soon as possible once ICU is updated to a new major version.

To determine what external libraries are needed (directly or indirectly) by an application or a library, run:

ldd <application or library>

or to see only the directly needed libraries:

readelf -d  <application or library> | grep NEEDED

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/unicode-org/icu/releases/download/release-74-2/icu4c-74_2-src.tgz
Download MD5 sum: 94c0b370f43123ea92b146ebea9c709d
Download size: 25 MB
Estimated disk space required: 339 MB (add 42 MB for tests)
Estimated build time: 0.7 SBU (Using parallelism=4; add 1.5 SBU for tests)

ICU Dependencies

Optional

LLVM-17.0.6 (with Clang), and Doxygen-1.10.0 (for documentation)

Installation of ICU

Note

This package expands to the directory icu.

Note

If clang++ is available, it will be used in the mistaken belief that g++ might not support C++11, even though configure has tested for that. If using g++ there will be an unnecessary warning at the end of configure. Building with g++ also takes longer than the estimated SBU shown.

Install ICU by running the following commands:

cd source                                    &&

./configure --prefix=/usr                    &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Programs: derb, escapesrc, genbrk, genccode, gencfu, gencmn, gencnval, gendict, gennorm2, genrb, gensprep, icu-config, icuexportdata, icuinfo, icupkg, makeconv, pkgdata, and uconv

Installed Libraries: libicudata.so, libicui18n.so, libicuio.so, libicutest.so, libicutu.so, and libicuuc.so

Installed Directories: /usr/include/unicode, /usr/lib/icu, and /usr/share/icu

Short Descriptions

derb	disassembles a resource bundle
escapesrc	converts “\u” escaped characters into unicode characters
genbrk	compiles ICU break iteration rules source files into binary data files
genccode	generates C or platform specific assembly code from an ICU data file
gencfu	reads in Unicode confusable character definitions and writes out the binary data
gencmn	generates an ICU memory-mappable data file
gencnval	compiles the converter's aliases file
gendict	compiles word lists into ICU string trie dictionaries
gennorm2	builds binary data files with Unicode normalization data
genrb	compiles a resource bundle
gensprep	compiles StringPrep data from filtered RFC 3454 files
icu-config	outputs ICU build options
icuinfo	outputs configuration information about the current ICU
icupkg	extracts or modifies an ICU .dat archive
makeconv	compiles a converter table
pkgdata	packages data for use by ICU
uconv	converts data from one encoding to another
`libicudata.so`	is the data library
`libicui18n.so`	is the internationalization (i18n) library
`libicuio.so`	is the ICU I/O (unicode stdio) library
`libicutest.so`	is the test library
`libicutu.so`	is the tool utility library
`libicuuc.so`	is the common library

inih-58

Introduction to inih

This package is a simple .INI file parser written in C.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/benhoyt/inih/archive/r58/inih-r58.tar.gz
Download MD5 sum: 5c9725320ad2c79e0b1f76568bd0ff24
Download size: 20 KB
Estimated disk space required: 724 KB
Estimated build time: less than 0.1 SBU

Installation of inih

Install inih by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Installed Program: None

Installed Libraries: libinih.so, libINIReader.so

Installed Directories: None

Short Descriptions

`libinih.so`	is the inih main library
`libINIReader.so`	is the inih parser library

Intel-gmmlib-22.3.16

Introduction to Intel-gmmlib

The Intel-gmmlib package contains the Intel Graphics Memory Management Library, which provides device specific memory and buffer management functions for the Intel Media Driver for VAAPI and the Intel Graphics Computer Runtime for OpenCL (TM).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/intel/gmmlib/archive/refs/tags/intel-gmmlib-22.3.16.tar.gz
Download MD5 sum: 7d947d9fa06c101731ac4881857e056a
Download size: 828 KB
Estimated disk space required: 53 MB
Estimated build time: 0.5 SBU

Note

The tarball intel-gmmlib-22.3.16.tar.gz will extract to the directory gmmlib-intel-gmmlib-22.3.16.

Intel-gmmlib Dependencies

Required

Installation of Intel-gmmlib

Install Intel-gmmlib by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr   \
      -DBUILD_TYPE=Release          \
      -G Ninja                      \
      -Wno-dev ..                   &&
ninja

The test suite is normally run by ninja unless -DRUN_TEST_SUITE=NO is passed to cmake.

Now, as the root user:

ninja install

Installed Programs: None

Installed Libraries: libigdgmm.so

Installed Directories: /usr/include/igdgmm

Short Descriptions

libigdgmm.so

contains functions that provide Memory Management functions for Intel Graphics Drivers

Jansson-2.14

Introduction to Jansson

The Jansson package contains a library used to encode, decode, and manipulate JSON data.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/akheron/jansson/releases/download/v2.14/jansson-2.14.tar.bz2
Download MD5 sum: 3f90473d7d54ebd1cb6a2757396641df
Download size: 424 KB
Estimated disk space required: 5.6 MB (add 1.9 MB for tests)
Estimated build time: 0.1 SBU (with tests)

Installation of Jansson

First fix one of the tests:

sed -e "/DT/s;| sort;| sed 's/@@libjansson.*//' &;" \
    -i test/suites/api/check-exports

Install jansson by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Programs: None

Installed Library: libjansson.so

Installed Directories: None

Short Descriptions

libjansson.so

contains an API for encoding, decoding, and manipulating JSON data

JSON-C-0.17

Introduction to JSON-C

The JSON-C implements a reference counting object model that allows you to easily construct JSON objects in C, output them as JSON formatted strings and parse JSON formatted strings back into the C representation of JSON objects.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://s3.amazonaws.com/json-c_releases/releases/json-c-0.17.tar.gz
Download MD5 sum: bad8f5e91b7b2563ee2d507054c70eb2
Download size: 384 KB
Estimated disk space required: 7.9 MB
Estimated build time: 0.4 SBU (with tests)

JSON-C Dependencies

Required

Optional (for documentation)

Doxygen-1.10.0 and Graphviz-10.0.1 (for dot tool)

Installation of JSON-C

Install JSON-C by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      -DBUILD_STATIC_LIBS=OFF     \
      .. &&
make

If you have installed Doxygen-1.10.0 and Graphviz-10.0.1, you can build the documentation by running the following command:

doxygen doc/Doxyfile

To test the results, issue: make test.

Now, as the root user:

make install

If you built the documentation, install it by running the following commands as the root user:

install -d -vm755 /usr/share/doc/json-c-0.17 &&
install -v -m644 doc/html/* /usr/share/doc/json-c-0.17

Command Explanations

-DCMAKE_BUILD_TYPE=Release: This switch is used to apply a higher level of compiler optimizations.

Installed Programs: None

Installed Libraries: libjson-c.so

Installed Directories: /usr/include/json-c

Short Descriptions

libjson-c.so

contains the JSON-C API functions

JSON-GLib-1.8.0

Introduction to JSON GLib

The JSON GLib package is a library providing serialization and deserialization support for the JavaScript Object Notation (JSON) format described by RFC 4627.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/json-glib/1.8/json-glib-1.8.0.tar.xz
Download MD5 sum: f1aac2b8a17fd68646653cc4d8426486
Download size: 156 KB
Estimated disk space required: 7.8 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

JSON-GLib Dependencies

Required

Optional (Required if building GNOME)

Optional

Installation of JSON GLib

Install JSON GLib by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dgtk_doc=disabled: Add this option if you have GTK-Doc-1.33.2 installed and do not wish to generate the API documentation.

Installed Programs: json-glib-format and json-glib-validate

Installed Library: libjson-glib-1.0.so

Installed Directories: /usr/{include,{libexec,share{/installed-tests}/json-glib-1.0 and /usr/share/gtk-doc/html/json-glib

Short Descriptions

json-glib-format	is a simple command line interface to format JSON data
json-glib-validate	is a simple command line interface to validate JSON data
`libjson-glib-1.0.so`	contains the JSON GLib API functions

keyutils-1.6.3

Introduction to keyutils

Keyutils is a set of utilities for managing the key retention facility in the kernel, which can be used by filesystems, block devices and more to gain and retain the authorization and encryption keys required to perform secure operations.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/snapshot/keyutils-1.6.3.tar.gz
Download MD5 sum: 6b70b2b381c1b6d9adfaf66d5d3e7c00
Download size: 136 KB
Estimated disk space required: 2.6 MB (with tests)
Estimated build time: less than 0.1 SBU (add 0.4 SBU for tests)

Keyutils Dependencies

Optional

lsb-tools-0.12 (referred by the test suite)

Kernel Configuration

If running the test suite, some tests needs the following kernel features enabled:

Security options --->
  [*] Enable access key retention support                                 [KEYS]
  [*]   Large payload keys                                            [BIG_KEYS]
  [*]   Diffie-Hellman operations on retained keys           [KEY_DH_OPERATIONS]

-*- Cryptographic API --->                                              [CRYPTO]
  Public-key cryptography --->
    <*/M> RSA (Rivest-Shamir-Adleman)                               [CRYPTO_RSA]
  [*] Asymmetric (public-key cryptographic) key type --->  [ASYMMETRIC_KEY_TYPE]
    <*> Asymmetric public-key crypto algorithm subtype
                                            ...  [ASYMMETRIC_PUBLIC_KEY_SUBTYPE]
    # If not built into the kernel, [SYSTEM_TRUSTED_KEYRING] won't show up;
    # building as a module won't work:
    <*>   X.509 certificate parser                     [X509_CERTIFICATE_PARSER]
  Certificates for signature checking --->
    [*] Provide system-wide ring of trusted keys        [SYSTEM_TRUSTED_KEYRING]
    [*]   Provide a keyring to which extra trustable keys may be added
                                                ...  [SECONDARY_TRUSTED_KEYRING]
    [*] Provide system-wide ring of blacklisted keys  [SYSTEM_BLACKLIST_KEYRING]

Library routines --->
  Crypto library routines --->
    # If not built into the kernel, [BIG_KEYS] won't show up;
    # building as a module won't work:
    <*> ChaCha20-Poly1305 AEAD support (8-byte nonce library version)
                                              ...  [CRYPTO_LIB_CHACHA20POLY1305]

Installation of keyutils

Install keyutils by running the following commands:

make

Now, as the root user:

make NO_ARLIB=1 LIBDIR=/usr/lib BINDIR=/usr/bin SBINDIR=/usr/sbin install

The test suite can only run after installing this package. To test the results, issue, as the root user:

make -k test

If lsb-tools-0.12 is not installed, the test suite will output some lines complaining the lsb_release command not available but it won't affect the test result. One test named TRY ADDING ASYMMETRIC KEYS is known to fail due to the removal of the support for SHA1 with RSA signature algorithm from Linux kernel version 6.7 or newer.

Command Explanations

NO_ARLIB=1: This make flag disables installing the static library.

Configuring keyutils

Config Files

/etc/request-key.conf and /etc/request-key.d/*

Installed Programs: keyctl, key.dns_resolver, and request-key

Installed Library: libkeyutils.so

Installed Directory: /etc/keyutils, /etc/request-key.d, and /usr/share/keyutils

Short Descriptions

keyctl	controls the key management facility with a variety of subcommands
key.dns_resolver	is invoked by request-key on behalf of the kernel when kernel services (such as NFS, CIFS and AFS) need to perform a hostname lookup and the kernel does not have the key cached. It is not ordinarily intended to be called directly
request-key	is invoked by the kernel when the kernel is asked for a key that it doesn't have immediately available. The kernel creates a temporary key and then calls out to this program to instantiate it. It is not intended to be called directly
`libkeyutils.so`	contains the keyutils library API instantiation

libaio-0.3.113

Introduction to libaio

The libaio package is an asynchronous I/O facility ("async I/O", or "aio") that has a richer API and capability set than the simple POSIX async I/O facility. This library, libaio, provides the Linux-native API for async I/O. The POSIX async I/O facility requires this library in order to provide kernel-accelerated async I/O capabilities, as do applications which require the Linux-native async I/O API.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://pagure.io/libaio/archive/libaio-0.3.113/libaio-0.3.113.tar.gz
Download MD5 sum: 605237f35de238dfacc83bcae406d95d
Download size: 48 KB
Estimated disk space required: 1.0 MB
Estimated build time: less than 0.1 SBU

Installation of libaio

First, disable the installation of the static library:

sed -i '/install.*libaio.a/s/^/#/' src/Makefile

Build libaio by running the following command:

make

To test the results, issue: make partcheck.

Now, install the package as the root user:

make install

Installed Programs: None

Installed Library: libaio.so

Installed Directories: None

Short Descriptions

libaio.so

is the libaio library

libarchive-3.7.2

Introduction to libarchive

The libarchive library provides a single interface for reading/writing various compression formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libarchive/libarchive/releases/download/v3.7.2/libarchive-3.7.2.tar.xz
Download MD5 sum: 4f4ef6a17c7b0b484aa2c95aa6deefac
Download size: 5.0 MB
Estimated disk space required: 42 MB (add 34 MB for tests)
Estimated build time: 0.3 SBU (add 0.7 SBU for tests)

libarchive Dependencies

Optional

libxml2-2.12.5, LZO-2.10, and Nettle-3.9.1

Installation of libarchive

Install libarchive by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: LC_ALL=C make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--without-xml2: This switch sets expat for xar archive format support instead of preferred libxml2 if both packages are installed.

--without-nettle: This switch sets OpenSSL for crypto support instead of preferred Nettle if both packages are installed.

Installed Programs: bsdcat, bsdcpio, bsdtar, and bsdunzip

Installed Libraries: libarchive.so

Installed Directories: None

Short Descriptions

bsdcat	expands files to standard output
bsdcpio	is a tool similar to cpio
bsdtar	is a tool similar to GNU tar
bsdunzip	is a tool similar to Info-ZIP unzip
`libarchive.so`	is a library that can create and read several streaming archive formats

libassuan-2.5.6

Introduction to libassuan

The libassuan package contains an inter process communication library used by some of the other GnuPG related packages. libassuan's primary use is to allow a client to interact with a non-persistent server. libassuan is not, however, limited to use with GnuPG servers and clients. It was designed to be flexible enough to meet the demands of many transaction based environments with non-persistent servers.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/libassuan/libassuan-2.5.6.tar.bz2
Download MD5 sum: 9c22e76168675ec996b9d620ffbb7b27
Download size: 564 KB
Estimated disk space required: 7.9 MB (with tests, add 3.4 MB for documentation)
Estimated build time: 0.1 SBU (with tests and documentation)

libassuan Dependencies

Required

libgpg-error-1.47

Optional

texlive-20230313 (or install-tl-unx)

Installation of libassuan

Install libassuan by running the following commands:

./configure --prefix=/usr &&
make                      &&

make -C doc html                                                       &&
makeinfo --html --no-split -o doc/assuan_nochunks.html doc/assuan.texi &&
makeinfo --plaintext       -o doc/assuan.txt           doc/assuan.texi

The above commands build the documentation in html and plaintext formats. If you wish to build alternate formats of the documentation, you must have texlive-20230313 installed and issue the following commands:

make -C doc pdf ps

To test the results, issue: make check.

Now, as the root user:

make install &&

install -v -dm755   /usr/share/doc/libassuan-2.5.6/html &&
install -v -m644 doc/assuan.html/* \
                    /usr/share/doc/libassuan-2.5.6/html &&
install -v -m644 doc/assuan_nochunks.html \
                    /usr/share/doc/libassuan-2.5.6      &&
install -v -m644 doc/assuan.{txt,texi} \
                    /usr/share/doc/libassuan-2.5.6

If you built alternate formats of the documentation, install them by running the following commands as the root user:

install -v -m644  doc/assuan.{pdf,ps,dvi} \
                  /usr/share/doc/libassuan-2.5.6

Installed Program: libassuan-config

Installed Library: libassuan.so

Installed Directory: /usr/share/doc/libassuan-2.5.6

Short Descriptions

libassuan-config	is a `libassuan` build information script
`libassuan.so`	is an inter process communication library which implements the Assuan protocol

libatasmart-0.19

Introduction to libatasmart

The libatasmart package is a disk reporting library. It only supports a subset of the ATA S.M.A.R.T. functionality.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://0pointer.de/public/libatasmart-0.19.tar.xz
Download MD5 sum: 53afe2b155c36f658e121fe6def33e77
Download size: 248 KB
Estimated disk space required: 3 MB
Estimated build time: less than 0.1 SBU

Editor Notes: https://wiki.linuxfromscratch.org/blfs/wiki/libatasmart

Installation of libatasmart

Install libatasmart by running the following commands:

./configure --prefix=/usr --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make docdir=/usr/share/doc/libatasmart-0.19 install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: skdump and sktest

Installed Library: libatasmart.so

Installed Directory: /usr/share/doc/libatasmart-0.19

Short Descriptions

skdump	is a utility that reports on the status of the disk
sktest	is a utility to issue disks tests
`libatasmart.so`	contains the ATA S.M.A.R.T API functions

libatomic_ops-7.8.2

Introduction to libatomic_ops

libatomic_ops provides implementations for atomic memory update operations on a number of architectures. This allows direct use of these in reasonably portable code. Unlike earlier similar packages, this one explicitly considers memory barrier semantics, and allows the construction of code that involves minimum overhead across a variety of architectures.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/ivmai/libatomic_ops/releases/download/v7.8.2/libatomic_ops-7.8.2.tar.gz
Download MD5 sum: d07b3d8369d7f9efdca59f7501dd1117
Download size: 516 KB
Estimated disk space required: 6.8 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Installation of libatomic_ops

Install libatomic_ops by running the following commands:

./configure --prefix=/usr    \
            --enable-shared  \
            --disable-static \
            --docdir=/usr/share/doc/libatomic_ops-7.8.2 &&
make

To check the results, issue make check.

Now, as the root user:

make install

Command Explanations

--enable-shared: This switch enables building of the libatomic_ops shared libraries.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: libatomic_ops.so and libatomic_ops_gpl.so

Installed Directory: /usr/include/libatomic_ops and /usr/share/doc/libatomic_ops-7.8.2

Short Descriptions

libatomic_ops.so

contains functions for atomic memory operations

libblockdev-3.1.0

Introduction to libblockdev

libblockdev is a C library supporting GObject Introspection for manipulation of block devices. It has a plugin-based architecture where each technology (like LVM, Btrfs, MD RAID, Swap,...) is implemented in a separate plugin, possibly with multiple implementations (e.g. using LVM CLI or the new LVM DBus API).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/storaged-project/libblockdev/releases/download/3.1.0-1/libblockdev-3.1.0.tar.gz
Download MD5 sum: 033f2098a13f9dae6105d0337470efd3
Download size: 1.0 MB
Estimated disk space required: 13 MB
Estimated build time: 0.1 SBU

libblockdev Dependencies

Required

Optional

btrfs-progs-6.7.1, GTK-Doc-1.33.2, mdadm-4.2, parted-3.6, volume_key, ndctl, and targetcli (for tests)

Installation of libblockdev

Install libblockdev by running the following commands:

./configure --prefix=/usr      \
            --sysconfdir=/etc  \
            --with-python3     \
            --without-escrow   \
            --without-gtk-doc  \
            --without-lvm      \
            --without-lvm_dbus \
            --without-nvdimm   \
            --without-tools    &&
make

The test suite requires targetcli, which is not a part of BLFS.

Now, as the root user:

make install

Command Explanations

--without-escrow: This switch allows building libblockdev without volume_key installed.

--without-lvm --without-lvm_dbus --without-tools: The combination of these switches allows building libblockdev without parted-3.6 installed. Remove it if you've installed parted-3.6 and wish to build the lvm-cache-stats or vfat-resize utilities, or wish libblockdev to support logical volumes.

--without-btrfs --without-mdraid --without-tools: The combination of these switches allows building libblockdev without libbytesize-2.10 installed. The --without-mdraid option will break UDisks-2.10.1, so don't use it unless you really know what you are doing.

--without-crypto: This switch allows building libblockdev without cryptsetup-2.7.0 or keyutils-1.6.3 installed. This switch will break UDisks-2.10.1, so don't use it unless you really know what you are doing.

--without-dm --without-lvm --without-lvm_dbus --without-mpath: The combination of these switches allows building libblockdev without LVM2-2.03.23 installed. The --without-dm and --without-mpath options are not in the instructions provided by the book because LVM2-2.03.23 is required for cryptsetup-2.7.0 and cryptsetup-2.7.0 is a recommended dependency of libblockdev anyway.

--without-nvme: This switch allows building libblockdev without libnvme-1.8 installed. This switch will break UDisks-2.10.1, so don't use it unless you really know what you are doing.

Installed Programs: lvm-cache-stats and vfat-resize (both optional)

Installed Libraries: libbd_btrfs.so, libbd_crypto.so, libbd_dm.so, libbd_fs.so, libbd_loop.so, libbd_lvm.so (optional), libbd_lvm-dbus.so (optional), libbd_mdraid.so, libbd_mpath.so, libbd_nvme.so, libbd_part.so, libbd_swap.so, libbd_utils.so, and libblockdev.so

Installed Directories: /etc/libblockdev, /usr/include/blockdev, and /usr/share/gtk-doc/html/libblockdev (optional)

Short Descriptions

lvm-cache-stats	prints statistics on caches on LVM Logical Volumes
vfat-resize	resizes `vfat` file systems

libbytesize-2.10

Introduction to libbytesize

The libbytesize package is a library which facilitates the common operations with sizes in bytes.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/storaged-project/libbytesize/releases/download/2.10/libbytesize-2.10.tar.gz
Download MD5 sum: 2ed2ad2e44c4017f016e1ca55be83e62
Download size: 452 KB
Estimated disk space required: 3.5 MB
Estimated build time: less than 0.1 SBU (including tests)

libbytesize Dependencies

Required

pcre2-10.42 and Pygments-2.17.2

Optional

GTK-Doc-1.33.2, pocketlint (python module for one test), and polib (python module for one test)

Installation of libbytesize

Install libbytesize by running the following commands:

./configure --prefix=/usr &&
make

If you have the optional python modules installed, the regression tests can be run with: make check.

Now, as the root user:

make install

Installed Programs: bscalc

Installed Library: libbytesize.so

Installed Directories: /usr/include/bytesize and /usr/lib/python3.12/site-packages/bytesize

Short Descriptions

bscalc	converts from a larger unit, such as MB or TB, back to a value in bytes
`libbytesize.so`	contains functions used to handle common read/write operations with sizes in bytes

libcloudproviders-0.3.5

Introduction to libcloudproviders

The libcloudproviders package contains a library which provides a DBus API that allows cloud storage sync clients to expose their services.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libcloudproviders/0.3/libcloudproviders-0.3.5.tar.xz
Download MD5 sum: bdb46d0e8222df79eeff4043cd9933b2
Download size: 24 KB
Estimated disk space required: 1.5 MB
Estimated build time: less than 0.1 SBU

libcloudproviders Dependencies

Required

gobject-introspection-1.78.1 and Vala-0.56.14

Optional

Installation of libcloudproviders

Install libcloudproviders by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Denable-gtk-doc: Use this switch if you have GTK-Doc-1.33.2 installed and wish to generate the API documentation.

Installed Programs: None

Installed Libraries: libcloudproviders.so

Installed Directories: /usr/include/cloudproviders

Short Descriptions

libcloudproviders.so

contains functions that provide a DBus API to allow cloud storage sync clients to expose their services

libdaemon-0.14

Introduction to libdaemon

The libdaemon package is a lightweight C library that eases the writing of UNIX daemons.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://0pointer.de/lennart/projects/libdaemon/libdaemon-0.14.tar.gz
Download MD5 sum: 509dc27107c21bcd9fbf2f95f5669563
Download size: 332 KB
Estimated disk space required: 3 MB
Estimated build time: 0.1 SBU

libdaemon Dependencies

Optional

Doxygen-1.10.0 and Lynx-2.8.9rel.1

Installation of libdaemon

Install libdaemon by running the following commands:

./configure --prefix=/usr --disable-static &&
make

If you have Doxygen installed and wish to build the API documentation, issue the following command:

make -C doc doxygen

This package does not come with a test suite.

Now, as the root user:

make docdir=/usr/share/doc/libdaemon-0.14 install

If you built the API documentation, install it using the following commands as the root user:

install -v -m755 -d /usr/share/doc/libdaemon-0.14/reference/html &&
install -v -m644 doc/reference/html/* /usr/share/doc/libdaemon-0.14/reference/html &&
install -v -m644 doc/reference/man/man3/* /usr/share/man/man3

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libdaemon.so

Installed Directories: /usr/include/libdaemon and /usr/share/doc/libdaemon-0.14

Short Descriptions

libdaemon.so

contains the libdaemon API functions

libgcrypt-1.10.3

Introduction to libgcrypt

The libgcrypt package contains a general purpose crypto library based on the code used in GnuPG. The library provides a high level interface to cryptographic building blocks using an extendable and flexible API.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.10.3.tar.bz2
Download MD5 sum: a8cada0b343e10dbee51c9e92d856a94
Download size: 3.6 MB
Estimated disk space required: 131 MB (with tests)
Estimated build time: 0.3 SBU (with documentation; add 0.4 SBU for tests)

libgcrypt Dependencies

Required

libgpg-error-1.47

Optional

texlive-20230313 (or install-tl-unx)

Installation of libgcrypt

Install libgcrypt by running the following commands:

./configure --prefix=/usr &&
make                      &&

make -C doc html                                                       &&
makeinfo --html --no-split -o doc/gcrypt_nochunks.html doc/gcrypt.texi &&
makeinfo --plaintext       -o doc/gcrypt.txt           doc/gcrypt.texi

To test the results, issue: make check.

Now, as the root user:

make install &&
install -v -dm755   /usr/share/doc/libgcrypt-1.10.3 &&
install -v -m644    README doc/{README.apichanges,fips*,libgcrypt*} \
                    /usr/share/doc/libgcrypt-1.10.3 &&

install -v -dm755   /usr/share/doc/libgcrypt-1.10.3/html &&
install -v -m644 doc/gcrypt.html/* \
                    /usr/share/doc/libgcrypt-1.10.3/html &&
install -v -m644 doc/gcrypt_nochunks.html \
                    /usr/share/doc/libgcrypt-1.10.3      &&
install -v -m644 doc/gcrypt.{txt,texi} \
                    /usr/share/doc/libgcrypt-1.10.3

Command Explanations

--with-capabilities: This option enables libcap2 support. Note that this breaks cryptsetup-2.7.0

Installed Programs: dumpsexp, hmac256, libgcrypt-config, and mpicalc

Installed Library: libgcrypt.so

Installed Directory: /usr/share/doc/libgcrypt-1.10.3

Short Descriptions

dumpsexp	is a debug tool for S-expressions
hmac256	is a standalone HMAC-SHA-256 implementation used to compute an HMAC-SHA-256 authentication code
libgcrypt-config	determines the compile and linker flags that should be used to compile and link programs that use `libgcrypt`
mpicalc	is a RPN (Reverse Polish Notation) calculator
`libgcrypt.so`	contains the cryptographic API functions

libgpg-error-1.47

Introduction to libgpg-error

The libgpg-error package contains a library that defines common error values for all GnuPG components.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.47.tar.bz2
Download MD5 sum: 58e054ca192a77226c4822bbee1b7fdb
Download size: 1.0 MB
Estimated disk space required: 11 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Installation of libgpg-error

Install libgpg-error by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install &&
install -v -m644 -D README /usr/share/doc/libgpg-error-1.47/README

Installed Programs: gpg-error, gpgrt-config, and yat2m

Installed Library: libgpg-error.so

Installed Directories: /usr/share/common-lisp/source/gpg-error, /usr/share/libgpg-error, and /usr/share/doc/libgpg-error-1.47

Short Descriptions

gpg-error	is used to determine libgpg-error error codes
gpgrt-config	is a pkg-config style tool for querying the information about installed version of libgpg-error
yat2m	extracts man pages from a Texinfo source
`libgpg-error.so`	contains the libgpg-error API functions

libgrss-0.7.0

Introduction to libgrss

The libgrss package contains a library designed to manipulate RSS and Atom feeds.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libgrss/0.7/libgrss-0.7.0.tar.xz
Download MD5 sum: 7c0ee46a82dc0e9610183fe9ef8c7c1d
Download size: 356 KB
Estimated disk space required: 10 MB
Estimated build time: 0.1 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/libgrss-0.7.0-bugfixes-2.patch

libgrss Dependencies

Required

libsoup-2.74.3

Installation of libgrss

Install libgrss by running the following commands:

patch -Np1 -i ../libgrss-0.7.0-bugfixes-2.patch &&
autoreconf -fv &&
./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: None

Installed Library: libgrss.so

Installed Directories: /usr/include/libgrss and /usr/share/doc/libgrss-0.7.0

Short Descriptions

libgrss.so

provides API functions for handling RSS feeds

libgsf-1.14.52

Introduction to libgsf

The libgsf package contains a library used for providing an extensible input/output abstraction layer for structured file formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libgsf/1.14/libgsf-1.14.52.tar.xz
Download MD5 sum: c64b4a29dd2e67749313f3917a12a709
Download size: 692 KB
Estimated disk space required: 14 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libgsf Dependencies

Required

GLib-2.78.4 and libxml2-2.12.5

Optional

gobject-introspection-1.78.1, GTK-Doc-1.33.2, and Valgrind-3.22.0 (for tests)

Installation of libgsf

Install libgsf by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: gsf, gsf-office-thumbnailer, and gsf-vba-dump

Installed Library: libgsf-1.so

Installed Directories: /usr/include/libgsf-1, /usr/share/gtk-doc/html/gsf and /usr/share/thumbnailers

Short Descriptions

gsf	is a simple archive utility, somewhat similar to tar(1)
gsf-office-thumbnailer	is used internally by GNOME applications such as Nautilus to generate thumbnails of several types of office application files
gsf-vba-dump	is used to extract Visual Basic for Applications macros from files
`libgsf-1.so`	contains the libgsf API functions

libgudev-238

Introduction to libgudev

The libgudev package contains GObject bindings for libudev.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libgudev/238/libgudev-238.tar.xz
Download MD5 sum: 46da30a1c69101c3a13fa660d9ab7b73
Download size: 32 KB
Estimated disk space required: 2.0 MB
Estimated build time: less than 0.1 SBU

Required

Optional

gobject-introspection-1.78.1 (for gir-data, needed for GNOME), GTK-Doc-1.33.2, and umockdev-0.17.18 (for testing)

Installation of libgudev

Install libgudev by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dgtk_doc=true: Use this option if GTK-Doc is installed and you wish to build and install the API documentation.

Installed Program: None

Installed Libraries: libgudev-1.0.so

Installed Directories: /usr/include/gudev-1.0 and /usr/share/gtk-doc/html/gudev

Short Descriptions

libgudev-1.0.so

is a GObject-based wrapper library for libudev

libgusb-0.4.8

Introduction to libgusb

The libgusb package contains the GObject wrappers for libusb-1.0 that makes it easy to do asynchronous control, bulk and interrupt transfers with proper cancellation and integration into a mainloop.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/hughsie/libgusb/releases/download/0.4.8/libgusb-0.4.8.tar.xz
Download MD5 sum: edc0715ded0b886c063189deef94c754
Download size: 52 KB
Estimated disk space required: 2.1 MB (with tests and docs)
Estimated build time: 0.1 SBU (with tests and docs)

libgusb Dependencies

Required

JSON-GLib-1.8.0 and libusb-1.0.27

Optional

Gi-DocGen-2023.3 and umockdev-0.17.18 (for full test coverage)

Installation of libgusb

Install libgusb by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Ddocs=false        &&
ninja

If you have Gi-DocGen-2023.3 installed and wish to build the API documentation for this package, issue:

sed -E "/output|install_dir/s/('libgusb)'/\1-0.4.8'/" \
    -i ../docs/meson.build                            &&
meson configure -Ddocs=true                           &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Ddocs=false: Allow building this package without Gi-DocGen-2023.3 installed. If you have Gi-DocGen-2023.3 installed and you wish to rebuild and install the API documentation, a meson configure command will reset this option.

Installed Programs: gusbcmd

Installed Library: libgusb.so

Installed Directories: /usr/include/gusb-1 and /usr/share/doc/libgusb-0.4.8 (if gi-docgen is used)

Short Descriptions

gusbcmd	is a debugging tool for the libgusb library
`libgusb.so`	contains the libgusb API functions

libical-3.0.17

Introduction to libical

The libical package contains an implementation of the iCalendar protocols and data formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libical/libical/releases/download/v3.0.17/libical-3.0.17.tar.gz
Download MD5 sum: aab3e2c80a5a61c744204675bff19ae0
Download size: 888 KB
Estimated disk space required: 38 MB (with tests and API documentation)
Estimated build time: 0.4 SBU (with tests and documentation)

libical Dependencies

Required

Optional

Doxygen-1.10.0 (for the API documentation), Graphviz-10.0.1 (for the API documentation), GTK-Doc-1.33.2 (for the API documentation), ICU-74.2, PyGObject-3.46.0 (for some tests), and Berkeley DB (deprecated)

Installation of libical

Install libical by running the following commands:

Note

This package may occasionally fail when building with multiple processors. See Using Multiple Processors for more information.

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr  \
      -DCMAKE_BUILD_TYPE=Release   \
      -DSHARED_ONLY=yes            \
      -DICAL_BUILD_DOCS=false      \
      -DGOBJECT_INTROSPECTION=true \
      -DICAL_GLIB_VAPI=true        \
      .. &&
make -j1

If you have Doxygen-1.10.0, Graphviz-10.0.1, and GTK-Doc-1.33.2 installed and wish to build the API documentation, you should remove the -DICAL_BUILD_DOCS=false switch and issue:

make docs

To test the results, issue: make test.

Now, as the root user:

make install

If you have built the API documentation, install by issuing, as root user:

install -vdm755 /usr/share/doc/libical-3.0.17/html &&
cp -vr apidocs/html/* /usr/share/doc/libical-3.0.17/html

Command Explanations

-DCMAKE_BUILD_TYPE=Release: This switch is used to apply higher level of the compiler optimizations.

-DSHARED_ONLY=yes: This switch is used in order to only build the shared libraries.

-DICAL_BUILD_DOCS=false: This switch prevents building the GTK documentation. Remove if you want to build the documentation.

-DGOBJECT_INTROSPECTION=true: This switch is used to generate GObject metadata bindings.

-DICAL_GLIB_VAPI=true: This switch is used in order to build bindings for Vala-0.56.14.

-DUSE_BUILTIN_TZDATA=yes: This switch is used in order to build using your own timezone data.

Installed Programs: None

Installed Libraries: libical_cxx.so, libical.so, libical-glib.so, libicalss_cxx.so, libicalss.so, and libicalvcal.so

Installed Directory: /usr/include/libical, /usr/include/libical-glib, /usr/lib/cmake/LibIcal, /usr/libexec/libical, /usr/share/gtk-doc/html/libical-glib (optional), and /usr/share/doc/libical-3.0.17/html

Short Descriptions

`libical.so`	contains the libical API functions
`libical_cxx.so`	contains the libical C++ bindings
`libical-glib.so`	contains the libical glib bindings
`libicalss.so`	is a library that allows you to store iCal component data to disk in a variety of ways
`libicalss_cxx.so`	contains the libicalss C++ bindings
`libicalvcal.so`	is a vCard/vCalendar C interface

libidn-1.42

Introduction to libidn

libidn is a package designed for internationalized string handling based on the Stringprep, Punycode and IDNA specifications defined by the Internet Engineering Task Force (IETF) Internationalized Domain Names (IDN) working group, used for internationalized domain names. This is useful for converting data from the system's native representation into UTF-8, transforming Unicode strings into ASCII strings, allowing applications to use certain ASCII name labels (beginning with a special prefix) to represent non-ASCII name labels, and converting entire domain names to and from the ASCII Compatible Encoding (ACE) form.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/libidn/libidn-1.42.tar.gz
Download MD5 sum: fe061a95ae23979150a692d102dce4ad
Download size: 2.5 MB
Estimated disk space required: 19 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libidn Dependencies

Optional

Emacs-29.2, GTK-Doc-1.33.2, OpenJDK-21.0.2, Valgrind-3.22.0, and Mono

Installation of libidn

Install libidn by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, run:

pushd tests  &&
  make check &&
popd

Now, as the root user:

make install &&

find doc -name "Makefile*" -delete            &&
rm -rf -v doc/{gdoc,idn.1,stamp-vti,man,texi} &&
mkdir -v       /usr/share/doc/libidn-1.42     &&
cp -r -v doc/* /usr/share/doc/libidn-1.42

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

--enable-java: Use this switch to enable building the Java implementation of libidn. Note that OpenJDK-21.0.2 must be installed to use this option.

Installed Program: idn

Installed Library: libidn.so

Installed Directories: /usr/share/doc/libidn-1.42 and /usr/share/gtk-doc/html/libidn

Short Descriptions

idn

is a command line interface to the internationalized domain name library

libidn.so

contains a generic Stringprep implementation that does Unicode 3.2 NFKC normalization, mapping and prohibition of characters, and bidirectional character handling. Profiles for Nameprep, iSCSI, SASL and XMPP are included as well as support for Punycode and ASCII Compatible Encoding (ACE) via IDNA. A mechanism to define Top-Level Domain (TLD) specific validation tables, and to compare strings against those tables, as well as default tables for some TLDs are included

libidn2-2.3.7

Introduction to libidn2

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.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/libidn/libidn2-2.3.7.tar.gz
Download MD5 sum: de2818c7dea718a4f264f463f595596b
Download size: 2.1 MB
Estimated disk space required: 21 MB (add 3 MB for tests)
Estimated build time: 0.1 SBU (add 0.6 SBU for tests)

libidn2 Dependencies

Optional

git-2.44.0 and GTK-Doc-1.33.2

Installation of libidn2

Install libidn2 by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Program: idn2

Installed Library: libidn2.so

Installed Directory: /usr/share/gtk-doc/html/libidn2

Short Descriptions

idn2	is a command line interface to the internationalized domain library
`libidn2.so`	contains a generic Stringprep implementation used for internationalized string handling

libiodbc-3.52.15

Introduction to libiodbc

libiodbc is an API to ODBC compatible databases.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/iodbc/libiodbc-3.52.15.tar.gz
Download MD5 sum: 89949a41e542bb1b880d7fcc4987dad2
Download size: 1.0 MB
Estimated disk space required: 26 MB
Estimated build time: 0.2 SBU

libiodbc Dependencies

Installation of libiodbc

Install libiodbc by running the following commands:

./configure --prefix=/usr                   \
            --with-iodbc-inidir=/etc/iodbc  \
            --includedir=/usr/include/iodbc \
            --disable-libodbc               \
            --disable-static                &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--with-iodbc-inidir=/etc/iodbc: libiodbc will install configuration files in this directory.

--includedir=/usr/include/iodbc: This installs the interface headers to a private directory to avoid a conflict with headers installed by unixODBC.

--disable-libodbc: This prevents the installation of the libodbc.so symbolic link to avoid a conflict with unixODBC.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: iodbc-config, iodbctest, iodbctestw, and iodbcadm-gtk

Installed Libraries: libdrvproxy.so, libiodbc.so, libiodbcinst.so, and libiodbcadm.so

Installed Directory: /usr/include/iodbc, /usr/share/libiodbc, and /etc/iodbc

Short Descriptions

iodbc-config	is a utility for retrieving the installation options of libiodbc
iodbctest{,w}	are interactive SQL processors
iodbcadm-gtk	is a graphical administration utility

libksba-1.6.5

Introduction to Libksba

The Libksba package contains a library used to make X.509 certificates as well as making the CMS (Cryptographic Message Syntax) easily accessible by other applications. Both specifications are building blocks of S/MIME and TLS. The library does not rely on another cryptographic library but provides hooks for easy integration with Libgcrypt.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/libksba/libksba-1.6.5.tar.bz2
Download MD5 sum: 57b88e5d24c8705d9a3ba3832140d188
Download size: 692 KB
Estimated disk space required: 9.4 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Libksba Dependencies

Required

libgpg-error-1.47

Optional

Valgrind-3.22.0

Installation of Libksba

Install Libksba by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Program: None

Installed Library: libksba.so

Installed Directory: None

Short Descriptions

libksba.{so,a}

contains the cryptographic API functions

liblinear-247

Introduction to liblinear

This package provides a library for learning linear classifiers for large scale applications. It supports Support Vector Machines (SVM) with L2 and L1 loss, logistic regression, multi class classification and also Linear Programming Machines (L1-regularized SVMs). Its computational complexity scales linearly with the number of training examples making it one of the fastest SVM solvers around.

This package is known to build and work properly using an LFS 12.1 platform.

Note

After updating this package from liblinear-1.96 or earlier, you need to reinstall Nmap-7.94, in order to link to the new library.

Package Information

Download (HTTP): https://github.com/cjlin1/liblinear/archive/v247/liblinear-247.tar.gz
Download MD5 sum: 0c81dd2b2cabc4fba85f61b9dc51c4a3
Download size: 560 KB
Estimated disk space required: 1.6 MB
Estimated build time: less than 0.1 SBU

Installation of liblinear

Install liblinear by running the following commands:

make lib

This package does not come with a test suite.

Now, as the root user:

install -vm644 linear.h /usr/include &&
install -vm755 liblinear.so.5 /usr/lib &&
ln -sfv liblinear.so.5 /usr/lib/liblinear.so

Installed Programs: None

Installed Library: liblinear.so

Installed Directories: None

Short Descriptions

liblinear.so

is a large linear classification library

libmbim-1.26.4

Introduction to libmbim

The libmbim package contains a GLib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/libmbim/libmbim-1.26.4.tar.xz
Download MD5 sum: 58dea20cad346f31d2873b68385a9973
Download size: 553 KB
Estimated disk space required: 33 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libmbim Dependencies

Optional

GTK-Doc-1.33.2 and help2man

Installation of libmbim

Install libmbim by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: mbimcli and mbim-network

Installed Libraries: libmbim-glib.so

Installed Directories: /usr/include/libmbim-glib and /usr/share/gtk-doc/html/libmbim-glib

Short Descriptions

mbimcli	is an utility used to control MBIM devices
mbim-network	is an utility used for simple network management of MBIM devices
`libmbim-glib.so`	contains API functions for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol

libnvme-1.8

Introduction to libnvme

The libnvme package is a library which provides type definitions for NVMe specification structures, enumerations, and bit fields, helper functions to construct, dispatch, and decode commands and payloads, and utilities to connect, scan, and manage NVMe devices on a Linux system.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/linux-nvme/libnvme/archive/refs/tags/v1.8/libnvme-1.8.tar.gz
Download MD5 sum: ff72b83dc2ada1da0bd528570154eed3
Download size: 616 KB
Estimated disk space required: 13 MB
Estimated build time: 0.1 SBU (including tests)

libnvme Dependencies

Optional

dbus-1.14.10, JSON-C-0.17, keyutils-1.6.3, and SWIG-4.2.0

Installation of libnvme

Install libnvme by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release -Dlibdbus=auto .. &&
ninja

To run the tests, issue: ninja test.

Now, as the root user:

ninja install

Installed Programs: None

Installed Library: libnvme.so and libnvme-mi.so

Installed Directories: /usr/include/nvme and /usr/lib/python3.11/site-packages/libnvme

Short Descriptions

libnvme.so

contains functions used to handle operations relating to NVMe devices.

libpaper-2.1.3

Introduction to libpaper

This package is intended to provide a simple way for applications to take actions based on a system or user-specified paper size.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/rrthomas/libpaper/releases/download/v2.1.3/libpaper-2.1.3.tar.gz
Download MD5 sum: dc9cdf541173d7737ee73963f3052c7a
Download size: 1.2 MB
Estimated disk space required: 11 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Installation of libpaper

Install libpaper by running the following commands:

./configure --prefix=/usr        \
            --sysconfdir=/etc    \
            --disable-static     \
            --enable-relocatable \
            --docdir=/usr/share/doc/libpaper-2.1.3 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-relocatable: This switch is needed to run the tests.

Configuring libpaper

Configuration Information

The paper size is automatically determined from the system locale; see LC_PAPER in locale(7). If you want to override it, create a papersize file in the user configuration directory. For example:

mkdir -pv ~/.config &&
echo "a4" > ~/.config/papersize

If you want to override the paper size globally (for all users), set up the PAPERSIZE environment variable. For example:

echo "PAPERSIZE=a4" > /etc/profile.d/libpaper.sh

You may use a different paper size, such as “letter”.

Installed Programs: paper and paperconf

Installed Library: libpaper.so

Installed Directories: /usr/share/doc/libpaper-2.1.3

Short Descriptions

paper	prints paper configuration information
paperconf	prints paper configuration information in a compatibility mode
`libpaper.so`	contains functions for interrogating the paper library

libportal-0.7.1

Introduction to libportal

The libportal package provides a library that contains GIO-style async APIs for most Flatpak portals.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/flatpak/libportal/releases/download/0.7.1/libportal-0.7.1.tar.xz
Download MD5 sum: f94be41e8495ae7d6aaed046481daa61
Download size: 76 KB
Estimated disk space required: 3.0 MB (with tests)
Estimated build time: 0.1 SBU (add 0.3 SBU for tests)

Additional Downloads

Optional patch (required for running the test suite): https://www.linuxfromscratch.org/patches/blfs/12.1/libportal-0.7.1-testsuite_fix-1.patch

libportal Dependencies

Required

Recommended (Runtime)

To make this package really useful, install xdg-desktop-portal-1.18.2, xdg-desktop-portal-gtk-1.15.1, xdg-desktop-portal-gnome-45.1 (if running a GNOME desktop environment), and xdg-desktop-portal-lxqt-0.5.0 (if running a LXQt desktop environment). They are not needed if only using this package to satisfy a build dependency.

Optional

Gi-DocGen-2023.3 (for documentation), dbusmock-0.30.2 and pytest-8.0.0 (for testing), (Qt-5.15.12 or qt-alternate-5.15.12) (for the Qt5 version of libportal), and Vala-0.56.14

Installation of libportal

Warning

If a previous version of libportal is installed, move the headers out of the way so that later packages do not encounter conflicts (as the root user):

if [ -e /usr/include/libportal ]; then
    rm -rf /usr/include/libportal.old &&
    mv -vf /usr/include/libportal{,.old}
fi

If running the test suite, apply a patch to fix a dozen of test failures with python-dbusmock 0.30.0 or later:

patch -Np1 -i ../libportal-0.7.1-testsuite_fix-1.patch

Install libportal by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release -Ddocs=false .. &&
ninja

If you have Gi-DocGen-2023.3 installed and wish to build the API documentation for this package, issue:

sed "/output/s/-1/-0.7.1/" -i ../doc/meson.build &&
meson configure -Ddocs=true                    &&
ninja

To test the results, issue: ninja test. Note that additional dbus-daemon processes may need to be killed after the tests are run.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: None

Installed Libraries: libportal.so, libportal-gtk3.so, libportal-gtk4.so, and libportal-qt5.so

Installed Directories: /usr/include/libportal and /usr/share/gtk-doc/html/libportal

Short Descriptions

`libportal.so`	provides GIO-style async APIs for most Flatpak portals
`libportal-gtk3.so`	provides GTK+-3 specific functions for interacting with Flatpak portals
`libportal-gtk4.so`	provides GTK-4 specific functions for interacting with Flatpak portals
`libportal-qt5.so`	provides Qt5 specific functions for interacting with Flatpak portals

libptytty-2.0

Introduction to libptytty

The libptytty package provides a library that allows for OS independent and secure pty/tty and utmp/wtmp/lastlog handling.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://dist.schmorp.de/libptytty/libptytty-2.0.tar.gz
Download MD5 sum: 2a7f3f3c0d3ef71902da745dc7959529
Download size: 48 KB
Estimated disk space required: 1.4 MB
Estimated build time: less than 0.1 SBU

libptytty Dependencies

Required

Installation of libptytty

Install libptytty by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr     \
      -DCMAKE_BUILD_TYPE=Release      \
      -DPT_UTMP_FILE:STRING=/run/utmp \
      .. &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: None

Installed Libraries: libptytty.so

Installed Directories: None

Short Descriptions

libptytty.so

provides for OS independent and secure pty/tty and utmp/wtmp/lastlog handling

libqalculate-4.9.0

Introduction to libqalculate

The libqalculate package contains a library that provides functions for a multi-purpose calculator.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/Qalculate/libqalculate/releases/download/v4.9.0/libqalculate-4.9.0.tar.gz
Download MD5 sum: c129774b53e2bf1f0488214c99c7171a
Download size: 2.5 MB
Estimated disk space required: 139 MB (with tests)
Estimated build time: 0.8 SBU (With tests; both using parallelism=4)

libqalculate Dependencies

Required

cURL-8.6.0, ICU-74.2, and libxml2-2.12.5

Optional

Doxygen-1.10.0 and gnuplot

Installation of libqalculate

Install libqalculate by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir=/usr/share/doc/libqalculate-4.9.0 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

rm -v /usr/lib/libqalculate.la

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: qalc

Installed Library: libqalculate.so

Installed Directories: /usr/include/libqalculate, /usr/share/doc/libqalculate-4.9.0, and /usr/share/qalculate

Short Descriptions

qalc	is a powerful and easy to use command line calculator
`libqalculate.so`	contains the libqalculate API functions

libqmi-1.30.8

Introduction to libqmi

The libqmi package contains a GLib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/libqmi/libqmi-1.30.8.tar.xz
Download MD5 sum: 5ec8838914f80e1dfa4d2fa8cc2f186d
Download size: 1.2 MB
Estimated disk space required: 151 MB (with tests)
Estimated build time: 0.3 SBU (Using parallelism=4; with tests)

libqmi Dependencies

Required

GLib-2.78.4 and libgudev-238

Optional

GTK-Doc-1.33.2, help2man, and libqrtr-glib

Installation of libqmi

Install libqmi by running the following commands:

PYTHON=python3 ./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

--disable-mbim-qmux: This switch disables support for using a MBIM control device for QMI messages. Use this switch if you did not install libmbim.

Installed Programs: qmicli, qmi-firmware-update, and qmi-network

Installed Libraries: libqmi-glib.so

Installed Directories: /usr/include/libqmi-glib and /usr/share/gtk-doc/html/libqmi-glib

Short Descriptions

qmicli	is an utility used to control QMI devices
qmi-firmware-update	is an utility used to perform firmware updates on QMI devices
qmi-network	is an utility used for simple network management of QMI devices
`libqmi-glib.so`	contains API functions for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol

libseccomp-2.5.5

Introduction to libseccomp

The libseccomp package provides an easy to use and platform independent interface to the Linux kernel's syscall filtering mechanism.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/seccomp/libseccomp/releases/download/v2.5.5/libseccomp-2.5.5.tar.gz
Download MD5 sum: c27a5e43cae1e89e6ebfedeea734c9b4
Download size: 628 KB
Estimated disk space required: 7.1 MB (additional 4.7 MB for tests)
Estimated build time: less than 0.1 SBU (additional 2.9 SBU for tests)

libseccomp Dependencies

Optional

Which-2.21 (needed for tests), Valgrind-3.22.0, and LCOV

Installation of libseccomp

Install libseccomp by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: scmp_sys_resolver

Installed Library: libseccomp.so

Installed Directories: None

Short Descriptions

scmp_sys_resolver	is used to resolve system calls for applications
`libseccomp.so`	contains API functions for translating syscalls

libsigc++-2.12.1

Introduction to libsigc++

The libsigc++ package implements a typesafe callback system for standard C++.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libsigc++/2.12/libsigc++-2.12.1.tar.xz
Download MD5 sum: 891f1b2dbaebd8007eda8c639bbe1149
Download size: 4.8 MB
Estimated disk space required: 27 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libsigc++ Dependencies

Optional

DocBook-utils-0.6.14, docbook-xml-5.0, Doxygen-1.10.0, and mm-common

Installation of libsigc++

Install libsigc++ by running the following commands:

mkdir bld &&
cd    bld &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

-Dbuild-documentation=true: Use this switch if Doxygen-1.10.0 is installed and you wish to build and install the API documentation.

Installed Programs: None

Installed Library: libsigc-2.0.so

Installed Directories: /usr/{include,lib}/sigc++-2.0 and /usr/share/{devhelp/books,doc}/libsigc++-2.0 (if the documentation is enabled)

Short Descriptions

libsigc-2.0.so

contains the libsigc++ API functions

libsigsegv-2.14

Introduction to libsigsegv

libsigsegv is a library for handling page faults in user mode. A page fault occurs when a program tries to access to a region of memory that is currently not available. Catching and handling a page fault is a useful technique for implementing pageable virtual memory, memory-mapped access to persistent databases, generational garbage collectors, stack overflow handlers, and distributed shared memory.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/libsigsegv/libsigsegv-2.14.tar.gz
Download MD5 sum: 63a2b35f11b2fbccc3d82f9e6c6afd58
Download size: 456 KB
Estimated disk space required: 3.6 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

Installation of libsigsegv

Install libsigsegv by running the following commands:

./configure --prefix=/usr   \
            --enable-shared \
            --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-shared: This switch ensures that shared libraries are compiled.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libsigsegv.so

Installed Directories: None

Short Descriptions

libsigsegv.so

is a library for handling page faults in user mode

libssh2-1.11.0

Introduction to libssh2

Libssh2 package is a client-side C library implementing the SSH2 protocol.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.libssh2.org/download/libssh2-1.11.0.tar.gz
Download MD5 sum: a01d543fd891ca48fe47726540d50b17
Download size: 1.1 MB
Estimated disk space required: 13 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/libssh2-1.11.0-security_fixes-1.patch

libssh2 Dependencies

Optional

CMake-3.28.3 (can be used instead of the configure script), libgcrypt-1.10.3 (can be used instead of OpenSSL), OpenSSH-9.6p1 (for some tests), and Docker (for some tests)

Installation of libssh2

First, fix a critical security vulnerability in libssh2:

patch -Np1 -i ../libssh2-1.11.0-security_fixes-1.patch

If you want to test the package, exclude the tests requiring a static library:

sed -E '/^DOCKER_TEST/,/^SSHD_TEST/s/test_(auth_keyboard_info.* |hostkey |simple)/$(NOTHING)/' \
    -i tests/Makefile.inc &&
autoreconf -fi

Install libssh2 by running the following commands:

./configure --prefix=/usr          \
            --disable-docker-tests \
            --disable-static       &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-docker-tests: Disable the tests requiring Docker, which is beyond the scope of BLFS. Remove this switch if you've installed Docker and you wish to run the test suite.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libssh2.so

Installed Directories: None

Short Descriptions

libssh2.so

contains functions to use the SSH2 protocol

libstatgrab-0.92.1

Introduction to libstatgrab

This is a library that provides cross platform access to statistics about the system on which it's run. It's written in C and presents a selection of useful interfaces which can be used to access key system statistics. The current list of statistics includes CPU usage, memory utilisation, disk usage, process counts, network traffic, disk I/O, and more.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.mirrorservice.org/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.92.1.tar.gz
Download MD5 sum: af685494e985229e0ac46365bc0cd50e
Download size: 800 KB
Estimated disk space required: 7.6 MB (with tests)
Estimated build time: 0.1 SBU (add 1.5 SBU for tests)

libstatgrab Dependencies

Optional

log4cplus-2.1.1

Installation of libstatgrab

Install libstatgrab by running the following commands:

./configure --prefix=/usr   \
            --disable-static \
            --docdir=/usr/share/doc/libstatgrab-0.92.1 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: saidar, statgrab, statgrab-make-mrtg-config, and statgrab-make-mrtg-index

Installed Library: libstatgrab.so

Installed Directories: /usr/share/doc/libstatgrab-0.92.1

Short Descriptions

saidar	is a curses-based tool for viewing system statistics
statgrab	is a sysctl-style interface to system statistics
statgrab-make-mrtg-config	generates MRTG configuration
statgrab-make-mrtg-index	generates an XHTML index page from MRTG configuration files or stdin
`libstatgrab.so`	contains the libstatgrab API functions

libtasn1-4.19.0

Introduction to libtasn1

libtasn1 is a highly portable C library that encodes and decodes DER/BER data following an ASN.1 schema.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/libtasn1/libtasn1-4.19.0.tar.gz
Download MD5 sum: f701ab57eb8e7d9c105b2cd5d809b29a
Download size: 1.7 MB
Estimated disk space required: 17 MB (with tests)
Estimated build time: 0.8 SBU (with tests)

libtasn1 Dependencies

Optional

GTK-Doc-1.33.2 and Valgrind-3.22.0

Installation of libtasn1

Install libtasn1 by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

If you did not pass the --enable-gtk-doc parameter to the configure script, you can install the API documentation using the following command as the root user:

make -C doc/reference install-data-local

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: This parameter is normally used if GTK-Doc is installed and you wish to rebuild and install the API documentation. It is broken for this package due to the use of a long deprecated gtk-doc program that is no longer available.

Installed Programs: asn1Coding, asn1Decoding and asn1Parser

Installed Library: libtasn1.so

Installed Directory: /usr/share/gtk-doc/html/libtasn1

Short Descriptions

asn1Coding	is an ASN.1 DER encoder
asn1Decoding	is an ASN.1 DER decoder
asn1Parser	is an ASN.1 syntax tree generator for libtasn1
`libtasn1.so`	is a library for Abstract Syntax Notation One (ASN.1) and Distinguish Encoding Rules (DER) manipulation

libunistring-1.1

Introduction to libunistring

libunistring is a library that provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/libunistring/libunistring-1.1.tar.xz
Download MD5 sum: 0dfba19989ae06b8e7a49a7cd18472a1
Download size: 2.3 MB
Estimated disk space required: 51 MB (add 56 MB for tests)
Estimated build time: 0.4 SBU (Using parallelism=4; add 1.0 SBU for tests)

libunistring Dependencies

Optional

texlive-20230313 (or install-tl-unx) (to rebuild the documentation)

Installation of libunistring

Install libunistring by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir=/usr/share/doc/libunistring-1.1 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: libunistring.so

Installed Directory: /usr/include/unistring and /usr/share/doc/libunistring-1.1

Short Descriptions

libunistring.so

provides the unicode string library API

libunwind-1.6.2

Introduction to libunwind

The libunwind package contains a portable and efficient C programming interface (API) to determine the call-chain of a program. The API additionally provides the means to manipulate the preserved (callee-saved) state of each call-frame and to resume execution at any point in the call-chain (non-local goto). The API supports both local (same-process) and remote (across-process) operation.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.savannah.nongnu.org/releases/libunwind/libunwind-1.6.2.tar.gz
Download MD5 sum: f625b6a98ac1976116c71708a73dc44a
Download size: 884 KB
Estimated disk space required: 20 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libunwind Dependencies

Optional

texlive-20230313 (for latex2man)

Installation of libunwind

Install libunwind by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check. Two tests, run-coredump-unwind and run-coredump-unwind-mdi are known to fail.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: libunwind.so, libunwind-coredump.so, libunwind-generic.so, libunwind-ptrace.so, libunwind-setjmp.so, and libunwind-x86_64.so (libunwind-x86.so on i686)

Installed Directories: None

liburcu-0.14.0

Introduction to liburcu

The userspace-rcu package provides a set of userspace RCU (read-copy-update) libraries. These data synchronization libraries provide read-side access which scales linearly with the number of cores. It does so by allowing multiples copies of a given data structure to live at the same time, and by monitoring the data structure accesses to detect grace periods after which memory reclamation is possible.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://lttng.org/files/urcu/userspace-rcu-0.14.0.tar.bz2
Download MD5 sum: 0cd5647788b048a5d6bbdb3b08d46299
Download size: 648 KB
Estimated disk space required: 25 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Installation of liburcu

Install liburcu by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir=/usr/share/doc/liburcu-0.14.0 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Programs: None

Installed Libraries: liburcu.so, liburcu-bp.so, liburcu-cds.so, liburcu-common.so, liburcu-mb.so, liburcu-memb.so, liburcu-qsbr.so, and liburcu-signal.so

Installed Directories: /usr/include/urcu and /usr/share/doc/liburcu-0.14.0

libusb-1.0.27

Introduction to libusb

The libusb package contains a library used by some applications for USB device access.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2
Download MD5 sum: 1fb61afe370e94f902a67e03eb39c51f
Download size: 632 KB
Estimated disk space required: 5.7 MB
Estimated build time: less than 0.1 SBU

libusb Dependencies

Optional

Doxygen-1.10.0

Configuring Libusb

To access raw USB devices (those not treated as a disk by the mass-storage driver), appropriate support must be available in the kernel. Check your kernel configuration:

Device Drivers --->
  [*] USB support --->                                             [USB_SUPPORT]
    <*/M>   Support for Host-side USB                                      [USB]
    [*]     PCI based USB host interface                               [USB_PCI]
    # These are most common USB controller drivers for PC-like systems.
    # For modern systems often [USB_XHCI_HCD] is the only one needed
    # even if the system has USB 2.0 ports:
    < /*/M> xHCI HCD (USB 3.0) support                            [USB_XHCI_HCD]
    < /*/M> EHCI HCD (USB 2.0) support                            [USB_EHCI_HCD]
    < /*/M> OHCI HCD (USB 1.1) support                            [USB_OHCI_HCD]

For more details on setting up USB devices, see the section called “USB Device Issues”.

Installation of libusb

Install libusb by running the following commands:

./configure --prefix=/usr --disable-static &&
make

If Doxygen is installed and you wish to build the API documentation, issue the following commands:

pushd doc                &&
  doxygen -u doxygen.cfg &&
  make docs              &&
popd

This package does not come with a test suite.

Now, as the root user:

make install

If you built the API documentation, install it using the following commands as the root user:

install -v -d -m755 /usr/share/doc/libusb-1.0.27/apidocs &&
install -v -m644    doc/api-1.0/* \
                    /usr/share/doc/libusb-1.0.27/apidocs

Installed Programs: None

Installed Library: libusb-1.0.so

Installed Directories: /usr/include/libusb-1.0 and /usr/share/doc/libusb-1.0.27

Short Descriptions

libusb-1.0.so

contains API functions used for accessing USB hardware

libuv-1.48.0

Introduction to libuv

The libuv package is a multi-platform support library with a focus on asynchronous I/O.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://dist.libuv.org/dist/v1.48.0/libuv-v1.48.0.tar.gz
Download MD5 sum: a808517c32ebd07c561bf21a4e30aeab
Download size: 1.3 MB
Estimated disk space required: 14 MB (add 16 MB for tests)
Estimated build time: less than 0.1 SBU (add 0.5 SBU for tests)

libuv Dependencies

Optional

sphinx-7.2.6

Installation of libuv

Install libuv by running the following commands:

Caution

The sh autogen.sh command below fails if the ACLOCAL environment variable is set as specified in Xorg-7. If it is used, ACLOCAL needs to be unset for this package and then reset for other packages.

sh autogen.sh                              &&
./configure --prefix=/usr --disable-static &&
make

If you installed the optional sphinx-7.2.6 python module, create the man page:

make man -C docs

If you want to run the tests, run: make check as a non-root user.

Now, as the root user:

make install

If you built the man page, install it as the root user:

install -Dm644 docs/build/man/libuv.1 /usr/share/man/man1

Installed Programs: None

Installed Library: libuv.so

Installed Directory: /usr/include/uv

Short Descriptions

libuv.so

contains API functions for asynchronous I/O operations

libxkbcommon-1.6.0

Introduction to libxkbcommon

libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://xkbcommon.org/download/libxkbcommon-1.6.0.tar.xz
Download MD5 sum: 90079ab4a0c6fa56dc75abffef9b1bc6
Download size: 500 KB
Estimated disk space required: 23 MB (with tests)
Estimated build time: 0.4 SBU (with tests)

libxkbcommon Dependencies

Required

xkeyboard-config-2.41 (runtime)

Optional

Doxygen-1.10.0

Installation of libxkbcommon

Install libxkbcommon by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Denable-docs=false &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Denable-docs=false: This switch disables documentation generation. Remove it if Doxygen-1.10.0 is installed.

mv -v /usr/share/doc/libxkbcommon{,-1.6.0}: If you removed -Denable-docs=false, use this command to install the documentation in a versioned directory.

Installed Programs: xkbcli

Installed Libraries: libxkbcommon.so, libxkbcommon-x11.so, and libxkbregistry.so

Installed Directories: /usr/include/xkbcommon, /usr/libexec/xkbcommon, and /usr/share/doc/libxkbcommon-1.6.0

Short Descriptions

xkbcli	provides a debugger and compiler for XKB keymaps
`libxkbcommon.so`	contains the libxkbcommon API functions
`libxkbcommon-x11.so`	contains the libxkbcommon X11 specific API functions
`libxkbregistry.so`	contains a list of available XKB models, layouts, and variants for a given ruleset

libxml2-2.12.5

Introduction to libxml2

The libxml2 package contains libraries and utilities used for parsing XML files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libxml2/2.12/libxml2-2.12.5.tar.xz
Download MD5 sum: 329138464b69422815c11e62acbc10dd
Download size: 2.5 MB
Estimated disk space required: 103 MB (with tests)
Estimated build time: 0.4 SBU (Using parallelism=4; with tests)

Additional Downloads

Optional Test Suite: https://www.w3.org/XML/Test/xmlts20130923.tar.gz - This enables make check to do complete testing.

libxml2 Dependencies

Optional

Valgrind-3.22.0 (may be used in the tests)

Installation of libxml2

Install libxml2 by running the following commands:

./configure --prefix=/usr           \
            --sysconfdir=/etc       \
            --disable-static        \
            --with-history          \
            --with-icu              \
            PYTHON=/usr/bin/python3 \
            --docdir=/usr/share/doc/libxml2-2.12.5 &&
make

If you downloaded the test suite, issue the following command:

tar xf ../xmlts20130923.tar.gz

To test the results, issue: make check > check.log. This command will print several lines of error messages like “Failed to parse xstc/...” because some test files are missing and these messages can be safely ignored. A summary of the results can be obtained with grep -E '^Total|expected|Ran' check.log. If Valgrind-3.22.0 is installed and you want to check for memory leaks, replace check with check-valgrind.

Note

The tests use http://localhost/ to test parsing of external entities. If the machine where you run the tests serves as a web site, the tests may hang, depending on the content of the file served. It is therefore recommended to shut down the server during the tests, as the root user:

/etc/init.d/httpd stop

Now, as the root user:

make install

Finally, prevent some packages from unnecessarily linking to ICU using the following commands as the root user:

rm -vf /usr/lib/libxml2.la &&
sed '/libs=/s/xml2.*/xml2"/' -i /usr/bin/xml2-config

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--with-history: This switch enables Readline support when running xmlcatalog or xmllint in shell mode.

--with-icu: This switch enables support for ICU, which provides additional Unicode support. This is needed for some packages in BLFS, such as for QtWebEngine.

PYTHON=/usr/bin/python3: Allows building the libxml2 module with Python3 instead of Python2.

Installed Programs: xml2-config, xmlcatalog, and xmllint

Installed Libraries: libxml2.so

Installed Directories: /usr/include/libxml2, /usr/lib/cmake/libxml2, /usr/share/doc/libxml2-2.12.5, and /usr/share/gtk-doc/html/libxml2

Short Descriptions

xml2-config	determines the compile and linker flags that should be used to compile and link programs that use `libxml2`
xmlcatalog	is used to monitor and manipulate XML and SGML catalogs
xmllint	parses XML files and outputs reports (based upon options) to detect errors in XML coding
`libxml2.so`	provides functions for programs to parse files that use the XML format

libxmlb-0.3.15

Introduction to libxmlb

The libxmlb package contains a library and a tool which help create and query binary XML blobs.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/hughsie/libxmlb/releases/download/0.3.15/libxmlb-0.3.15.tar.xz
Download MD5 sum: ff8f7cefefc89d8bed97b911cb38fa9c
Download size: 100 KB
Estimated disk space required: 3.8 MB
Estimated build time: 0.1 SBU

libxmlb Dependencies

Required

Optional

GTK-Doc-1.33.2 and libstemmer

Installation of libxmlb

Install libxmlb by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release -Dgtkdoc=false .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dgtkdoc=false: This switch disables building the API documentation. Remove it if you have GTK-Doc-1.33.2 installed and wish to build the API documentation.

-Dintrospection=false: Use this switch if you do not have gobject-introspection-1.78.1 installed.

-Dstemmer=true: Use this switch if you have libstemmer installed and wish to build stemmer support.

Installed Programs: xb-tool

Installed Libraries: libxmlb.so

Installed Directories: /usr/include/libxmlb-2, /usr/libexec/installed-tests/libxmlb, and /usr/share/gtk-doc/html/libxmlb (if gtk-doc was enabled)

Short Descriptions

xb-tool	is a tool used to create, dump, or query a binary XML blob
`libxmlb.so`	contains functions that allow for creating and querying binary XML blobs

libxslt-1.1.39

Introduction to libxslt

The libxslt package contains XSLT libraries used for extending libxml2 libraries to support XSLT files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libxslt/1.1/libxslt-1.1.39.tar.xz
Download MD5 sum: 22e9eb7c23825124e786611b3760a3c7
Download size: 1.5 MB
Estimated disk space required: 34 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

libxslt Dependencies

Required

libxml2-2.12.5

Recommended (at runtime)

docbook-xml-4.5 and docbook-xsl-nons-1.79.2

Note

Although it is not a direct dependency, many applications using libxslt will expect docbook-xml-4.5 and docbook-xsl-nons-1.79.2 to be present.

Optional

libgcrypt-1.10.3

Installation of libxslt

Install libxslt by running the following commands:

./configure --prefix=/usr                          \
            --disable-static                       \
            --docdir=/usr/share/doc/libxslt-1.1.39 \
            PYTHON=/usr/bin/python3 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: xslt-config and xsltproc

Installed Libraries: libexslt.so, libxslt.so and optionally, libxsltmod.so Python module

Installed Directories: /usr/include/libexslt, /usr/include/libxslt, /usr/lib/cmake/libxslt, /usr/lib/libxslt-plugins, /usr/share/gtk-doc/lib{xslt,exslt}, /usr/share/doc/libxslt-1.1.39, and /usr/share/doc/libxslt-python-1.1.39

Short Descriptions

xslt-config	is used to find out the pre-processor, linking and compiling flags necessary to use the libxslt libraries in 3rd-party programs
xsltproc	is used to apply XSLT stylesheets to XML documents
`libexslt.so`	is used to provide extensions to XSLT functions
`libxslt.so`	provides extensions to the `libxml2` libraries to parse files that use the XSLT format

libwacom-2.10.0

Introduction to libwacom

The libwacom package contains a library used to identify wacom tablets and their model-specific features.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/linuxwacom/libwacom/releases/download/libwacom-2.10.0/libwacom-2.10.0.tar.xz
Download MD5 sum: 9baf8fb0e486e225ef81b9becb46031b
Download size: 116 KB
Estimated disk space required: 3.4 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

libwacom Dependencies

Required

libgudev-238

Optional

Doxygen-1.10.0, git-2.44.0, librsvg-2.57.1, Valgrind-3.22.0 (optional for some tests), and pytest-8.0.0 with python-libevdev and pyudev

Installation of libwacom

Install libwacom by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Dtests=disabled    &&
ninja

To test the results, issue: ninja test. To run additional tests, install pytest-8.0.0, python-libevdev, and pyudev, then remove the "-Dtests=disabled" option from the meson line above.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dtests=disabled: This parameter disables some of the more advanced tests because they require pytest-8.0.0 and other two Python modules beyond the scope of BLFS to work properly.

Installed Programs: libwacom-list-devices, libwacom-list-local-devices, libwacom-show-stylus, and libwacom-update-db

Installed Libraries: libwacom.so

Installed Directories: /usr/include/libwacom-1.0 and /usr/share/libwacom

Short Descriptions

libwacom-list-devices	lists all tablet devices that are supported by libwacom
libwacom-list-local-devices	lists tablet devices that are connected to the system
libwacom-show-stylus	lists tablet stylus IDs
libwacom-update-db	updates the system according to the current set of tablet data files
`libwacom.so`	contains functions used for accessing Wacom information

libwpe-1.14.2

Introduction to libwpe

The libwpe package contains a general purpose library for WPE WebKit and the WPE Renderer.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://wpewebkit.org/releases/libwpe-1.14.2.tar.xz
Download MD5 sum: 61840e24ba0a0f5828194dff28db92ee
Download size: 64 KB
Estimated disk space required: 1.9 MB
Estimated build time: less than 0.1 SBU

libwpe Dependencies

Required

libxkbcommon-1.6.0 and Mesa-24.0.1

Optional

hotdoc

Installation of libwpe

Install libwpe by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: None

Installed Libraries: libwpe-1.0.so

Installed Directories: /usr/include/wpe-1.0

Short Descriptions

libwpe-1.0.so

contains functions that provide a general purpose library for WPEWebKit and the WPE Renderer

libyaml-0.2.5

Introduction to libyaml

The yaml package contains a C library for parsing and emitting YAML (YAML Ain't Markup Language) code.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/yaml/libyaml/releases/download/0.2.5/yaml-0.2.5.tar.gz
Download MD5 sum: bb15429d8fb787e7d3f1c83ae129a999
Download size: 596 KB
Estimated disk space required: 6.4 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

libyaml Dependencies

Optional

Doxygen-1.10.0

Installation of libyaml

Install libyaml by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: libyaml.so

Installed Directories: None

Short Descriptions

libyaml.so

contains API functions for parsing and emitting YAML code

log4cplus-2.1.1

Introduction to log4cplus

log4cplus is an easy to use C++20 logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modeled after the Java log4j API.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/log4cplus/log4cplus/releases/download/REL_2_1_1/log4cplus-2.1.1.tar.xz
Download MD5 sum: 6ee2555be39cd269086cc871c834e43f
Download size: 919 KB
Estimated disk space required: 73 MB
Estimated build time: 0.3 SBU (Using parallelism=4; add 0.5 SBU for tests)

log4cplus Dependencies

Optional

(Qt-5.15.12 or qt-alternate-5.15.12)

Installation of log4cplus

Build log4cplus by running the following command:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, install the package as the root user:

make install

Command Explanations

--with-qt5: This option enables compilation of a separate shared library (liblog4cplusqt5debugappender) that implements Qt5DebugAppender. It requires Qt5 and pkg-config to be available.

Installed Programs: None

Installed Library: log4cplus.so

Installed Directories: None

Short Descriptions

log4cplus.so

is the log4cplus library

LZO-2.10

Introduction to LZO

LZO is a data compression library which is suitable for data decompression and compression in real-time. This means it favors speed over compression ratio.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.oberhumer.com/opensource/lzo/download/lzo-2.10.tar.gz
Download MD5 sum: 39d3f3f9c55c87b1e5d6888e1420f4b5
Download size: 588 KB
Estimated disk space required: 12 MB
Estimated build time: 0.3 SBU (with tests)

Installation of LZO

Install LZO by running the following commands:

./configure --prefix=/usr                    \
            --enable-shared                  \
            --disable-static                 \
            --docdir=/usr/share/doc/lzo-2.10 &&
make

To test the results, issue: make check. All the checks should pass. Now issue make test to run the full suite of tests.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: liblzo2.so

Installed Directories: /usr/include/lzo and /usr/share/doc/lzo

Short Descriptions

liblzo2.so

is a data compression and decompression library

mtdev-1.1.6

Introduction to mtdev

The mtdev package contains Multitouch Protocol Translation Library which is used to transform all variants of kernel MT (Multitouch) events to the slotted type B protocol.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://bitmath.org/code/mtdev/mtdev-1.1.6.tar.bz2
Download MD5 sum: bf8ef2482e84a00b5db8fbd3ce00e249
Download size: 292 KB
Estimated disk space required: 2.5 MB
Estimated build time: less than 0.1 SBU

Installation of mtdev

Install mtdev by running the following commands:

./configure --prefix=/usr --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: mtdev-test

Installed Library: libmtdev.so

Installed Directories: None

Short Descriptions

mtdev-test	is a tool to test `libmtdev`
`libmtdev.so`	contains Multitouch Protocol Translation API functions

Node.js-20.11.1

Introduction to Node.js

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://nodejs.org/dist/v20.11.1/node-v20.11.1.tar.xz
Download MD5 sum: 3b2fe4d7a4c8dadb58563d822de6c4f4
Download size: 41 MB
Estimated disk space required: 1040 MB (add 62 MB for tests)
Estimated build time: 10.9 SBU (add 3.2 SBU for tests: both using parallelism=8 and 8 CPUs online, parts of the tests will use all online CPUs)

Node.js Dependencies

Required

Which-2.21

Optional

http-parser and npm (an internal copy of npm will be installed if not present)

Installation of Node.js

Build Node.js by running the following commands:

./configure --prefix=/usr          \
            --shared-brotli        \
            --shared-cares         \
            --shared-libuv         \
            --shared-openssl       \
            --shared-nghttp2       \
            --shared-zlib          \
            --with-intl=system-icu &&
make

To test the results, issue: make test-only.

Now, as the root user:

make install &&
ln -sf node /usr/share/doc/node-20.11.1

Command Explanations

--with-intl=system-icu: use the system version of icu. Other values are full-icu (to build a local, full icu library) and small-icu (to build a local, minimal icu library).

--shared-{brotli,cares,libuv,nghttp2,openssl,zlib}: use the system installed libraries instead of local copies.

--without-npm: do not build npm (use if you'd like to build a separate npm later).

--shared-http-parser: use the system installed library instead of a local copy.

Installed Programs: corepack, node, npm, and npx

Installed Library: None

Installed Directories: /usr/include/node, /usr/lib/node_modules/{corepack,npm}, /usr/share/doc/{node,node-20.11.1}, and /usr/share/systemtap/tapset

Short Descriptions

corepack	is an experimental tool to help with managing versions of package managers.
node	is the server-side JavaScript runtime
npm	is the Node.js package manager
`/usr/lib/node_modules/npm/`	is the installation root for Node.js executables and libraries

npth-1.6

Introduction to NPth

The NPth package contains a very portable POSIX/ANSI-C based library for Unix platforms which provides non-preemptive priority-based scheduling for multiple threads of execution (multithreading) inside event-driven applications. All threads run in the same address space of the server application, but each thread has its own individual program-counter, run-time stack, signal mask and errno variable.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/npth/npth-1.6.tar.bz2
Download MD5 sum: 375d1a15ad969f32d25f1a7630929854
Download size: 296 KB
Estimated disk space required: 2.6 MB (with checks)
Estimated build time: less than 0.1 SBU (with checks)

Installation of NPth

Install NPth by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Program: npth-config

Installed Library: libnpth.so

Installed Directory: None

Short Descriptions

npth-config	is a utility used to configure and build applications based on the npth library. It can be used to query the C compiler and linker flags which are required to correctly compile and link the application against the npth library
`libnpth.so`	contains the API functions used by the New Portable Threads Library

NSPR-4.35

Introduction to NSPR

Netscape Portable Runtime (NSPR) provides a platform-neutral API for system level and libc like functions.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://archive.mozilla.org/pub/nspr/releases/v4.35/src/nspr-4.35.tar.gz
Download MD5 sum: 5e0acf9fbdde85181bddd510f4624841
Download size: 1.0 MB
Estimated disk space required: 9.6 MB
Estimated build time: less than 0.1 SBU

Installation of NSPR

Install NSPR by running the following commands:

cd nspr &&

sed -i '/^RELEASE/s|^|#|' pr/src/misc/Makefile.in &&
sed -i 's|$(LIBRARY) ||'  config/rules.mk         &&

./configure --prefix=/usr   \
            --with-mozilla  \
            --with-pthreads \
            $([ $(uname -m) = x86_64 ] && echo --enable-64bit) &&
make

The test suite is designed for testing changes to nss or nspr and is not particularly useful for checking a released version (e.g. it needs to be run on a non-optimized build with both nss and nspr directories existing alongside each other). For further details, see the Editor Notes for nss at https://wiki.linuxfromscratch.org/blfs/wiki/nss

Now, as the root user:

make install

Command Explanations

sed -ri '/^RELEASE/s/^/#/' pr/src/misc/Makefile.in: This sed disables installing two unneeded scripts.

sed -i 's#$(LIBRARY) ##' config/rules.mk: This sed disables installing the static libraries.

--with-mozilla: This parameter adds Mozilla support to the libraries (required if you want to build any other Mozilla products and link them to these libraries).

--with-pthreads: This parameter forces use of the system pthread library.

--enable-64bit: The --enable-64bit parameter is required on an x86_64 system to prevent configure failing with a claim that this is a system without pthread support. The [ $(uname -m) = x86_64 ] test ensures it has no effect on a 32 bit system.

Installed Programs: nspr-config

Installed Libraries: libnspr4.so, libplc4.so, and libplds4.so

Installed Directories: /usr/include/nspr

Short Descriptions

nspr-config	provides compiler and linker options to other packages that use NSPR
`libnspr4.so`	contains functions that provide platform independence for non-GUI operating system facilities such as threads, thread synchronization, normal file and network I/O, interval timing and calendar time, basic memory management and shared library linking
`libplc4.so`	contains functions that implement many of the features offered by libnspr4
`libplds4.so`	contains functions that provide data structures

PCRE-8.45

Introduction to PCRE

The PCRE package contains Perl Compatible Regular Expression libraries. These are useful for implementing regular expression pattern matching using the same syntax and semantics as Perl 5.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://sourceforge.net/projects/pcre/files/pcre/8.45/pcre-8.45.tar.bz2
Download MD5 sum: 4452288e6a0eefb2ab11d36010a1eebb
Download size: 1.5 MB
Estimated disk space required: 23 MB (with tests)
Estimated build time: 0.3 SBU (with tests)

PCRE Dependencies

Optional

Valgrind-3.22.0

Installation of PCRE

Install PCRE by running the following commands:

./configure --prefix=/usr                     \
            --docdir=/usr/share/doc/pcre-8.45 \
            --enable-unicode-properties       \
            --enable-pcre16                   \
            --enable-pcre32                   \
            --enable-pcregrep-libz            \
            --enable-pcregrep-libbz2          \
            --enable-pcretest-libreadline     \
            --disable-static                 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-unicode-properties: This switch enables Unicode properties support and includes the code for handling UTF-8/16/32 character strings in the library. You need this switch if you are going to build GLib-2.78.4.

--enable-pcre16: This switch enables 16 bit character support.

--enable-pcre32: This switch enables 32 bit character support.

--enable-pcregrep-libz: This switch adds support to pcregrep to read .gz compressed files.

--enable-pcregrep-libbz2: This switch adds support to pcregrep to read .bz2 compressed files.

--enable-pcretest-libreadline: This switch adds line editing and history features to pcretest program.

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-jit: this option enables Just-in-time compiling, which can greatly speed up pattern matching.

Installed Programs: pcregrep, pcretest, and pcre-config

Installed Libraries: libpcre.so, libpcre16.so, libpcre32.so, libpcrecpp.so and libpcreposix.so

Installed Directory: /usr/share/doc/pcre-8.45

Short Descriptions

pcregrep	is a grep that understands Perl compatible regular expressions
pcretest	can test a Perl compatible regular expression
pcre-config	is used during the compile process of programs linking to the PCRE libraries

PCRE2-10.42

Introduction to PCRE2

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.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/PCRE2Project/pcre2/releases/download/pcre2-10.42/pcre2-10.42.tar.bz2
Download MD5 sum: a8e9ab2935d428a4807461f183034abe
Download size: 1.7 MB
Estimated disk space required: 24 MB (with tests)
Estimated build time: 0.4 SBU (with tests)

PCRE2 Dependencies

Optional

Valgrind-3.22.0 and libedit

Installation of PCRE2

Install PCRE2 by running the following commands:

./configure --prefix=/usr                       \
            --docdir=/usr/share/doc/pcre2-10.42 \
            --enable-unicode                    \
            --enable-jit                        \
            --enable-pcre2-16                   \
            --enable-pcre2-32                   \
            --enable-pcre2grep-libz             \
            --enable-pcre2grep-libbz2           \
            --enable-pcre2test-libreadline      \
            --disable-static                    &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-unicode: This switch enables Unicode support and includes the functions for handling UTF-8/16/32 character strings in the library.

--enable-pcre2-16: This switch enables 16 bit character support.

--enable-pcre2-32: This switch enables 32 bit character support.

--enable-pcre2grep-libz: This switch adds support for reading .gz compressed files to pcre2grep.

--enable-pcre2grep-libbz2: This switch adds support for reading .bz2 compressed files to pcre2grep.

--enable-pcre2test-libreadline: This switch adds line editing and history features to the pcre2test program.

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-jit: this option enables Just-in-time compiling, which can greatly speed up pattern matching.

Installed Programs: pcre2-config, pcre2grep, and pcre2test.

Installed Libraries: libpcre2-8.so, libpcre2-16.so, libpcre2-32.so, and libpcre2-posix.so

Installed Directory: /usr/share/doc/pcre2-10.42

Short Descriptions

pcre2grep	is a version of grep that understands Perl compatible regular expressions.
pcre2test	can test a Perl compatible regular expression.
pcre2-config	outputs compilation information to programs linking against the PCRE2 libraries

Popt-1.19

Introduction to Popt

The popt package contains the popt libraries which are used by some programs to parse command-line options.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://ftp.rpm.org/popt/releases/popt-1.x/popt-1.19.tar.gz
Download MD5 sum: eaa2135fddb6eb03f2c87ee1823e5a78
Download size: 584 KB
Estimated disk space required: 6.9 MB (includes installing documentation and tests)
Estimated build time: less than 0.1 SBU (with tests)

popt Dependencies

Optional

Doxygen-1.10.0 (for generating documentation)

Installation of Popt

Install popt by running the following commands:

./configure --prefix=/usr --disable-static &&
make

If you have Doxygen-1.10.0 installed and wish to build the API documentation, issue:

sed -i 's@\./@src/@' Doxyfile &&
doxygen

To test the results, issue: make check.

Now, as the root user:

make install

If you built the API documentation, install it using the following commands issued by the root user:

install -v -m755 -d /usr/share/doc/popt-1.19 &&
install -v -m644 doxygen/html/* /usr/share/doc/popt-1.19

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libpopt.so

Installed Directories: /usr/share/doc/popt-1.19

Short Descriptions

libpopt.so

is used to parse command-line options

Qca-2.3.8

Introduction to Qca

Qca aims to provide a straightforward and cross-platform crypto API, using Qt datatypes and conventions. Qca separates the API from the implementation, using plugins known as Providers.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.kde.org/stable/qca/2.3.8/qca-2.3.8.tar.xz
Download MD5 sum: 4c6348286c170b3da24820c977565d75
Download size: 744 KB
Estimated disk space required: 42 MB
Estimated build time: 0.5 SBU (using parallelism=4; add 0.1 SBU for tests)

Qca Dependencies

Required

make-ca-1.13, CMake-3.28.3, Qt-5.15.12, and Which-2.21

Optional

Cyrus SASL-2.1.28, GnuPG-2.4.4, libgcrypt-1.10.3, libgpg-error-1.47, nss-3.98, NSPR-4.35, p11-kit-0.25.3, Doxygen-1.10.0, Which-2.21, and Botan

Installation of Qca

Fix the location of the CA certificates:

sed -i 's@cert.pem@certs/ca-bundle.crt@' CMakeLists.txt

Install Qca by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=$QT5DIR            \
      -DCMAKE_BUILD_TYPE=Release                \
      -DQCA_MAN_INSTALL_DIR:PATH=/usr/share/man \
      .. &&
make

To test the results, issue make test.

Now, as the root user:

make install

Command Explanations

-DCMAKE_BUILD_TYPE=Release: This switch is used to apply a higher level of compiler optimizations.

-DQCA_MAN_INSTALL_DIR:PATH=/usr/share/man: Install the qca man page in the normal location.

Installed Programs: mozcerts-qt5 and qcatool-qt5

Installed Libraries: libqca-qt5.so, libqca-cyrus-sasl.so, libqca-gcrypt.so, libqca-gnupg.so, libqca-logger.so, libqca-nss.so, libqca-ossl.so, and libqca-softstore.so

Installed Directories: $QT5DIR/include/Qca-qt5, $QT5DIR/lib/cmake/Qca-qt5, and $QT5DIR/lib/qca-qt5

Short Descriptions

mozcerts-qt5	is a command line tool for converting certdata.txt into outfile.pem files
qcatool-qt5	is a command line tool for performing various cryptographic operations with Qca
`libqca-qt5.so`	is the Qt Cryptography Architecture (Qca) library

SpiderMonkey from Firefox-115.7.0

Introduction to SpiderMonkey

SpiderMonkey is Mozilla's JavaScript and WebAssembly Engine, written in C++ and Rust. In BLFS, the source code of SpiderMonkey is taken from Firefox.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://archive.mozilla.org/pub/firefox/releases/115.7.0esr/source/firefox-115.7.0esr.source.tar.xz
Download MD5 sum: 9105bdf076d457ce5e0aa5628d5acc84
Download size: 492 MB
Estimated disk space required: 3.6 GB (40 MB installed after removing 36MB static lib; add 34 MB for the main tests and 37 MB for the jit tests)
Estimated build time: 1.9 SBU (with parallelism=4; add 1.1 SBU for the main tests and 3.7 SBU for the jit tests)

SpiderMonkey Dependencies

Required

ICU-74.2, rustc-1.76.0, six-1.16.0, and Which-2.21

Important

If you are building this package on a 32-bit system, and Clang is not installed or you're overriding the default compiler choice with the environment variable CXX, please read the Command Explanations section first.

Installation of SpiderMonkey

Note

Unlike most other packages in BLFS, the instructions below require you to untar firefox-115.7.0esr.tar.xz and change into the firefox-115.7.0 folder.

Extracting the tarball will reset the permissions of the current directory to 0755 if you have permission to do that. If you do this in a directory where the sticky bit is set, such as /tmp it will end with error messages:

tar: .: Cannot utime: Operation not permitted
tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
tar: Exiting with failure status due to previous errors

This does finish with non-zero status, but it does NOT mean there is a real problem. Do not untar as the root user in a directory where the sticky bit is set - that will unset it.

The building system ships several internal copies of the Python 3 module six.py. The shipped copies are too old to work well with Python 3.12 or later. Replace them with the symlinks to six-1.16.0 already installed on the system:

for i in $(find -name six.py); do
  ln -sfv /usr/lib/python3.12/site-packages/six.py $i;
done

Install SpiderMonkey by running the following commands:

Note

If you are compiling this package in chroot you must ensure that /dev/shm is mounted. If you do not do this, the Python configuration will fail with a traceback report referencing /usr/lib/pythonN.N/multiprocessing/synchronize.py. As the root user, run:

mountpoint -q /dev/shm || mount -t tmpfs devshm /dev/shm

Compiling the C++ code respects $MAKEFLAGS and defaults to 'j1', the rust code will use all processors.

mkdir obj &&
cd    obj &&

../js/src/configure --prefix=/usr            \
                    --disable-debug-symbols  \
                    --disable-jemalloc       \
                    --enable-readline        \
                    --enable-rust-simd       \
                    --with-intl-api          \
                    --with-system-icu        \
                    --with-system-zlib       &&
make

To run the SpiderMonkey test suite, issue: make -C js/src check-jstests JSTESTS_EXTRA_ARGS="--timeout 300 --wpt=disabled". It's recommended to redirect the output into a log. Because we are building with system ICU, 42 tests (out of a total of more than 50,000) are known to fail. The test suite is executed with all CPU cores available: even in a cgroup with less cores assigned, it still attempts to spawn as many testing jobs as the number of all cores in the system; fortunately the kernel still won't run these jobs on cores not assigned to the cgroup so the CPU usage is still controlled.

To run the JIT test suite, issue: make -C js/src check-jit-test JITTEST_EXTRA_ARGS="--timeout 300". Like the SpiderMonkey test suite, the number of test jobs is same as the number of all CPU cores in the system even if a cgroup is used. To make things worse, there are six tests each of them will use 3 GB of system memory, so the peak memory usage may be up to 18 GB if the number of cores is six or more. Running the JIT test suite without enough memory may invoke the kernel OOM killer and cause stability issues. If you don't have enough system memory available, append -jN after --timeout 300 with N replaced by the number of parallel test jobs you want to start. For example, if you have 16 GB system memory available and 8 CPU cores, issue make -C js/src check-jit-test JITTEST_EXTRA_ARGS="--timeout=300 -j5" to run the test with 5 parallel jobs so the memory usage won't exceed 15 GB.

Caution

An issue in the installation process causes any running program which links to SpiderMonkey shared library (for example, GNOME Shell) to crash if SpiderMonkey is reinstalled, or upgraded or downgraded without a change of the major version number (115 in 115.7.0). To work around this issue, remove the old version of the SpiderMonkey shared library before installation:

rm -fv /usr/lib/libmozjs-115.so

Now, as the root user:

make install &&
rm -v /usr/lib/libjs_static.ajs &&
sed -i '/@NSPR_CFLAGS@/d' /usr/bin/js115-config

Command Explanations

--disable-debug-symbols: Don't generate debug symbols since they are very large and most users won't need it. Remove it if you want to debug SpiderMonkey.

--disable-jemalloc: This switch disables the internal memory allocator used in SpiderMonkey. jemalloc is only intended for the Firefox browser environment. For other applications using SpiderMonkey, the application may crash as items allocated in the jemalloc allocator are freed on the system (glibc) allocator.

--enable-readline: This switch enables Readline support in the SpiderMonkey command line interface.

--enable-rust-simd: This switch enables SIMD optimization in the shipped encoding_rs crate.

--with-intl-api: This enables the internationalization functions required by Gjs.

--with-system-*: These parameters allow the build system to use system versions of the above libraries. These are required for stability.

rm -v /usr/lib/libjs_static.ajs: Remove a large static library which is not used by any BLFS package.

sed -i '/@NSPR_CFLAGS@/d' /usr/bin/js115-config: Prevent js115-config from using buggy CFLAGS.

CC=gcc CXX=g++: BLFS used to prefer to use gcc and g++ instead of upstream's defaults of the clang programs. With the release of gcc-12 the build takes longer with gcc and g++, primarily because of extra warnings, and is bigger. Pass these environment variables to the configure script if you wish to continue to use gcc, g++ (by exporting them and unset them after the installation, or simply prepending them before the ../js/src/configure command). If you are building on a 32-bit system, also see below.

CXXFLAGS="-msse2 -mfpmath=sse": Use SSE2 instead of 387 for double-precision floating-point operations. It's needed by GCC to satisfy the expectations of upstream (Mozilla) developers with floating-point arithmetic. Use it if you are building this package on a 32-bit system with GCC (if Clang is not installed or GCC is explicitly specified). Note that this will cause SpiderMonkey to crash on a processor without SSE2 capability. If you are running the system on such an old processor, Clang is strictly needed. This setting is not needed on 64-bit systems because all 64-bit x86 processors support SSE2 and the 64-bit compilers (both Clang and GCC) use SSE2 by default.

Installed Programs: js115 and js115-config

Installed Libraries: libmozjs-115.so

Installed Directories: /usr/include/mozjs-115

Short Descriptions

js115	provides a command line interface to the JavaScript engine
js115-config	is used to find the SpiderMonkey compiler and linker flags
`libmozjs-115.so`	contains the Mozilla JavaScript API functions

SPIRV-Headers-1.3.275.0

Introduction to SPIRV-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, including OpenGL and Vulkan.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/KhronosGroup/SPIRV-Headers/archive/refs/tags/vulkan-sdk-1.3.275.0/SPIRV-Headers-1.3.275.0.tar.gz
Download MD5 sum: f293886617aa816fdbb2b50d5e909681
Download size: 456 KB
Estimated disk space required: 6.7 MB
Estimated build time: less than 0.1 SBU

SPIRV-Headers Dependencies

Required

Installation of SPIRV-Headers

Note

This tarball SPIRV-Headers-1.3.275.0.tar.gz will extract to the directory SPIRV-Headers-vulkan-sdk-1.3.275.0.

Install SPIRV-Headers by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr -G Ninja .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Installed Programs: None

Installed Libraries: None

Installed Directories: /usr/include/spirv and /usr/share/cmake/SPIRV-Headers

SPIRV-Tools-1.3.275.0

Introduction to SPIRV-Tools

The SPIRV-Tools package contains libraries and utilities for processing SPIR-V modules.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/KhronosGroup/SPIRV-Tools/archive/refs/tags/vulkan-sdk-1.3.275.0/SPIRV-Tools-1.3.275.0.tar.gz
Download MD5 sum: f187bb132058995a5992a5a15c269bb1
Download size: 3.0 MB
Estimated disk space required: 70 MB
Estimated build time: 1.0 SBU (with parallelism=8)

SPIRV-Tools Dependencies

Required

CMake-3.28.3 and SPIRV-Headers-1.3.275.0

Installation of SPIRV-Tools

Note

This tarball SPIRV-Tools-1.3.275.0.tar.gz will extract to the directory SPIRV-Tools-vulkan-sdk-1.3.275.0.

Install SPIRV-Tools by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr     \
      -DCMAKE_BUILD_TYPE=Release      \
      -DSPIRV_WERROR=OFF              \
      -DBUILD_SHARED_LIBS=ON          \
      -DSPIRV_TOOLS_BUILD_STATIC=OFF  \
      -DSPIRV-Headers_SOURCE_DIR=/usr \
      -G Ninja .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

-DSPIRV_WERROR=OFF: This switch stops the build system from treating warnings as errors.

-DBUILD_SHARED_LIBS=ON: This switch forces the build system to install shared libraries instead of static libraries.

-DSPIRV_TOOLS_BUILD_STATIC=OFF: This switch disables building static versions of the libraries.

-DSPIRV-Headers_SOURCE_DIR: This switch tells the build system that SPIRV-Headers-1.3.275.0 is installed in /usr. This is needed since the build system tries to use an internal copy by default.

Installed Programs: spirv-as, spirv-cfg, spirv-dis, spirv-lesspipe.sh, spirv-link, spirv-lint, spirv-objdump, spirv-opt, spirv-reduce, and spirv-val

Installed Libraries: libSPIRV-Tools-diff.so, libSPIRV-Tools-link.so, libSPIRV-Tools-lint.so, libSPIRV-Tools-opt.so, libSPIRV-Tools-reduce.so, libSPIRV-Tools-shared.so, and libSPIRV-Tools.so

Installed Directories: /usr/include/spirv-tools and /usr/lib/cmake/SPIRV-Tools

Short Descriptions

spirv-as	creates a SPIR-V binary module from SPIR-V assembly text
spirv-cfg	shows the control flow graph in "dot" format
spirv-dis	disassembles a SPIR-V binary module
spirv-lesspipe.sh	automatically disassembles a .SPV file for 'less'
spirv-link	links SPIR-V binary files together
spirv-lint	checks a SPIR-V binary module for errors
spirv-objdump	dumps information from a SPIR-V binary
spirv-opt	performs optimizations on SPIR-V binary files
spirv-reduce	reduces a SPIR-V binary file
spirv-val	validates a SPIR-V binary file
`libSPIRV-Tools.so`	contains functions for processing SPIR-V modules

Talloc-2.4.2

Introduction to Talloc

Talloc provides a hierarchical, reference counted memory pool system with destructors. It is the core memory allocator used in Samba.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.samba.org/ftp/talloc/talloc-2.4.2.tar.gz
Download MD5 sum: d29bdf75ce181e148c46b16a83de6d76
Download size: 664 KB
Estimated disk space required: 10 MB (with tests)
Estimated build time: 0.4 SBU (with tests)

Talloc Dependencies

Optional

docbook-xml-4.5, docbook-xsl-nons-1.79.2 and libxslt-1.1.39 (To generate man pages), GDB-14.1, git-2.44.0, libnsl-2.0.1, libtirpc-1.3.4, Valgrind-3.22.0, and xfsprogs-6.6.0

Installation of Talloc

Install Talloc by running the following commands:

./configure --prefix=/usr &&
make

To check the results, issue make check.

Now, as the root user:

make install

Installed Programs: None

Installed Libraries: libpytalloc-util.cpython-312-<arch>-linux-gnu.so, libtalloc.so, and talloc.cpython-312-<arch>-linux-gnu.so (Python 3 Module)

Installed Directories: None

Short Descriptions

libtalloc.so

contains a replacement for the Glibc malloc function

telepathy-glib-0.24.2

Introduction to Telepathy GLib

The Telepathy GLib contains a library used by GLib based Telepathy components. Telepathy is a D-Bus framework for unifying real time communication, including instant messaging, voice calls and video calls. It abstracts differences between protocols to provide a unified interface for applications.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://telepathy.freedesktop.org/releases/telepathy-glib/telepathy-glib-0.24.2.tar.gz
Download MD5 sum: a3a75657e9389381b44fee1680f770a7
Download size: 3.7 MB
Estimated disk space required: 256 MB
Estimated build time: 1.2 SBU

Telepathy GLib Dependencies

Required

dbus-glib-0.112 and libxslt-1.1.39

Optional

Installation of Telepathy Glib

If you intend to run the tests, one of them defaults to invoking /usr/bin/python and fails if it is absent, causing the second batch of tests to not run - unlike the other tests which can be overridden from the environment. Fix it with the following command:

sed -i 's%/usr/bin/python%&3%' tests/all-errors-documented.py

Install Telepathy GLib by running the following commands:

PYTHON=/usr/bin/python3 ./configure --prefix=/usr          \
                                    --enable-vala-bindings \
                                    --disable-static       &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-vala-bindings: This switch enables building of the Vala bindings. Remove if you don't have Vala-0.56.14 installed.

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: None

Installed Libraries: libtelepathy-glib.so

Installed Directories: /usr/include/telepathy-1.0 and /usr/share/gtk-doc/html/telepathy-glib

Short Descriptions

libtelepathy-glib.so

contains the Telepathy GLib API functions

Uchardet-0.0.8

Introduction to Uchardet

The Uchardet package contains an encoding detectory library which takes a sequence of bytes in an unknown character encoding and attempts to determine the encoding of the text.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/uchardet/releases/uchardet-0.0.8.tar.xz
Download MD5 sum: 9e267be7aee81417e5875086dd9d44fd
Download size: 217 KB
Estimated disk space required: 4.6 MB (with test)
Estimated build time: less than 0.1 SBU (with test)

Uchardet Dependencies

Required

Installation of Uchardet

Install Uchardet by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DBUILD_STATIC=OFF          \
      -Wno-dev ..                 &&
make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

-DBUILD_STATIC=OFF: This switch disables building the static version of the library.

Installed Programs: uchardet

Installed Libraries: libuchardet.so

Installed Directories: /usr/include/uchardet

Short Descriptions

uchardet	detects what character set is used inside of a file
`libuchardet.so`	provides an API for detecting the encoding of text in a file

Umockdev-0.17.18

Introduction to Umockdev

The Umockdev package contains a framework that allows a developer to mock devices for use in unit testing.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/martinpitt/umockdev/releases/download/0.17.18/umockdev-0.17.18.tar.xz
Download MD5 sum: a9ff284518c034aa334b58237074e313
Download size: 484 KB
Estimated disk space required: 6.8 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Umockdev Dependencies

Required

libgudev-238, libpcap-1.10.4, and Vala-0.56.14

Optional

GTK-Doc-1.33.2 and libgphoto2 (optional for tests)

Installation of Umockdev

Install Umockdev by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test. One test needs to be run in an X session.

Now, as the root user:

ninja install

Command Explanations

-Dgtk_doc=true: Use this switch if you have GTK-Doc-1.33.2 installed and wish to rebuild and install the API documentation.

Installed Programs: umockdev-record, umockdev-run, and umockdev-wrapper

Installed Libraries: libumockdev-preload.so and libumockdev.so

Installed Directories: /usr/include/umockdev-1.0

Short Descriptions

umockdev-record	records Linux devices and their ancestors from sysfs/udev or records ioctls for a device
umockdev-run	runs a program under an umockdev testbed
umockdev-wrapper	wraps a program around `libumockdev-preload.so.0` through LD_PRELOAD
`libumockdev.so`	provides API functions that allow mocking hardware devices for unit testing

utfcpp-4.0.5

Introduction to utfcpp

The utfcpp package contains a set of include files to provide UTF-8 with C++ in a Portable Way.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/nemtrif/utfcpp/archive/v4.0.5/utfcpp-4.0.5.tar.gz
Download MD5 sum: 8e0fe13266a7fa02f61340bf399986c3
Download size: 36 KB
Estimated disk space required: 496 KB
Estimated build time: less than 0.1 SBU

utfcpp Dependencies

Required

Installation of utfcpp

Install utfcpp by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr ..

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: None

Installed Libraries: None

Installed Directories: /usr/include/utfcpp and /usr/share/utfcpp

Wayland-1.22.0

Introduction to Wayland

Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.freedesktop.org/wayland/wayland/-/releases/1.22.0/downloads/wayland-1.22.0.tar.xz
Download MD5 sum: 7410ab549e3928fce9381455b17b0803
Download size: 228 KB
Estimated disk space required: 7.4 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Wayland Dependencies

Required

libxml2-2.12.5

Optional

Doxygen-1.10.0, Graphviz-10.0.1 and xmlto-0.0.28 (to build the API documentation) and docbook-xml-4.5, docbook-xsl-nons-1.79.2 and libxslt-1.1.39 (to build the manual pages)

Installation of Wayland

Install Wayland by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Ddocumentation=false &&
ninja

To test the results, issue: env -u XDG_RUNTIME_DIR ninja test.

Now, as the root user:

ninja install

Command Explanations

-Ddocumentation=false: This switch is used to disable building of the API documentation. Remove it if you have installed optional dependencies.

Installed Programs: wayland-scanner

Installed Libraries: libwayland-client.so, libwayland-cursor.so, libwayland-egl.so, and libwayland-server.so

Installed Directories: /usr/share/wayland

Short Descriptions

wayland-scanner	is a tool to generate proxy methods in wayland-client-protocol.h and wayland-server-protocol.h
`libwayland-client.so`	contains API functions for writing Wayland applications
`libwayland-cursor.so`	contains API functions for managing cursors in Wayland applications
`libwayland-egl.so`	contains API functions for handling OpenGL calls in Wayland applications
`libwayland-server.so`	contains API functions for writing Wayland compositors

Wayland-Protocols-1.33

Introduction to Wayland-Protocols

The Wayland-Protocols package contains additional Wayland protocols that add functionality outside of protocols already in the Wayland core.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/1.33/downloads/wayland-protocols-1.33.tar.xz
Download MD5 sum: 6af4d3a18fbfc7d8aa3f9ccf5b4743f3
Download size: 92 KB
Estimated disk space required: 7.9 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Wayland-protocols Dependencies

Required

Wayland-1.22.0

Installation of Wayland-protocols

Install Wayland-protocols by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Installed Programs: None

Installed Libraries: None

Installed Directories: /usr/share/wayland-protocols

wpebackend-fdo-1.14.2

Introduction to wpebackend-fdo

The wpebackend-fdo package contains the Freedesktop.org backend for WPE WebKit and the WPE renderer.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://wpewebkit.org/releases/wpebackend-fdo-1.14.2.tar.xz
Download MD5 sum: dafd899646b2e31ef2d97938a638c48d
Download size: 44 KB
Estimated disk space required: 1.7 MB
Estimated build time: 0.1 SBU

wpebackend-fdo Dependencies

Required

libepoxy-1.5.10, libwpe-1.14.2, and wayland-protocols-1.33

Installation of wpebackend-fdo

Install wpebackend-fdo by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release ..
ninja

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: None

Installed Libraries: libWPEBackend-fdo-1.0.so

Installed Directories: /usr/include/wpe-fdo-1.0

Short Descriptions

libWPEBackend-fdo-1.0.so

contains functions that provide the freedesktop.org backend for WPE WebKit and the WPE renderer

wv-1.2.9

Introduction to wv

The wv package contains tools for reading information from an MS Word document.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://anduin.linuxfromscratch.org/BLFS/wv/wv-1.2.9.tar.gz
Download MD5 sum: dbccf2e9f747e50c913b7e3d126b73f7
Download size: 608 KB
Estimated disk space required: 25 MB
Estimated build time: 0.4 SBU

wv Dependencies

Required

libgsf-1.14.52 and libpng-1.6.42

Optional

libwmf

Installation of wv

Install wv by running the following commands:

./configure --prefix=/usr --disable-static &&
make

This package does not have a test suite.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: wvSummary and several other wv* programs which are deprecated in favour of abiword: see https://wvware.sourceforge.net/

Installed Library: libwv-1.2.so

Installed Directory: /usr/share/wv

Short Descriptions

wvSummary	displays the summary information from an MS Word document
`libwv-1.2.so`	provides functions to access MS Word documents

Xapian-1.4.24

Introduction to xapian

Xapian is an open source search engine library.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://oligarchy.co.uk/xapian/1.4.24/xapian-core-1.4.24.tar.xz
Download MD5 sum: f0136a41451567099ac9d2b5ff028e77
Download size: 3.0 MB
Estimated disk space required: 195 MB (add 163 MB for tests)
Estimated build time: 0.7 SBU (using parallelism=4; add 16 SBU for tests)

Xapian Dependencies

Optional

Valgrind-3.22.0 (for tests)

Installation of Xapian

Install Xapian by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir=/usr/share/doc/xapian-core-1.4.24 &&
make

To run the test suite, issue: make check.

Now, as the root user:

make install

Installed Programs: copydatabase, quest, simpleexpand, simpleindex, simplesearch, xapian-check, xapian-compact, xapian-config, xapian-delve, xapian-metadata, xapian-pos, xapian-progsrv, xapian-replicate, xapian-replicate-server and xapian-tcpsrv

Installed Libraries: libxapian.so

Installed Directories: /usr/include/xapian, /usr/lib/cmake/xapian, /usr/share/doc/xapian-core-1.4.24, and /usr/share/xapian-core

Short Descriptions

copydatabase	performs a document-by-document copy of one or more Xapian databases
quest	is a command line tool to search through a database
simpleexpand	is a simple example program demonstrating query expansion
simpleindex	indexes each paragraph of a text file as a Xapian document
simplesearch	is a simple command line search utility
xapian-check	checks the consistency of a database or table
xapian-compact	compacts a database, or merges and compacts several databases
xapian-config	reports information about the installed version of xapian
xapian-delve	inspects the contents of a Xapian database
xapian-metadata	reads and writes user metadata
xapian-pos	inspects the contents of a flint table for development or debugging
xapian-progsrv	is a remote server for use with ProgClient
xapian-replicate	replicates a database from a master server to a local copy
xapian-replicate-server	services database replication requests from clients
xapian-tcpsrv	is the TCP daemon for use with Xapian's remote backend

Chapter 10. Graphics and Font Libraries

Depending on what your system will be used for, you may or may not require the graphics and font libraries. Most desktop machines will want them for use with graphical applications. Most servers on the other hand, will not require them.

AAlib-1.4rc5

Introduction to AAlib

AAlib is a library to render any graphic into ASCII Art.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/aa-project/aalib-1.4rc5.tar.gz
Download MD5 sum: 9801095c42bba12edebd1902bcf0a990
Download size: 388 KB
Estimated disk space required: 6.5 MB
Estimated build time: 0.1 SBU

AAlib Dependencies

Optional

Xorg Libraries, Xorg Fonts (runtime), slang-2.3.3, and GPM-1.20.7

Installation of AAlib

Fix a minor problem with the included m4 file:

sed -i -e '/AM_PATH_AALIB,/s/AM_PATH_AALIB/[&]/' aalib.m4

Change the default X11 font from Xorg Legacy Fonts to Xorg Fonts:

sed -e 's/8x13bold/-*-luxi mono-bold-r-normal--13-120-*-*-m-*-*-*/' \
    -i src/aax.c

Install AAlib by running the following commands:

./configure --prefix=/usr             \
            --infodir=/usr/share/info \
            --mandir=/usr/share/man   \
            --with-ncurses=/usr       \
            --disable-static          &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: aafire, aainfo, aalib-config, aasavefont, and aatest

Installed Library: libaa.so

Installed Directories: None

Short Descriptions

aafire	is a demo of AAlib, rendering an animated fire in ASCII Art
aainfo	provides information for your current settings related to AAlib
aalib-config	provides configuration info for AAlib
aasavefont	saves a font to a file
aatest	shows the abilities of AAlib in a little test
`libaa.so`	is a collection of routines to render any graphical input in portable format to ASCII Art. It can be used through many programs and has a very well documented API, so you can easily put it into your own programs

babl-0.1.108

Introduction to Babl

The Babl package is a dynamic, any to any, pixel format translation library.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gimp.org/pub/babl/0.1/babl-0.1.108.tar.xz
Download MD5 sum: 749169721b551882332a64ac17735de6
Download size: 312 KB
Estimated disk space required: 13 MB (with tests)
Estimated build time: 0.1 SBU (Using parallelism=4; with tests)

Babl Dependencies

Optional

Little CMS-2.14 and w3m

Installation of Babl

Install Babl by running the following commands:

mkdir bld &&
cd    bld &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install &&

install -v -m755 -d                         /usr/share/gtk-doc/html/babl/graphics &&
install -v -m644 docs/*.{css,html}          /usr/share/gtk-doc/html/babl          &&
install -v -m644 docs/graphics/*.{html,svg} /usr/share/gtk-doc/html/babl/graphics

Command Explanations

install -v -m755 -d /usr/share/gtk-doc/html/babl/graphics: This and the subsequent commands install the library html documentation under /usr/share/gtk-doc/html where other gtk packages put the programmer-oriented documentation.

Installed Programs: None

Installed Libraries: libbabl-0.1.so and libraries in /usr/lib/babl-0.1

Installed Directories: /usr/{include,lib}/babl-0.1 and /usr/share/gtk-doc/html/babl

Short Descriptions

libbabl-0.1.so

contains functions to access BablFishes to convert between formats

Exiv2-0.28.2

Introduction to Exiv2

Exiv2 is a C++ library and a command line utility for managing image and video metadata.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/Exiv2/exiv2/archive/v0.28.2/exiv2-0.28.2.tar.gz
Download MD5 sum: 75a8766216a15ad104f09ab4a0eab7ca
Download size: 43 MB
Estimated disk space required: 127 MB (with tests)
Estimated build time: 0.3 SBU (Using parallelism=4, with tests)

Exiv2 dependencies

Required

c2man (to build man pages)

Optional

libssh

Optional for documentation

Doxygen-1.10.0, Graphviz-10.0.1, and libxslt-1.1.39

Installation of Exiv2

Install Exiv2 by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr  \
      -DCMAKE_BUILD_TYPE=Release   \
      -DEXIV2_ENABLE_VIDEO=yes     \
      -DEXIV2_ENABLE_WEBREADY=yes  \
      -DEXIV2_ENABLE_CURL=yes      \
      -DEXIV2_BUILD_SAMPLES=no     \
      -G "Unix Makefiles" .. &&
make

To test the results, issue: make test

Now, as the root user:

make install

Command Explanations

-DEXIV2_ENABLE_VIDEO=yes: This switch enables managing video metadata.

-DEXIV2_ENABLE_WEBREADY=yes: This switch enables managing web image metadata.

-DEXIV2_BUILD_SAMPLES=no: This switch is necessary to suppress building and installing sample programs. If the sample programs are built, 34 additional programs are installed in /usr/bin.

-DEXIV2_ENABLE_CURL=yes: This switch is necessary to enable network/http capabilities.

-DEXIV2_ENABLE_INIH=no: Use this switch if you have not installed inih-58.

-DEXIV2_ENABLE_BROTLI=no: Use this switch if you have not installed Brotli-1.1.0.

Installed Program: exiv2

Installed Library: libexiv2.so

Installed Directories: /usr/include/exiv2 and /usr/lib/cmake/exiv2

Short Descriptions

exiv2

is a utility used to dump Exif data

FreeType-2.13.2

Introduction to FreeType2

The FreeType2 package contains a library which allows applications to properly render TrueType fonts.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/freetype/freetype-2.13.2.tar.xz
Download MD5 sum: 1f625f0a913c449551b1e3790a1817d7
Download size: 2.4 MB
Estimated disk space required: 33 MB (with additional documentation)
Estimated build time: 0.2 SBU (with additional documentation)

Additional Downloads

Additional Documentation

Download (HTTP): https://downloads.sourceforge.net/freetype/freetype-doc-2.13.2.tar.xz
Download MD5 sum: e6466f08934ebf2d7f711b0464d7a6cf
Download size: 2.1 MB

FreeType2 Dependencies

Optional

Brotli-1.1.0 and librsvg-2.57.1

Optional (for documentation)

docwriter

Installation of FreeType2

If you downloaded the additional documentation, unpack it into the source tree using the following command:

tar -xf ../freetype-doc-2.13.2.tar.xz --strip-components=2 -C docs

Install FreeType2 by running the following commands:

sed -ri "s:.*(AUX_MODULES.*valid):\1:" modules.cfg &&

sed -r "s:.*(#.*SUBPIXEL_RENDERING) .*:\1:" \
    -i include/freetype/config/ftoption.h  &&

./configure --prefix=/usr --enable-freetype-config --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make install

If you downloaded the optional documentation, install it as the root user:

cp -v -R docs -T /usr/share/doc/freetype-2.13.2 &&
rm -v /usr/share/doc/freetype-2.13.2/freetype-config.1

Command Explanations

sed -ri ...: First command enables GX/AAT and OpenType table validation and second command enables Subpixel Rendering. Note that Subpixel Rendering may have patent issues. Be sure to read the 'Other patent issues' part of https://freetype.org/patents.html before enabling this option.

--enable-freetype-config: This switch ensure that the man page for freetype-config is installed.

--without-harfbuzz: If harfbuzz is installed prior to freetype without freetype support, use this switch to avoid a build failure.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: freetype-config

Installed Library: libfreetype.so

Installed Directories: /usr/include/freetype2 and /usr/share/doc/freetype-2.13.2

Short Descriptions

freetype-config	is used to get FreeType compilation and linking information
`libfreetype.so`	contains functions for rendering various font types, such as TrueType and Type1

Fontconfig-2.15.0

Introduction to Fontconfig

The Fontconfig package contains a library and support programs used for configuring and customizing font access.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/fontconfig/release/fontconfig-2.15.0.tar.xz
Download MD5 sum: 5bb3a2829aecb22ae553c39099bd0d6a
Download size: 1.4 MB
Estimated disk space required: 17 MB (with tests)
Estimated build time: 0.4 SBU (with tests)

Fontconfig Dependencies

Required

FreeType-2.13.2

Optional

bubblewrap-0.8.0 (used by some tests), cURL-8.6.0 and UnZip-6.0 (both used by some tests for downloading and extracting test files), JSON-C-0.17, DocBook-utils-0.6.14 and libxml2-2.12.5, texlive-20230313 (or install-tl-unx)

Note

An Internet connection is needed for some tests of this package.

Note

If you have DocBook Utils installed and you remove the --disable-docs parameter from the configure command below, you must have SGMLSpm-1.1 and texlive-20230313 installed also, or the Fontconfig build will fail.

Installation of Fontconfig

Install Fontconfig by running the following commands:

./configure --prefix=/usr        \
            --sysconfdir=/etc    \
            --localstatedir=/var \
            --disable-docs       \
            --docdir=/usr/share/doc/fontconfig-2.15.0 &&
make

To test the results, issue: make check. One test is known to fail if the kernel does not support user namespaces. Some tests will download some font files via Internet.

Now, as the root user:

make install

If you did not remove the --disable-docs parameter from the configure command, you can install the pre-generated documentation by using the following commands as the root user:

install -v -dm755 \
        /usr/share/{man/man{1,3,5},doc/fontconfig-2.15.0/fontconfig-devel} &&
install -v -m644 fc-*/*.1         /usr/share/man/man1 &&
install -v -m644 doc/*.3          /usr/share/man/man3 &&
install -v -m644 doc/fonts-conf.5 /usr/share/man/man5 &&
install -v -m644 doc/fontconfig-devel/* \
                                  /usr/share/doc/fontconfig-2.15.0/fontconfig-devel &&
install -v -m644 doc/*.{pdf,sgml,txt,html} \
                                  /usr/share/doc/fontconfig-2.15.0

Command Explanations

--disable-docs: This switch avoids building the documentation (the release tarball includes pre-generated documentation).

Configuring Fontconfig

Config Files

/etc/fonts/*, /etc/fonts/conf.d/* and /usr/share/fontconfig/conf.avail/*

Configuration Information

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. To put a new font directory in the configuration, create (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:

/usr/share/fonts
~/.local/share/fonts
~/.fonts (this is now deprecated, but for the moment it still works)

Fontconfig also ships many example configuration files in the /usr/share/fontconfig/conf.avail directory. Symlinking specific files to /etc/fonts/conf.d will enable them. The default setup is generally good enough for most users. See /etc/fonts/conf.d/README for a description of the configuration files.

More information about configuring Fontconfig can be found in the user's manual in file:///usr/share/doc/fontconfig-2.15.0/fontconfig-user.html.

Installed Programs: fc-cache, fc-cat, fc-conflist, fc-list, fc-match, fc-pattern, fc-query, fc-scan, and fc-validate

Installed Library: libfontconfig.so

Installed Directories: /etc/fonts, /usr/include/fontconfig, /usr/share/doc/fontconfig-2.15.0, /usr/share/fontconfig, /usr/share/xml/fontconfig, and /var/cache/fontconfig

Short Descriptions

fc-cache	is used to create font information caches
fc-cat	is used to read font information caches
fc-conflist	shows the ruleset files' information on the system
fc-list	is used to create font lists
fc-match	is used to match available fonts, or find fonts that match a given pattern
fc-pattern	is used to parse pattern (empty pattern by default) and show the parsed result
fc-query	is used to query fonts files and print resulting patterns
fc-scan	is used to scan font files and directories, and print resulting patterns
fc-validate	is used to validate font files
`libfontconfig.so`	contains functions used by the Fontconfig programs and also by other programs to configure or customize font access

FriBidi-1.0.13

Introduction to FriBidi

The FriBidi package is an implementation of the Unicode Bidirectional Algorithm (BIDI). This is useful for supporting Arabic and Hebrew alphabets in other packages.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/fribidi/fribidi/releases/download/v1.0.13/fribidi-1.0.13.tar.xz
Download MD5 sum: 49b17442e0d8fa2e97b5c898078f6f51
Download size: 1.1 MB
Estimated disk space required: 21 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

FriBidi Dependencies

Optional

Installation of FriBidi

Install FriBidi by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Program: fribidi

Installed Library: libfribidi.so

Installed Directory: /usr/include/fribidi

Short Descriptions

fribidi	is a command-line interface to the `libfribidi` library and can be used to convert a logical string to visual output
`libfribidi.so`	contains functions used to implement the Unicode Bidirectional Algorithm

gegl-0.4.48

Introduction to gegl

This package provides the GEneric Graphics Library, which is a graph based image processing format.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gimp.org/pub/gegl/0.4/gegl-0.4.48.tar.xz
Download MD5 sum: a96ae32d46855ab4eefa1fce2dbefda1
Download size: 5.5 MB
Estimated disk space required: 80 MB (Add 4 MB for tests)
Estimated build time: 0.7 SBU (add 0.1 SBU for tests, both with parallelism=4)

gegl Dependencies

Required

babl-0.1.108 and JSON-GLib-1.8.0

Optional

asciidoc-10.2.0, Cairo-1.18.0, FFmpeg-6.1.1, gdk-pixbuf-2.42.10, gexiv2-0.14.2, GTK-Doc-1.33.2, JasPer-4.2.0, Little CMS-2.14, libraw-0.21.2, librsvg-2.57.1, libtiff-4.6.0, libwebp-1.3.2, Pango-1.51.2, Poppler-24.02.0, Ruby-3.3.0, SDL2-2.30.0, v4l-utils-1.26.1, Vala-0.56.14, libspiro-20220722, LuaJIT, lensfun, LuaJIT, libnsgif, libumfpack, maxflow, MRG, OpenCL, OpenEXR, poly2tri-c, source-highlight, and w3m

Installation of gegl

If installing over a previous version of gegl, one module needs to be removed. As the root user, run:

rm -f /usr/lib/gegl-0.4/vector-fill.so

Install gegl by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To run the tests, issue: ninja test. 7 tests in the gegl:ff-load-save portion of the test suite are known to fail due to incompatibilities with ffmpeg-6.0.

Now, as the root user:

ninja install

Command Explanations

-Ddocs=true: Build and install documentation (requires GTK-Doc-1.33.2,).

Installed Programs: gegl and gegl-imgcmp

Installed Libraries: libgegl-0.4.so, libgegl-npd-0.4.so, and modules in /usr/lib/gegl-0.4

Installed Directories: /usr/lib/gegl-0.4 and /usr/include/gegl-0.4

Short Descriptions

gegl	is a commandline tool for working with the XML data model
gegl-imgcmp	is a simple image difference detection tool for use in regression testing
`libgegl-0.4.so`	provides infrastructure to do demand based cached non destructive image editing on larger than RAM buffers
`libgegl-npd-0.4.so`	is the GEGL N-point image deformation library

giflib-5.2.1

Introduction to giflib

The giflib package contains libraries for reading and writing GIFs as well as programs for converting and working with GIF files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://sourceforge.net/projects/giflib/files/giflib-5.2.1.tar.gz
Download MD5 sum: 6f03aee4ebe54ac2cc1ab3e4b0a049e5
Download size: 436 KB
Estimated disk space required: 3.2 MB (with documentation)
Estimated build time: less than 0.1 SBU (with documentation)

giflib Dependencies

Required

xmlto-0.0.28

Installation of giflib

Install giflib by running the following commands:

make

This package does not come with a test suite.

Now, as the root user:

make PREFIX=/usr install &&

rm -fv /usr/lib/libgif.a &&

find doc \( -name Makefile\* -o -name \*.1 \
         -o -name \*.xml \) -exec rm -v {} \; &&

install -v -dm755 /usr/share/doc/giflib-5.2.1 &&
cp -v -R doc/* /usr/share/doc/giflib-5.2.1

Command Explanations

rm -fv /usr/lib/libgif.a: This command removes a static library which is not used by any BLFS package.

find doc ... -exec rm -v {} \;: This command removes Makefiles, man and xml files from the documentation directory that would otherwise be installed by the commands that follow.

Installed Programs: gif2rgb, gifbuild, gifclrmp, giffix, giftext, and giftool

Installed Library: libgif.so

Installed Directory: /usr/share/doc/giflib-5.2.1

Short Descriptions

gif2rgb	converts images saved as GIF to 24-bit RGB images
gifbuild	dumps GIF data in a textual format, or undumps it to a GIF
gifclrmp	modifies GIF image colormaps
giffix	clumsily attempts to fix truncated GIF images
giftext	prints (text only) general information about a GIF file
giftool	is a GIF transformation tool
`libgif.so`	contains API functions required by the giflib programs and any other programs needing library functionality to read, write and manipulate GIF images

Glad-2.0.5

Introduction to Glad

The Glad package contains a generator for loading Vulkan, OpenGL, EGL, GLES, and GLX contexts.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/Dav1dde/glad/archive/refs/tags/v2.0.5/glad-2.0.5.tar.gz
Download MD5 sum: 7bd99cc337608d9cad42b861ccc0e28e
Download size: 620 KB
Estimated disk space required: 36 MB
Estimated build time: less than 0.1 SBU

Glad Dependencies

Optional (required to run the tests)

pytest-8.0.0, rustc-1.76.0, Xorg Libraries, glfw, and WINE

Installation of Glad

Install Glad by running the following commands:

pip3 wheel -w dist --no-build-isolation --no-deps --no-cache-dir $PWD

This package comes with a test suite, but it cannot be run without installing the external dependencies listed above.

Now, as the root user:

pip3 install --no-index --find-links=dist --no-cache-dir --no-user glad2

Installed Programs: glad

Installed Libraries: None

Installed Directories: /usr/lib/python3.12/site-packages/glad and /usr/lib/python3.12/site-packages/glad2-2.0.5.dist-info

Short Descriptions

glad

generates loaders for Vulkan, OpenGL, EGL, GLES, and GLX contexts

GLM-1.0.0

Introduction to GLM

OpenGL Mathematics (GLM) is a header-only C++ mathematics library for graphics software based on the OpenGL Shading Language (GLSL) specifications. An extension system provides extended capabilities such as matrix transformations and quaternions.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/g-truc/glm/archive/1.0.0/glm-1.0.0.tar.gz
Download MD5 sum: 61f6cd584a7489a0d4c8152191d5d2fa
Download size: 4.3 MB
Estimated disk space required: 44 MB
Estimated build time: less than 0.1 SBU

Installation of GLM

Note

This package is unusual as it includes its functionality in header files. We just copy them into position.

As the root user:

cp -r glm /usr/include/ &&
cp -r doc /usr/share/doc/glm-1.0.0

Installed Program: None

Installed Library: None

Installed Directory: /usr/include/glm and /usr/share/doc/glm-1.0.0

Graphite2-1.3.14

Introduction to Graphite2

Graphite2 is a rendering engine for graphite fonts. These are TrueType fonts with additional tables containing smart rendering information and were originally developed to support complex non-Roman writing systems. They may contain rules for e.g. ligatures, glyph substitution, kerning, justification - this can make them useful even on text written in Roman writing systems such as English. Note that firefox by default provides an internal copy of the graphite engine and cannot use a system version (although it can now be patched to use it), but it too should benefit from the availability of graphite fonts.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/silnrsi/graphite/releases/download/1.3.14/graphite2-1.3.14.tgz
Download MD5 sum: 1bccb985a7da01092bfb53bb5041e836
Download size: 6.3 MB
Estimated disk space required: 30 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Graphite2 Dependencies

Required

Optional

FreeType-2.13.2, silgraphite to build the comparerender test and benchmarking tool, and if that is present, and HarfBuzz-8.3.0 to add more functionality to it (this is a circular dependency, you would need to first build graphite2 without harfbuzz).

To build the documentation: asciidoc-10.2.0, Doxygen-1.10.0, texlive-20230313 (or install-tl-unx), and dblatex (for PDF docs)

To execute the test suite you will need FontTools (Python 3 module), otherwise, the "cmp" tests fail.

Optional (at runtime)

You will need at least one suitable graphite font for the package to be useful.

Installation of Graphite2

Some tests fail if FontTools (Python 3 module) is not installed. These tests can be removed with:

sed -i '/cmptest/d' tests/CMakeLists.txt

Install Graphite2 by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr .. &&
make

If you wish to build the documentation, issue:

make docs

To test the results, issue: make test. One test named nametabletest is known to fail.

Now, as the root user:

make install

If you built the documentation, install, as the root user:

install -v -d -m755 /usr/share/doc/graphite2-1.3.14 &&

cp      -v -f    doc/{GTF,manual}.html \
                    /usr/share/doc/graphite2-1.3.14 &&
cp      -v -f    doc/{GTF,manual}.pdf \
                    /usr/share/doc/graphite2-1.3.14

Command Explanations

-DCMAKE_VERBOSE_MAKEFILE=ON: This switch turns on build verbose mode.

Installed Programs: gr2fonttest, and optionally comparerender

Installed Libraries: libgraphite2.so

Installed Directories: /usr/{include,share}/graphite2 and optionally /usr/share/doc/graphite2-1.3.14

Short Descriptions

comparerender	is a test and benchmarking tool
gr2fonttest	is a diagnostic console tool for graphite fonts
`libgraphite2.so`	is a rendering engine for graphite fonts

HarfBuzz-8.3.0

Introduction to Harfbuzz

The HarfBuzz package contains an OpenType text shaping engine.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/harfbuzz/harfbuzz/releases/download/8.3.0/harfbuzz-8.3.0.tar.xz
Download MD5 sum: 7bf11a21c51a4f3ce0728decc4c557d4
Download size: 18 MB
Estimated disk space required: 153 MB (with tests)
Estimated build time: 0.8 SBU (Using parallelism=4; with tests)

HarfBuzz Dependencies

Optional

Cairo-1.18.0 (circular: build cairo and all its recommended dependencies, including harfbuzz, first, then rebuild harfbuzz if the cairo backend is needed), git-2.44.0, GTK-Doc-1.33.2, FontTools (Python 3 module, for the test suite), ragel, and wasm-micro-runtime

Warning

Recommended dependencies are not strictly required to build the package. However, you might not get expected results at runtime if you don't install them. Please do not report bugs with this package if you have not installed the recommended dependencies.

Installation of HarfBuzz

Install HarfBuzz by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Dgraphite2=enabled &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dgraphite2=enabled: This switch enables Graphite2 support, which is required for building texlive-20230313 or LibreOffice-24.2.0.3 with system harfbuzz.

-Ddocs=disabled: If GTK-Doc-1.33.2 is installed, the documentation is built and installed. This switch prevents that.

Installed Programs: hb-info, hb-ot-shape-closure, hb-shape, hb-subset, and hb-view (only if Cairo is installed)

Installed Libraries: libharfbuzz.so, libharfbuzz-cairo.so (only if Cairo is installed), libharfbuzz-gobject.so, libharfbuzz-icu.so, and libharfbuzz-subset.so

Installed Directories: /usr/include/harbuzz, /usr/lib/cmake/harfbuzz, and /usr/share/gtk-doc/html/harfbuzz (optional)

Short Descriptions

hb-info	is used for gathering information about fonts installed on the system
hb-ot-shape-closure	gives the set of characters contained in a string, represented as single characters and/or single character names. Example: hb-ot-shape-closure /usr/share/fonts/dejavu/DejaVuSans.ttf "Hello World."
hb-shape	is used for the conversion of text strings into positioned glyphs
hb-subset	is used to create subsets of fonts, and display text using them
hb-view	displays a graphical view of a string shape using a particular font as a set of glyphs. The output format is automatically defined by the file extension, the supported ones being ansi/png/svg/pdf/ps/eps. For example: hb-view --output-file=hello.png /usr/share/fonts/dejavu/DejaVuSans.ttf "Hello World."
`libharfbuzz.so`	is the HarfBuzz text shaping library
`libharfbuzz-cairo.so`	provides Cairo integration for the Harfbuzz text shaping library
`libharfbuzz-gobject.so`	provides GObject integration for the HarfBuzz text shaping library
`libharfbuzz-icu.so`	provides ICU integration for the HarfBuzz text shaping library
`libharfbuzz-subset.so`	provides API functions for performing subsetting operations on font files

JasPer-4.2.0

Introduction to JasPer

The JasPer Project is an open-source initiative to provide a free software-based reference implementation of the JPEG-2000 codec.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/jasper-software/jasper/archive/version-4.2.0/jasper-4.2.0.tar.gz
Download MD5 sum: 14e0fe33bf708603de4966026aa2695d
Download size: 1.9 MB
Estimated disk space required: 10.0 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

JasPer Dependencies

Required

Optional

Freeglut-3.4.0 (required for jiv), Doxygen-1.10.0 (needed for generating html documentation), and texlive-20230313 (needed to regenerate the pdf documentation)

Installation of JasPer

Note

The tarball jasper-4.2.0.tar.gz will extract to jasper-version-4.2.0.

Install JasPer by running the following commands:

mkdir BUILD &&
cd    BUILD &&

cmake -DCMAKE_INSTALL_PREFIX=/usr    \
      -DCMAKE_BUILD_TYPE=Release     \
      -DCMAKE_SKIP_INSTALL_RPATH=YES \
      -DJAS_ENABLE_DOC=NO            \
      -DALLOW_IN_SOURCE_BUILD=YES    \
      -DCMAKE_INSTALL_DOCDIR=/usr/share/doc/jasper-4.2.0 \
      ..  &&
make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

-DCMAKE_SKIP_INSTALL_RPATH=YES: This option removes embedded library search paths.

-DJAS_ENABLE_DOC=NO: This option disables rebuilding the pdf documentation if texlive-20230313 is installed.

-DALLOW_IN_SOURCE_BUILD=YES: This switch allows building from within the source tree. In our case, this is needed to allow us to build inside of the BUILD directory instead of needing to create another directory outside of the source tree.

Installed Programs: imgcmp, imginfo, jasper, and jiv

Installed Library: libjasper.so

Installed Directories: /usr/include/jasper and /usr/share/doc/jasper-4.2.0

Short Descriptions

imgcmp	compares two images of the same geometry
imginfo	displays information about an image
jasper	converts images between formats (BMP, JPS, JPC, JPG, PGX, PNM, MIF, and RAS)
jiv	displays images
`libjasper.so`	is a library used by programs for reading and writing JPEG2000 format files

Little CMS-2.14

Introduction to Little CMS2

The Little Color Management System is a small-footprint color management engine, with special focus on accuracy and performance. It uses the International Color Consortium standard (ICC), which is the modern standard for color management.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/mm2/Little-CMS/releases/download/lcms2.14/lcms2-2.14.tar.gz
Download MD5 sum: 7f7baa3e605c961b9301135105ee9a34
Download size: 7.1 MB
Estimated disk space required: 20 MB (with the tests)
Estimated build time: 0.2 SBU (with the tests)

Little CMS2 Dependencies

Optional

libjpeg-turbo-3.0.1 and libtiff-4.6.0

Installation of Little CMS2

Apply the upstream fix for an issue breaking colord:

sed '/BufferSize < TagSize/,+1 s/goto Error/TagSize = BufferSize/' \
    -i src/cmsio0.c

Install Little CMS2 by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: jpgicc, linkicc, psicc, tificc, and transicc

Installed Library: liblcms2.so

Installed Directories: None

Short Descriptions

jpgicc	is the Little CMS ICC profile applier for JPEG
linkicc	is the Little CMS ICC device link generator
psicc	is the Little CMS ICC PostScript generator
tificc	is the Little CMS ICC tiff generator
transicc	is the Little CMS ColorSpace conversion calculator
`liblcms2.so`	contains functions that implement the lcms2 API

libavif-1.0.4

Introduction to libavif

The libavif package contains a library used for encoding and decoding AVIF files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/AOMediaCodec/libavif/archive/v1.0.4/libavif-1.0.4.tar.gz
Download MD5 sum: 8c786fd21f8757ace8cc011401e4d420
Download size: 11 MB
Estimated disk space required: 16 MB
Estimated build time: less than 0.1 SBU

libavif Dependencies

Required

libaom-3.8.1

Optional

gtest, libdav1d, libyuv, rav1e, and svt-av1

Installation of libavif

Install libavif by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      -DAVIF_CODEC_AOM=ON         \
      -DAVIF_BUILD_GDK_PIXBUF=ON  \
      -G Ninja .. &&
ninja

This package does come with a test suite, but it requires gtest, which is not part of BLFS.

Now, as the root user:

ninja install

The AV1 format needs to be added to the loaders cache. As the root user:

gdk-pixbuf-query-loaders --update-cache

Command Explanations

-DAVIF_CODEC_AOM=ON: This switch enables using the AOM codec. This package is useless without at least one codec built in.

-DAVIF_BUILD_GDK_PIXBUF=ON: This switch builds the AVIF loader for applications which use gdk-pixbuf. Remove it if you have not installed gdk-pixbuf-2.42.10.

-DAVIF_CODEC_DAV1D=ON: Use this switch if you have installed libdav1d and wish to use it as a codec.

-DAVIF_CODEC_RAV1E=ON: Use this switch if you have installed rav1e and wish to use it as a codec.

-DAVIF_CODEC_SVT=ON: Use this switch if you have installed svt-av1 and wish to use it as a codec.

Installed Programs: None

Installed Libraries: libavif.so and libpixbbufloader-avif.so (in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders)

Installed Directories: /usr/include/avif and /usr/lib/cmake/libavif

Short Descriptions

`libavif.so`	contains functions that provide a portable C implementation of the AV1 Image Format
`libpixbufloader-avif.so`	allows applications which use gdk-pixbuf to read AVIF images

libexif-0.6.24

Introduction to libexif

The libexif package contains a library for parsing, editing, and saving EXIF data. Most digital cameras produce EXIF files, which are JPEG files with extra tags that contain information about the image. All EXIF tags described in EXIF standard 2.1 are supported.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/libexif/libexif/releases/download/v0.6.24/libexif-0.6.24.tar.bz2
Download MD5 sum: 00ea6e7ff62d3fd41ea9b2139746703c
Download size: 1.9 MB
Estimated disk space required: 17 MB
Estimated build time: 0.1 SBU

libexif Dependencies

Optional (to Build Documentation)

Doxygen-1.10.0 and Graphviz-10.0.1

Installation of libexif

Install libexif by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --with-doc-dir=/usr/share/doc/libexif-0.6.24 &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Documentation was built and installed if you have the dependencies shown above installed. If you don't have the dependencies installed, there is a compressed tarball in the source tree doc directory that can be unpacked into /usr/share/doc/libexif-0.6.24.

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libexif.so

Installed Directories: /usr/include/libexif and /usr/share/doc/libexif-0.6.24

Short Descriptions

libexif.so

contains functions used for parsing, editing, and saving EXIF data

Libgxps-0.3.2

Introduction to libgxps

The libgxps package provides an interface to manipulate XPS documents.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/libgxps/0.3/libgxps-0.3.2.tar.xz
Download MD5 sum: 0527ac7c8c405445e96a5baa6019a0c3
Download size: 80 KB
Estimated disk space required: 5.4 MB
Estimated build time: 0.1 SBU

Libgxps Dependencies

Required

GTK+-3.24.41, Little CMS-2.14, libarchive-3.7.2, libjpeg-turbo-3.0.1, libtiff-4.6.0, and libxslt-1.1.39

Optional

git-2.44.0 and GTK-Doc-1.33.2

Installation of Libgxps

Install Libgxps by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: xpstojpeg, xpstopdf, xpstopng, xpstops, and xpstosvg

Installed Library: libgxps.so

Installed Directories: /usr/include/libgxps

Short Descriptions

xpstojpeg	converts XPS documents to a JPEG image
xpstopdf	converts XPS documents to PDF format
xpstopng	converts XPS documents to a PNG image
xpstops	converts XPS documents to PostScript
xpstosvg	converts XPS documents to SVG images
`libgxps.so`	contains API functions for manipulating XPS documents

libjpeg-turbo-3.0.1

Introduction to libjpeg-turbo

libjpeg-turbo is a fork of the original IJG libjpeg which uses SIMD to accelerate baseline JPEG compression and decompression. libjpeg is a library that implements JPEG image encoding, decoding and transcoding.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/libjpeg-turbo/libjpeg-turbo-3.0.1.tar.gz
Download MD5 sum: 1fdc6494521a8724f5f7cf39b0f6aff3
Download size: 2.7 MB
Estimated disk space required: 55 MB (with tests)
Estimated build time: 0.5 SBU (with tests; both using parallelism=4)

libjpeg-turbo Dependencies

Required

Installation of libjpeg-turbo

Install libjpeg-turbo by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr        \
      -DCMAKE_BUILD_TYPE=RELEASE         \
      -DENABLE_STATIC=FALSE              \
      -DCMAKE_INSTALL_DEFAULT_LIBDIR=lib \
      -DCMAKE_INSTALL_DOCDIR=/usr/share/doc/libjpeg-turbo-3.0.1 \
      .. &&
make

To test the results, issue: make test.

Now, as the root user:

make install

Command Explanations

-DWITH_JPEG8=ON: This switch enables compatibility with libjpeg version 8.

Installed Programs: cjpeg, djpeg, jpegtran, rdjpgcom, tjbench, and wrjpgcom

Installed Libraries: libjpeg.so and libturbojpeg.so

Installed Directories: /usr/share/doc/libjpeg-turbo-3.0.1

Short Descriptions

cjpeg	compresses image files to produce a JPEG/JFIF file on the standard output. Currently supported input file formats are: PPM (PBMPLUS color format), PGM (PBMPLUS gray-scale format), BMP, and Targa
djpeg	decompresses image files from JPEG/JFIF format to either PPM (PBMPLUS color format), PGM (PBMPLUS gray-scale format), BMP, or Targa format
jpegtran	is used for lossless transformation of JPEG files
rdjpgcom	displays text comments from within a JPEG file
tjbench	is used to benchmark the performance of libjpeg-turbo
wrjpgcom	inserts text comments into a JPEG file
`libjpeg.so`	contains functions used for reading and writing JPEG images

libmng-2.0.3

Introduction to libmng

The libmng libraries are used by programs wanting to read and write Multiple-image Network Graphics (MNG) files which are the animation equivalents to PNG files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/libmng/libmng-2.0.3.tar.xz
Download MD5 sum: e9e899adb1b681b17f14d91e261878c5
Download size: 932 KB
Estimated disk space required: 15 MB
Estimated build time: 0.1 SBU

libmng Dependencies

Required

libjpeg-turbo-3.0.1 and Little CMS-2.14

Installation of libmng

Install libmng by running the following commands:

./configure --prefix=/usr --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&

install -v -m755 -d        /usr/share/doc/libmng-2.0.3 &&
install -v -m644 doc/*.txt /usr/share/doc/libmng-2.0.3

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libmng.so

Installed Directory: /usr/share/doc/libmng-2.0.3

Short Descriptions

libmng.so

provides functions for programs wishing to read and write MNG files which are animation files without the patent problems associated with certain other formats

libmypaint-1.6.1

Introduction to libmypaint

The libmypaint package, a.k.a. "brushlib", is a library for making brushstrokes which is used by MyPaint and other projects.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/mypaint/libmypaint/releases/download/v1.6.1/libmypaint-1.6.1.tar.xz
Download MD5 sum: 7f1dab2d30ce8a3f494354c7c77a2977
Download size: 508 KB
Estimated disk space required: 11 MB (add 1 MB for tests)
Estimated build time: 0.1 SBU (add 0.3 SBU for tests)

libmypaint Dependencies

Required

JSON-C-0.17

Optional

Doxygen-1.10.0 (to create XML docs), gegl (0.3 versions only) and gperftools

Installation of libmypaint

Install libmypaint by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Programs: None.

Installed Libraries: libmypaint.so (and optionally libmypaint-gegl.so which is not used by any packages in this book).

Installed Directory: /usr/include/libmypaint

Short Descriptions

libmypaint.so

contains functions for making brushstrokes

libpng-1.6.42

Introduction to libpng

The libpng package contains libraries used by other programs for reading and writing PNG files. The PNG format was designed as a replacement for GIF and, to a lesser extent, TIFF, with many improvements and extensions and lack of patent problems.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/libpng/libpng-1.6.42.tar.xz
Download MD5 sum: c580b12b1a8c040b13c35f324a636bb6
Download size: 1.0 MB
Estimated disk space required: 14 MB (with tests)
Estimated build time: 0.1 SBU (add 0.5 SBU for tests)

Additional Downloads

Recommended patch to include animated png functionality in libpng (required to use the system libpng in Firefox, Seamonkey, and Thunderbird): https://downloads.sourceforge.net/sourceforge/libpng-apng/libpng-1.6.40-apng.patch.gz
Patch md5sum: c6e309802ada5ed814a6a553161d8fe6

Installation of libpng

If you want to patch libpng to support apng files, apply it here:

gzip -cd ../libpng-1.6.40-apng.patch.gz | patch -p1

Install libpng by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install &&
mkdir -v /usr/share/doc/libpng-1.6.42 &&
cp -v README libpng-manual.txt /usr/share/doc/libpng-1.6.42

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: libpng-config (symlink), libpng16-config, pngfix and png-fix-itxt

Installed Libraries: libpng.so

Installed Directories: /usr/include/libpng16 and /usr/share/doc/libpng-1.6.42

Short Descriptions

pngfix	tests, optimizes and optionally fixes the zlib header in PNG files. Optionally, when fixing, strips ancillary chunks from the file
png-fix-itxt	fixes PNG files that have an incorrect length field in the iTXt chunks
libpng-config	is a shell script that provides configuration information for applications wanting to use libpng
`libpng.so`	contain routines used to create and manipulate PNG format graphics files

libraw-0.21.2

Introduction to libraw

Libraw is a library for reading RAW files obtained from digital photo cameras (CRW/CR2, NEF, RAF, DNG, and others).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.libraw.org/data/LibRaw-0.21.2.tar.gz
Download MD5 sum: 0533724bad17c0fde22e642e4594e45d
Download size: 1.6 MB
Estimated disk space required: 30 MB
Estimated build time: 0.2 SBU (Using parallelism=4)

libraw Dependencies

Installation of libraw

Install libraw by running the following commands:

autoreconf -fiv              &&
./configure --prefix=/usr    \
            --enable-jpeg    \
            --enable-jasper  \
            --enable-lcms    \
            --disable-static \
            --docdir=/usr/share/doc/libraw-0.21.2 &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--enable-jpeg: This switch enables support for jpeg. Remove if you don't have libjpeg-turbo-3.0.1 installed.

--enable-jasper: This switch enables support for jasper. Remove if you don't have JasPer-4.2.0 installed.

--enable-lcms: This switch enables support for Little CMS2. Remove if you don't have Little CMS-2.14 installed.

--disable-static: This switch prevents installation of static versions of the libraries.

Note

All the installed programs are examples of using libraw.

Installed Programs: 4channels, dcraw_emu, dcraw_half, half_mt, mem_image, multirender_test, postprocessing_benchmark, raw-identify, simple_dcraw, and unprocessed_raw

Installed Library: libraw.so and libraw_r.so

Installed Directories: /usr/include/libraw and /usr/share/doc/libraw-0.21.2

Short Descriptions

4channels	generates four TIFF files from RAW data, one file per channel
dcraw_half	emulates "dcraw -h" (see DCRAW manpage)
mem_image	emulates "dcraw [-4] [-6] [-e]" (see DCRAW manpage)
postprocessing_benchmark	creates eight different renderings from one source file. The first and fourth one should be identical
simple_dcraw	emulates call to "dcraw [-D] [-T] [-v] [-e] [-4]" (see DCRAW manpage)
dcraw_emu	is an almost complete dcraw emulator (see DCRAW manpage)
half_mt	emulates call to "dcraw -h [-w] [-a] [-v]" (see DCRAW manpage)
multirender_test	creates eight different renderings from one source file. The first and fourth one should be identical
raw-identify	emulates call to "dcraw -i [-v]" (see DCRAW manpage)
unprocessed_raw	generates unprocessed raw image: with masked pixels and without black subtraction

librsvg-2.57.1

Introduction to librsvg

The librsvg package contains a library and tools used to manipulate, convert and view Scalable Vector Graphic (SVG) images.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/librsvg/2.57/librsvg-2.57.1.tar.xz
Download MD5 sum: 0a9d809a4bdd371c894792e4c2eb94e9
Download size: 5.4 MB
Estimated disk space required: 998 MB (16 MB installed), add 589 MB for tests
Estimated build time: 1.2 SBU (add 0.5 SBU for tests; both using parallelism=4)

librsvg Dependencies

Required

Cairo-1.18.0, gdk-pixbuf-2.42.10, Pango-1.51.2, and rustc-1.76.0

Note

An Internet connection is needed for building this package.

Optional

docutils-0.20.1 (for man pages), Gi-DocGen-2023.3 (for documentation), and Xorg Fonts (for tests)

Installation of librsvg

Install librsvg by running the following commands:

./configure --prefix=/usr    \
            --enable-vala    \
            --disable-static \
            --docdir=/usr/share/doc/librsvg-2.57.1 &&
make

To test the results, issue: LC_ALL=C make -k check.

Now, as the root user:

make DOC_INSTALL_DIR='$(docdir)' install

Note

If you installed the package on to your system using a “DESTDIR” method, an important file was not installed and should be copied and/or generated. Generate it using the following command as the root user:

gdk-pixbuf-query-loaders --update-cache

Command Explanations

--enable-vala: This switch enables building of the Vala bindings. Remove this switch if you don't have Vala-0.56.14 installed.

--disable-static: This switch prevents installation of static versions of the libraries.

DOC_INSTALL_DIR='$(docdir)': This override ensures installing the API documentation into the expected location if Gi-DocGen-2023.3 is installed.

--disable-introspection: Use this switch if you have not installed Gobject Introspection.

--disable-gtk-doc: This switch prevents building the API documentation, even if Gi-DocGen-2023.3 (despite the name of the option) is available.

Installed Programs: rsvg-convert

Installed Library: librsvg-2.so and libpixbufloader-svg.so (installed in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders)

Installed Directories: /usr/include/librsvg-2.0 and /usr/share/doc/librsvg-2.57.1

Short Descriptions

rsvg-convert	is used to convert images into PNG, PDF, PS, SVG and other formats
`librsvg-2.so`	provides the functions to render Scalable Vector Graphics
`libpixbufloader-svg.so`	is the Gdk Pixbuf plugin that allows GTK+ applications to render Scalable Vector Graphics images

Libspiro-20220722

Introduction to libspiro

Libspiro will take an array of spiro control points and convert them into a series of bezier splines which can then be used in the myriad of ways the world has come to use beziers.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/fontforge/libspiro/releases/download/20220722/libspiro-dist-20220722.tar.gz
Download MD5 sum: c21f86e6c1ad65ed4cb1f754f6d7563c
Download size: 428 KB
Estimated disk space required: 5.1 MB (add 1.3 MB if running the tests)
Estimated build time: 0.1 SBU

Installation of libspiro

Install libspiro by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Library: libspiro.so

Installed Directories: None

Short Descriptions

libspiro.so

is a shareable library that can be used by programs to do the Spiro computations for you

libtiff-4.6.0

Introduction to libtiff

The libtiff package contains the TIFF libraries and associated utilities. The libraries are used by many programs for reading and writing TIFF files and the utilities are used for general work with TIFF files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.osgeo.org/libtiff/tiff-4.6.0.tar.gz
Download MD5 sum: fc7d49a9348b890b29f91a4ecadd5b49
Download size: 3.4 MB
Estimated disk space required: 46 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

libtiff Dependencies

Optional

Freeglut-3.4.0 (required for tiffgt), libjpeg-turbo-3.0.1, sphinx-7.2.6, libwebp-1.3.2, JBIG-KIT, and LERC

Installation of libtiff

Install libtiff by running the following commands:

mkdir -p libtiff-build &&
cd       libtiff-build &&

cmake -DCMAKE_INSTALL_DOCDIR=/usr/share/doc/libtiff-4.6.0 \
      -DCMAKE_INSTALL_PREFIX=/usr -G Ninja .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Installed Programs: tiffcp, tiffdump, tiffinfo, tiffset, and tiffsplit

Installed Libraries: libtiff.so and libtiffxx.so

Installed Directory: /usr/share/doc/tiff-4.6.0

Short Descriptions

tiffcp	copies (and possibly converts) a TIFF file
tiffdump	prints verbatim information about TIFF files
tiffinfo	prints information about TIFF files
tiffset	sets the value of a TIFF header to a specified value
tiffsplit	splits a multi-image TIFF into single-image TIFF files
`libtiff.so`	contains the API functions used by the libtiff programs as well as other programs to read and write TIFF files
`libtiffxx.so`	contains the C++ API functions used by programs to read and write TIFF files

libwebp-1.3.2

Introduction to libwebp

The libwebp package contains a library and support programs to encode and decode images in WebP format.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://storage.googleapis.com/downloads.webmproject.org/releases/webp/libwebp-1.3.2.tar.gz
Download MD5 sum: 34869086761c0e2da6361035f7b64771
Download size: 4.0 MB
Estimated disk space required: 45 MB
Estimated build time: 0.1 SBU (with parallelism=4)

libwebp Dependencies

Optional

Freeglut-3.4.0 and giflib-5.2.1

Installation of libwebp

Install libwebp by running the following commands:

./configure --prefix=/usr           \
            --enable-libwebpmux     \
            --enable-libwebpdemux   \
            --enable-libwebpdecoder \
            --enable-libwebpextras  \
            --enable-swap-16bit-csp \
            --disable-static        &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--enable-swap-16bit-csp: This switch enables byte swap for 16 bit colorspaces.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: cwebp, dwebp, gif2webp, img2webp, vwebp, webpinfo, and webpmux

Installed Library: libsharpyuv.so, libwebpdecoder.so, libwebpdemux.so, libwebpmux.so, and libwebp.so

Installed Directory: /usr/include/webp

Short Descriptions

cwebp	compresses an image using the WebP format
dwebp	decompresses WebP files into PNG, PAM, PPM or PGM images
gif2webp	converts a GIF image to a WebP image
img2webp	creates an animated WebP file from a sequence of input images
vwebp	decompresses a WebP file and displays it in a window
webpinfo	prints out the cunk level structure of WebP files along with performing basic integrity checks
webpmux	creates animated WebP files from non-animated WebP images, extracts frames from animated WebP images, and manages XMP/EXIF metadata and the ICC profile
`libwebp.so`	contains the API functions for WebP encoding and decoding

mypaint-brushes-1.3.1

Introduction to mypaint-brushes

The mypaint-brushes package contains brushes used by packages which use libmypaint.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/mypaint/mypaint-brushes/releases/download/v1.3.1/mypaint-brushes-1.3.1.tar.xz
Download MD5 sum: 7241032d814cb91d2baae7d009a2a2e0
Download size: 1.3 MB
Estimated disk space required: 3.4 MB
Estimated build time: less than 0.1 SBU

mypaint-brushes Dependencies

Required at runtime

libmypaint-1.6.1

Installation of mypaint-brushes

Install mypaint-brushes by running the following commands:

./configure --prefix=/usr &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: None.

Installed Libraries: None.

Installed Directories: /usr/share/mypaint-data.

newt-0.52.24

Introduction to newt

Newt is a programming library for color text mode, widget based user interfaces. It can be used to add stacked windows, entry widgets, checkboxes, radio buttons, labels, plain text fields, scrollbars, etc., to text mode user interfaces. Newt is based on the S-Lang library.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://releases.pagure.org/newt/newt-0.52.24.tar.gz
Download MD5 sum: 9a0630e2f59eaa3037aec94989c36c4a
Download size: 176 KB
Estimated disk space required: 3.0 MB
Estimated build time: less than 0.1 SBU

Newt Dependencies

Required

popt-1.19 and slang-2.3.3

Installation of newt

Install newt by running the following command:

sed -e '/install -m 644 $(LIBNEWT)/ s/^/#/' \
    -e '/$(LIBNEWT):/,/rv/ s/^/#/'          \
    -e 's/$(LIBNEWT)/$(LIBNEWTSH)/g'        \
    -i Makefile.in                          &&

./configure --prefix=/usr           \
            --with-gpm-support      \
            --with-python=python3.12 &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

sed -e ... -i Makefile.in: Disables installation of a static library.

--with-gpm-support: This switch enables mouse support for newt applications through GPM.

--with-python=python3.12: By giving explicitly the name of the directory where python modules reside, this switch prevents building the python2 module.

Installed Programs: whiptail

Installed Library: libnewt.so, whiptcl.so, and /usr/lib/python3.12/site-packages/_snack.so

Installed Directories: None

Short Descriptions

whiptail	displays dialog boxes from shell scripts
`libnewt.so`	is the library for color text mode, widget based user interfaces

opencv-4.9.0

Introduction to opencv

The opencv package contains graphics libraries mainly aimed at real-time computer vision.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/opencv/opencv/archive/4.9.0/opencv-4.9.0.tar.gz
Download MD5 sum: 153b4b8dd103b1bfe447f7dd1f22eac0
Download size: 88 MB
Estimated disk space required: 820 MB
Estimated build time: 7.4 SBU (using parallelism=4)

Additional Downloads

Optional additional modules: https://github.com/opencv/opencv_contrib/archive/4.9.0/opencv_contrib-4.9.0.tar.gz

Note

One additional file that starts with "ippicv" (integrated performance primitives) will be automatically downloaded during the cmake portion of the build procedure. This download is specific to the system architecture.

opencv Dependencies

Required

CMake-3.28.3 and UnZip-6.0

Optional

apache-ant-1.10.14, Doxygen-1.10.0, Java-21.0.2, NumPy-1.26.4, ATLAS, blas, Cuda, Eigen, OpenEXR, GDAL, lapack, libdc1394, Threading Building Blocks (TBB), and VTK - The Visualization Toolkit,

Installation of opencv

If you downloaded the optional modules, unpack them now:

tar -xf ../opencv_contrib-4.9.0.tar.gz

Install opencv by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr      \
      -DCMAKE_BUILD_TYPE=Release       \
      -DENABLE_CXX11=ON                \
      -DBUILD_PERF_TESTS=OFF           \
      -DWITH_XINE=ON                   \
      -DBUILD_TESTS=OFF                \
      -DENABLE_PRECOMPILED_HEADERS=OFF \
      -DCMAKE_SKIP_RPATH=ON            \
      -DBUILD_WITH_DEBUG_INFO=OFF      \
      -Wno-dev  ..                     &&
make

The package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

-DWITH_XINE=ON: This option instructs the make procedure to use xine-lib-1.2.13.

-DENABLE_PRECOMPILED_HEADERS=OFF: This option is needed for compatibility with gcc-6.1 and later.

-DOPENCV_EXTRA_MODULES_PATH=../opencv_contrib-4.9.0/modules: instructs the build system to build additional modules.

Installed Programs: opencv_annotation, opencv_interactive-calibration, opencv_model_diagnostics, opencv_version, opencv_visualisation, and setup_vars_opencv4.sh

Installed Libraries: libopencv_calib3d.so, libopencv_core.so, libopencv_dnn.so, libopencv_features2d.so, libopencv_flann.so, libopencv_gapi.so, libopencv_highgui.so, libopencv_imgcodecs.so, libopencv_imgproc.so, libopencv_ml.so, libopencv_objdetect.so, libopencv_photo.so, libopencv_stitching.so, libopencv_video.so, and libopencv_videoio.so

Installed Directories: /usr/include/opencv4, /usr/lib/cmake/opencv4, /usr/lib/python3.12/site-packages/cv2, /usr/share/licenses/opencv4, /usr/share/opencv4, and /usr/share/java/opencv4

OpenJPEG-2.5.0

Introduction to OpenJPEG

OpenJPEG is an open-source implementation of the JPEG-2000 standard. OpenJPEG fully respects the JPEG-2000 specifications and can compress/decompress lossless 16-bit images.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/uclouvain/openjpeg/archive/v2.5.0/openjpeg-2.5.0.tar.gz
Download MD5 sum: 5cbb822a1203dd75b85639da4f4ecaab
Download size: 1.8 MB
Estimated disk space required: 13 MB
Estimated build time: 0.2 SBU

OpenJPEG Dependencies

Required

Optional

Little CMS-2.14, libpng-1.6.42, libtiff-4.6.0, and Doxygen-1.10.0 (to build the API documentation)

Installation of OpenJPEG

Install OpenJPEG by running the following commands:

mkdir -v build &&
cd       build &&

cmake -DCMAKE_BUILD_TYPE=Release \
      -DCMAKE_INSTALL_PREFIX=/usr \
      -DBUILD_STATIC_LIBS=OFF .. &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&
cp -rv ../doc/man -T /usr/share/man

Installed Programs: opj_compress, opj_decompress, and opj_dump

Installed Libraries: libopenjp2.so

Installed Directories: /usr/include/openjpeg-2.5 and /usr/lib/openjpeg-2.5

Short Descriptions

opj_compress	converts various image formats to the jpeg2000 format
opj_decompress	converts jpeg2000 images to other image types
opj_dump	reads in a jpeg2000 image and dumps the contents to stdout

Pixman-0.43.2

Introduction to Pixman

The Pixman package contains a library that provides low-level pixel manipulation features such as image compositing and trapezoid rasterization.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.cairographics.org/releases/pixman-0.43.2.tar.gz
Download MD5 sum: b5ad6407cd8c7abf8c1669273a2fb162
Download size: 776 KB
Estimated disk space required: 27 MB (With tests)
Estimated build time: 0.2 SBU (Using parallelism=4; with tests)

Pixman Dependencies

Optional

GTK+-2.24.33 and libpng-1.6.42 (for tests and demos)

Installation of Pixman

Install Pixman by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: None

Installed Library: libpixman-1.so

Installed Directory: /usr/include/pixman-1

Short Descriptions

libpixman-1.so

contains functions that provide low-level pixel manipulation features

Poppler-24.02.0

Introduction to Poppler

The Poppler package contains a PDF rendering library and command line tools used to manipulate PDF files. This is useful for providing PDF rendering functionality as a shared library.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://poppler.freedesktop.org/poppler-24.02.0.tar.xz
Download MD5 sum: a02d3b32e956bef66a5108fcaabe1c63
Download size: 1.8 MB
Estimated disk space required: 79 MB (with Qt5 library; add 13 MB for tests)
Estimated build time: 0.9 SBU (with parallelism=4 and Qt5 library; add 2.7 SBU for tests)

Additional Downloads

Poppler Encoding Data

Download (HTTP): https://poppler.freedesktop.org/poppler-data-0.4.12.tar.gz
Download MD5 sum: 67ee4a40aa830b1f6e2560ce5f6471ba
Download size: 4.3 MB
Estimated disk space required: 26 MB
Estimated build time: less than 0.1 SBU

The additional package consists of encoding files for use with Poppler. The encoding files are optional and Poppler will automatically read them if they are present. When installed, they enable Poppler to render CJK and Cyrillic properly.

Poppler Dependencies

Required

CMake-3.28.3, Fontconfig-2.15.0, and gobject-introspection-1.78.1

Optional

cURL-8.6.0, gdk-pixbuf-2.42.10, git-2.44.0 (for downloading test files), GTK-Doc-1.33.2, GTK+-3.24.41, and Qt-6.6.2

Installation of Poppler

Install Poppler by running the following commands:

mkdir build                         &&
cd    build                         &&

cmake  -DCMAKE_BUILD_TYPE=Release   \
       -DCMAKE_INSTALL_PREFIX=/usr  \
       -DTESTDATADIR=$PWD/testfiles \
       -DENABLE_QT6=OFF             \
       -DENABLE_UNSTABLE_API_ABI_HEADERS=ON \
       ..                           &&
make

In order to run the test suite, some testcases are needed and can be obtained only from a git repository. The command to download them is: git clone --depth 1 https://gitlab.freedesktop.org/poppler/test.git testfiles. Then issue: LC_ALL=en_US.UTF-8 make test. One test, check_qt5_signature_basics, is known to fail.

Now, as the root user:

make install

To install the documentation, run the following commands as root:

install -v -m755 -d           /usr/share/doc/poppler-24.02.0 &&
cp -vr ../glib/reference/html /usr/share/doc/poppler-24.02.0

Poppler Data

If you downloaded the additional encoding data package, install it by issuing the following commands:

tar -xf ../../poppler-data-0.4.12.tar.gz &&
cd poppler-data-0.4.12

Now, as the root user:

make prefix=/usr install

Command Explanations

-DCMAKE_BUILD_TYPE=Release: This switch is used to apply a higher level of compiler optimizations.

-DTESTDATADIR=$PWD/testfiles: Tells the test programs where the auxiliary files are located.

-DENABLE_QT6=OFF: This switch is needed to prevent an error when Qt6 is not installed. Remove it if you have installed Qt-6.6.2.

-DENABLE_UNSTABLE_API_ABI_HEADERS=ON: Installs some old Xpdf headers required by certain programs.

-DENABLE_GTK_DOC=ON: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

-DENABLE_QT5=OFF: Use this parameter if (Qt-5.15.12 or qt-alternate-5.15.12) is not installed.

-DENABLE_BOOST=OFF: Use this parameter if you have not installed boost (the Splash backend for Qt5 recommends boost).

-DENABLE_NSS3=OFF: Use this parameter if you have not installed nss.

-DENABLE_GPGME=OFF: Use this parameter if you have not installed gpgme.

-DENABLE_LIBTIFF=OFF: Use this parameter if you have not installed libtiff.

LC_ALL=en_US.UTF-8 make test: Runs the test suite. The environment variable LC_ALL=en_US.UTF-8 is only needed if the default locale does not include UTF-8.

Installed Programs: pdfattach, pdfdetach, pdffonts, pdfimages, pdfinfo, pdfseparate, pdfsig, pdftocairo, pdftohtml, pdftoppm, pdftops, pdftotext, and pdfunite

Installed Libraries: libpoppler.so, libpoppler-cpp.so, libpoppler-glib.so, libpoppler-qt5.so, and (optionally) libpoppler-qt6.so

Installed Directories: /usr/include/poppler, /usr/share/poppler, and /usr/share/doc/poppler-24.02.0

Short Descriptions

pdfattach	adds a new embedded file to an existing PDF file
pdfdetach	lists or extracts embedded files from PDF files
pdffonts	lists the fonts used in a PDF file along with various information for each font
pdfimages	saves images from a PDF file as PPM, PBM, or JPEG files
pdfinfo	prints the contents of the 'Info' dictionary (plus some other useful information) from a PDF file
pdfseparate	extracts single pages from a PDF file
pdfsig	verifies the digital signatures in a PDF document
pdftocairo	converts a PDF file to one of several formats (PNG, JPEG, PDF, PS, EPS, SVG) using the cairo output device of the poppler library
pdftohtml	converts a PDF file to HTML
pdftoppm	converts PDF files to PBM, PGM and PPM formats
pdftops	converts PDF files to Postscript format
pdftotext	converts PDF files to plain text
pdfunite	merges several PDF files, in the order of their occurrence on the command line, to one PDF output file
`libpoppler.so`	contains the API functions to render PDF files
`libpoppler-cpp.so`	is a C++ backend for rendering PDF files
`libpoppler-glib.so`	is a wrapper library used to interface the PDF rendering functions with GTK+
`libpoppler-qt5.so`	is a wrapper library used to interface the PDF rendering functions with Qt5
`libpoppler-qt6.so`	is a wrapper library used to interface the PDF rendering functions with Qt6

Potrace-1.16

Introduction to Potrace

Potrace™ is a tool for transforming a bitmap (PBM, PGM, PPM, or BMP format) into one of several vector file formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/potrace/potrace-1.16.tar.gz
Download MD5 sum: 5f0bd87ddd9a620b0c4e65652ef93d69
Download size: 644 KB
Estimated disk space required: 7.1 MB (including tests)
Estimated build time: less than 0.1 SBU (including tests)

Potrace Dependencies

Installation of Potrace

Install Potrace by running the following commands:

./configure --prefix=/usr                        \
            --disable-static                     \
            --docdir=/usr/share/doc/potrace-1.16 \
            --enable-a4                          \
            --enable-metric                      \
            --with-libpotrace                    &&
make

To run the test suite, issue: make check.

Now, as the root user:

make install

Command Explanations

--enable-a4: Use A4 as the default paper size.

--enable-metric: Use metric units (centimeters) as default

--disable-static: This switch prevents installation of static versions of the libraries.

--with-libpotrace: Install the library and headers.

Installed Programs: mkbitmap, potrace

Installed Libraries: libpotrace.so

Installed Directories: /usr/share/doc/potrace-1.16

Short Descriptions

mkbitmap	transforms images into bitmaps with scaling and filtering
potrace	transforms bitmaps into vector graphics
`libpotrace.so`	is a library for transforming bitmaps into vector graphics

Qpdf-11.8.0

Introduction to Qpdf

The Qpdf package contains command-line programs and a library that does structural, content-preserving transformations on PDF files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/qpdf/qpdf/releases/download/v11.8.0/qpdf-11.8.0.tar.gz
Download MD5 sum: aec6ad628203411cd04fbb7e145ecc72
Download size: 18 MB
Estimated disk space required: 256 MB (add 1 MB for tests)
Estimated build time: 0.5 SBU (using parallelism=4; add 0.5 SBU for tests)

Qpdf Dependencies

Required

libjpeg-turbo-3.0.1

Optional

ghostscript-10.02.1, GnuTLS-3.8.3, libtiff-4.6.0, sphinx-7.2.6 with sphinx_rtd_theme-2.0.0, and texlive-20230313 or install-tl-unx

Installation of Qpdf

Install Qpdf by running the following commands:

mkdir build &&
cd    build &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      -DBUILD_STATIC_LIBS=OFF     \
      -DCMAKE_INSTALL_DOCDIR=/usr/share/doc/qpdf-11.8.0 \
      .. &&
make

To test the results, issue: ctest.

Now, as the root user:

make install

Installed Programs: fix-qdf, qpdf, and zlib-flate

Installed Library: libqpdf.so

Installed Directories: /usr/lib/cmake/qpdf, /usr/include/qpdf, and /usr/share/doc/qpdf-11.8.0

Short Descriptions

fix-qdf	is used to repair PDF files in QDF form after editing
qpdf	is used to convert one PDF file to another equivalent PDF file
zlib-flate	is a raw zlib compression program
`libqpdf.so`	contains the Qpdf API functions

qrencode-4.1.1

Introduction to qrencode

Qrencode is a fast and compact library for encoding data in a QR Code symbol, a 2D symbology that can be scanned by handheld terminals such as a mobile phone with a CCD sensor.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://fukuchi.org/works/qrencode/qrencode-4.1.1.tar.bz2
Download MD5 sum: de7185bcab635a34730e1b73d4efa705
Download size: 451 KB
Estimated disk space required: 5.0 MB (with documentation, add 5 MB for tests)
Estimated build time: less than 0.1 SBU, add 0.1 SBU for tests

Qrencode Dependencies

Optional

Doxygen-1.10.0 for generating documentation, and SDL2-2.30.0 for tests

Installation of qrencode

Install libqrencode by running the following commands:

./configure --prefix=/usr &&
make

If you have installed Doxygen-1.10.0, you can build the documentation by issuing:

doxygen

The tests must be run after installing the package.

Now, as the root user:

make install

If you have built the optional documentation, install it as the root user:

install -vdm 755 /usr/share/doc/qrencode-4.1.1 &&
mv html/* /usr/share/doc/qrencode-4.1.1

To test the results, if you have passed the --with-tests option to configure, issue: make check.

Command Explanations

--with-tests: This option allows building the test programs. It requires SDL2-2.30.0.

--without-tools: This option prevents building the qrencode executable, removing the need for libpng-1.6.42.

Installed Program: qrencode

Installed Library: libqrencode.so

Installed Directory: /usr/share/doc/qrencode-4.1.1 (optional)

Short Descriptions

qrencode	encodes input data in a QR Code and saves it as a PNG or EPS image
`libqrencode.so`	contains functions for encoding data in a QR code symbol

sassc-3.6.2

Introduction to sassc

SassC is a wrapper around libsass, a CSS pre-processor language.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/sass/sassc/archive/3.6.2/sassc-3.6.2.tar.gz
Download MD5 sum: 4c3b06ce2979f2a9f0a35093e501d8bb
Download size: 28 KB
Estimated disk space required: 5.1 MB
Estimated build time: less than 0.1 SBU

Additional Downloads

Download (HTTP): https://github.com/sass/libsass/archive/3.6.6/libsass-3.6.6.tar.gz
Download MD5 sum: afda97284d75a030cabadf5b9f998a3b
Download size: 336 KB
Estimated disk space required: 135 MB
Estimated build time: 0.4 SBU (Using parallelism=4)

Installation of sassc

First, build the library:

tar -xf ../libsass-3.6.6.tar.gz &&
pushd libsass-3.6.6 &&

autoreconf -fi &&

./configure --prefix=/usr --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Build the command line wrapper:

popd &&
autoreconf -fi &&

./configure --prefix=/usr &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Programs: sassc

Installed Libraries: libsass.so

Installed Directories: /usr/include/sass

Short Descriptions

sassc

provides a command line interface to the libsass library

webp-pixbuf-loader-0.2.7

Introduction to webp-pixbuf-loader

The webp-pixbuf-loader package contains a library that allows gdk-pixbuf to load and process webp images.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/aruiz/webp-pixbuf-loader/archive/0.2.7/webp-pixbuf-loader-0.2.7.tar.gz
Download MD5 sum: e97025dc70178877dbd041776f151947
Download size: 8.8 MB
Estimated disk space required: 9.7 MB
Estimated build time: less than 0.1 SBU (with tests)

webp-pixbuf-loader Dependencies

Required

gdk-pixbuf-2.42.10 and libwebp-1.3.2

Installation of webp-pixbuf-loader

Install webp-pixbuf-loader by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

The webp format needs to be added to the loaders cache:

gdk-pixbuf-query-loaders --update-cache

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

gdk-pixbuf-query-loaders --update-cache: This command updates the gdk-pixbuf loader cache so that it knows the webp loader has been installed.

Installed Programs: None

Installed Libraries: libpixbufloader-webp.so

Installed Directories: None

Short Descriptions

libpixbufloader-webp.so

contains functions that allow gdk-pixbuf to load webp images

woff2-1.0.2

Introduction to WOFF2

WOFF2 is a library for converting fonts from the TTF format to the WOFF 2.0 format. It also allows decompression from WOFF 2.0 to TTF. The WOFF 2.0 format uses the Brotli compression algorithm to compress fonts suitable for downloading in CSS @font-face rules.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/google/woff2/archive/v1.0.2/woff2-1.0.2.tar.gz
Download MD5 sum: 793c8844845351cb80730a74937e411b
Download size: 39 KB
Estimated disk space required: 1.6 MB
Estimated build time: less than 0.1 SBU

WOFF2 Dependencies

Required

Brotli-1.1.0 and CMake-3.28.3

Installation of WOFF2

Install WOFF2 by running the following commands:

mkdir out                           &&
cd    out                           &&
cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release .. &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Program: None

Installed Libraries: libwoff2common.so, libwoff2dec.so and libwoff2enc.so

Installed Directory: /usr/include/woff2

Short Descriptions

`libwoff2common.so`	provides shared data used by the libwoff2dec and libwoff2enc libraries
`libwoff2dec.so`	is the WOFF2 decoder library
`libwoff2enc.so`	is the WOFF2 encoder library

Chapter 11. General Utilities

This chapter contains various utilities that do not fit conveniently into other chapters. Programs include some documentation generators, several utilities for manipulating text and graphics, programs for listing files, a program for entering PIN numbers and pass-phrases, and a connection manager.

Asciidoctor-2.0.20

Introduction to Asciidoctor

Asciidoctor is a fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML5, DocBook, PDF, and other formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/asciidoctor/asciidoctor/archive/v2.0.20/asciidoctor-2.0.20.tar.gz
Download MD5 sum: 11f40bda9a2c07f6b632a0fc91b43a13
Download size: 1.6 MB
Estimated disk space required: 5.4 MB
Estimated build time: less than 0.1 SBU

Asciidoctor Dependencies

Required

Ruby-3.3.0

Installation of Asciidoctor

Note

When building this package, the following message may appear:

fatal: not a git repository (or any of the parent directories): .git

. This is normal, and the package will continue building past this point.

Build the Ruby gem:

gem build asciidoctor.gemspec

The test suite needs many Ruby gems beyond the scope of BLFS.

Now, as the root user:

gem install asciidoctor-2.0.20.gem &&
install -vm644 man/asciidoctor.1 /usr/share/man/man1

Installed Programs: asciidoctor

Installed Libraries: None

Installed Directories: /usr/lib/ruby/gems/3.3.0/gems/asciidoctor-2.0.20 and /usr/lib/ruby/gems/3.3.0/doc/asciidoctor-2.0.20

Short Descriptions

asciidoctor

converts AsciiDoc source files to HTML, DocBook, and other formats

Bogofilter-1.2.5

Introduction to Bogofilter

The Bogofilter application is a mail filter that classifies mail as spam or ham (non-spam) by a statistical analysis of the message's header and content (body).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/bogofilter/bogofilter-1.2.5.tar.xz
Download MD5 sum: 8763f87adfff7b802ced177d8c654539
Download size: 784 KB
Estimated disk space required: 19 MB
Estimated build time: 0.1 SBU

Bogofilter Dependencies

Optional

lmdb-0.9.31, xmlto-0.0.28, Berkeley DB (deprecated), QDBM and TokyoCabinet

Note

If you do not install the recommended Gsl-2.7.1 package then a statically linked shipped version will be used instead.

Installation of Bogofilter

Note

If you plan to change the version of your database library on an existing installation, or to change to a different database, read the warning at the top of the RELEASE.NOTES file.

Install Bogofilter by running the following commands:

./configure --prefix=/usr                \
            --sysconfdir=/etc/bogofilter \
            --with-database=sqlite3      &&
make

To test the results, issue make check.

Now, as the root user:

make install

Command Explanations

--with-database=sqlite3: This switch makes Bogofilter use SQLite-3.45.1 as the database, instead of Berkeley DB.

--with-database={lmdb,qdbm,tokyocabinet}: This switch also allows to use lmdb, qdbm, or tokyocabinet as the database.

Installed Programs: bf_compact, bf_copy, bf_tar, bogofilter, bogolexer, bogotune, bogoupgrade and bogoutil

Installed Libraries: None

Installed Directories: /etc/bogofilter

Short Descriptions

bf_compact	creates a more compact bogofilter working directory with a dump/load cycle
bf_copy	copies a bogofilter working directory to another directory
bf_tar	bundles a bogofilter working directory in tar format and copies it to standard output
bogofilter	is a fast Bayesian spam filter
bogolexer	is used to separate messages into tokens and to test new versions of the lexer.l code
bogotune	attempts to find optimum parameter settings for bogofilter
bogoupgrade	upgrades the bogofilter database to the current version
bogoutil	dumps, loads, and maintains bogofilter database files

Compface-1.5.2

Introduction to Compface

Compface provides utilities and a library to convert from/to X-Face format, a 48x48 bitmap format used to carry thumbnails of email authors in a mail header.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://anduin.linuxfromscratch.org/BLFS/compface/compface-1.5.2.tar.gz
Download MD5 sum: 62f4f79c0861ad292ba3cf77b4c48319
Download size: 47 KB
Estimated disk space required: 520 KB
Estimated build time: less than 0.1 SBU

Installation of Compface

Install Compface by running the following commands:

./configure --prefix=/usr --mandir=/usr/share/man &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&
install -m755 -v xbm2xface.pl /usr/bin

Installed Programs: compface, uncompface and xbm2xface.pl

Installed Library: libcompface.{so,a}

Installed Directories: None

Short Descriptions

compface	is a filter for generating highly compressed representations of 48x48x1 face image files
uncompface	is an inverse filter which performs an inverse transformation with no loss of data
xbm2xface.pl	is a script to generate xfaces
`libcompface.{so,a}`	allows the compression and decompression algorithms to be used in other programs such as MTAs

desktop-file-utils-0.27

Introduction to Desktop File Utils

The Desktop File Utils package contains command line utilities for working with Desktop entries. These utilities are used by Desktop Environments and other applications to manipulate the MIME-types application databases and help adhere to the Desktop Entry Specification.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/desktop-file-utils/releases/desktop-file-utils-0.27.tar.xz
Download MD5 sum: fdf9215aea91acb6aebc43f770537f2c
Download size: 80 KB
Estimated disk space required: 1.2 MB
Estimated build time: less than 0.1 SBU

Desktop File Utils Dependencies

Required

Optional

Emacs-29.2

Installation of Desktop File Utils

Warning

If you are upgrading from a previous version of desktop-file-utils that used the Autotools method of installing and configuring the package, you must remove the desktop-file-edit symlink by using the following commands.

rm -fv /usr/bin/desktop-file-edit

Install Desktop File Utils by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Configuring Desktop File Utils

Configuration Information

The XDG Base Directory specification defines the standard locations for applications to place data and configuration files. These files can be used, for instance, to define the menu structure and menu items in a desktop environment.

The default location for configuration files to be installed is /etc/xdg, and the default locations for data files are /usr/local/share and /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 settings.

When a package installs a .desktop file to a location in one of the base data directories, the database that maps MIME-types to available applications can be updated. For instance, the cache file at /usr/share/applications/mimeinfo.cache can be rebuilt by executing the following command as the root user:

install -vdm755 /usr/share/applications &&
update-desktop-database /usr/share/applications

Installed Programs: desktop-file-edit, desktop-file-install, desktop-file-validate and update-desktop-database

Installed Libraries: None

Installed Directories: None

Short Descriptions

desktop-file-edit	is used to modify an existing desktop file entry
desktop-file-install	is used to install a new desktop file entry. It is also used to rebuild or modify the MIME-types application database
desktop-file-validate	is used to verify the integrity of a desktop file
update-desktop-database	is used to update the MIME-types application database

dos2unix-7.5.2

Introduction to dos2unix

The dos2unix package contains an any-to-any text format converter.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/dos2unix/dos2unix-7.5.2.tar.gz
Download MD5 sum: 646272020848c9b673de24c4e8e3422e
Download size: 972 KB
Estimated disk space required: 7.2 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

Installation of dos2unix

Build dos2unix by running the following commands:

make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Program: dos2unix, mac2unix, unix2dos, and unix2mac

Installed Libraries: None

Installed Directories: /usr/share/doc/dos2unix-7.5.2

Short Descriptions

dos2unix	converts plain text files in DOS format to Unix format
mac2unix	converts plain text files in Mac format to Unix format
unix2dos	converts plain text files in Unix format to DOS format
unix2mac	converts plain text files in Unix format to Mac format

Graphviz-10.0.1

Introduction to Graphviz

The Graphviz package contains graph visualization software. Graph visualization is a way of representing structural information as diagrams of abstract graphs and networks. Graphviz has several main graph layout programs. It also has web and interactive graphical interfaces, auxiliary tools, libraries, and language bindings.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.com/graphviz/graphviz/-/archive/10.0.1/graphviz-10.0.1.tar.bz2
Download MD5 sum: 5d343d0ba08dc11624d3961af2b4755c
Download size: 26 MB
Estimated disk space required: 220 MB
Estimated build time: 0.8 SBU (using parallelism=4)

Graphviz Dependencies

Note

Graphviz basic usage does not need any libraries out of what is found in the LFS book. Its “core” rendering engine allows to generate several graphic formats, such as Postscript, SVG, VML, .fig, and Tk. Those formats can be converted to almost any other format using for example tools from ImageMagick-7.1.1-28. The dependencies below add the ability to generate graph images in bitmap format, to display the graph image on screen, to edit a graph by viewing the resulting image directly, or to view large graphs. Since Graphviz is a dependency of several other packages in this book, it is suggested to first build it without any dependencies, then to rebuild it when you have built enough packages to suit your needs.

Optional, for various bitmap outputs

Pango-1.51.2, with Cairo-1.18.0, Xorg Libraries, Fontconfig-2.15.0, and libpng-1.6.42, to generate images in bitmap SVG, postscript, PNG, and PDF formats, or displaying the image on screen. The PNG output is required for building gegl-0.4.48

Adding GTK+-2.24.33 with libjpeg-turbo-3.0.1 adds support for JPEG, BMP, TIF, and ICO formats, and allows displaying the image in a GTK+ window

GD Library may be used instead of Pango. It adds the ability to generate images in GIF, VRML, and GD formats, but Pango provides better outputs for the other formats, and is needed for displaying images

Other formats may be added with libwebp-1.3.2 (WebP support is considered experimental), DevIL, libLASi, and glitz

Optional, to load graphic images that may be displayed inside the nodes of a graph

libgs.so from ghostscript-10.02.1, librsvg-2.57.1, and Poppler-24.02.0

Optional, to build more tools

Freeglut-3.4.0 (with GtkGLExt and libGTS for building the smyrna large graph viewer, which is considered experimental), and (Qt-5.15.12 or qt-alternate-5.15.12) (for building the gvedit graph editor.)

Optional (To Build Language Bindings)

SWIG-4.2.0 (SWIG must be installed or no bindings will be built), GCC-13.2.0 (for the go compiler), Guile-3.0.9, OpenJDK-21.0.2, Lua-5.4.6, PHP-8.3.3, Ruby-3.3.0, Tk-8.6.13, Io, Mono, OCaml, and R

Optional (building tools)

Criterion (framework for tests) and Electric Fence

Optional (for building the pdf documentation)

ghostscript-10.02.1 (for the ps2pdf command)

Installation of Graphviz

Install Graphviz by running the following commands:

sed -i '/LIBPOSTFIX="64"/s/64//' configure.ac &&

./autogen.sh              &&
./configure --prefix=/usr \
            --docdir=/usr/share/doc/graphviz-10.0.1

Note

A warning is generated by autogen.sh because the build tree is not a git repository. As a result, the build date is set to 0. To get a meaningful date in the version string, you can run:

sed -i "s/0/$(date +%Y%m%d)/" builddate.h

Whether or not you fix the date, proceed to compile the package:

make

This package does not come with a test suite that provides meaningful results.

Now, as the root user:

make install

Command Explanations

sed ... configure.ac: This command is needed to avoid installing files in /usr/lib64.

--with-javaincludedir="$JAVA_HOME/include -I$JAVA_HOME/include/linux": If you have built OpenJDK-21.0.2 in /opt, and you want to build the JAVA bindings, it is necessary to specify the location of the JAVA header files to configure. The configure switch is designed for only one directory, but two directories need to be included. This is possible nevertheless by using the -I switch inside the variable.

--with-webp: Even if libwebp-1.3.2 is installed, it is not included in the build without this option.

--with-smyrna: Even if the needed dependencies are installed, the interactive graph viewer smyrna is not built without this option.

Configuring Graphviz

Config Files

/usr/lib/graphviz/config

Configuration Information

There are no specific configuration requirements for Graphviz. You may consider installing the additional plugins and tools available from the download page at https://graphviz.org/download/source/ for additional capabilities. If additional plugins are installed, you can run dot -c (as the root user) to update the config file in /usr/lib/graphviz.

Installed Programs: acyclic, bcomps, ccomps, circo, cluster, dijkstra, dot, dot2gxl, dot_builtins, edgepaint, fdp, gc, gml2gv, graphml2gv, gv2gml, gv2gxl, gvcolor, gvedit, gvgen, gvmap, gvmap.sh, gvpack, gvpr, gxl2dot, gxl2gv, mm2gv, neato, nop, osage, patchwork, prune, sccmap, sfdp, tred, twopi, unflatten, and vimdot

Installed Libraries: libcdt.so, libcgraph.so, libgvc.so, libgvpr.so, liblab_gamut.so, libpathplan.so, libxdot.so, and several plugins in /usr/lib/graphviz. There are also several in subdirectories of /usr/lib/{lua,perl5,php,python3.12,tcl8.6}. Unfortunately, some libraries are duplicated.

Installed Directories: /usr/include/graphviz, /usr/lib/graphviz, /usr/lib/tcl8.6/graphviz, /usr/share/doc/graphviz-10.0.1, and /usr/share/graphviz

Short Descriptions

acyclic	is a filter that takes a directed graph as input and outputs a copy of the graph with sufficient edges reversed to make the graph acyclic
bcomps	decomposes graphs into their biconnected components, printing the components to standard output
ccomps	decomposes graphs into their connected components, printing the components to standard output
circo	draws graphs using a circular layout
cluster	takes a graph in DOT format as input, finds node clusters and then augments the graph with this information
diffimg	(needs GD Library) generates an image where each pixel is the difference between the corresponding pixel in each of the two source images
dijkstra	reads a stream of graphs and for each computes the distance of every node from sourcenode
dot	draws directed graphs. It works well on DAGs and other graphs that can be drawn as hierarchies. It reads attributed graph files and writes drawings. By default, the output format dot is the input file with layout coordinates appended
dot2gxl	converts between graphs represented in GXL and in the DOT language. Unless a conversion type is specified using a flag, gxl2dot will deduce the type of conversion from the suffix of the input file, a `.dot` suffix causing a conversion from DOT to GXL, and a `.gxl` suffix causing a conversion from GXL to DOT
edgepaint	performs edge coloring to disambiguate crossing edges
fdp	draws undirected graphs using a “spring” model. It relies on a force-directed approach in the spirit of Fruchterman and Reingold
gc	is a graph analogue to wc in that it prints to standard output the number of nodes, edges, connected components or clusters contained in the input files. It also prints a total count for all graphs if more than one graph is given
gml2gv	converts a graph specified in the GML format to a graph in the GV (formerly DOT) format
graphml2gv	converts a graph specified in the GRAPHML format to a graph in the GV (formerly DOT) format
gv2gml	converts a graph specified in the GV format to a graph in the GML format
gv2gxl	converts a graph specified in the GV format to a graph in the GXL format
gvcolor	is a filter that sets node colors from initial seed values. Colors flow along edges from tail to head, and are averaged (as HSB vectors) at nodes
gvedit	provides a simple graph editor and viewer. It allows many graphs to be viewed at the same time. The text of each graph is displayed in its own text window
gvgen	generates a variety of simple, regularly-structured abstract graphs
gvmap	takes as input a graph in DOT format, finds node clusters and produces a rendering of the graph as a geographic-style map, with clusters highlighted, in xdot format
gvmap.sh	is a pipeline for running gvmap
gvpack	reads in a stream of graphs, combines the graphs into a single layout, and produces a single graph serving as the union of the input graphs
gvpr	is a graph stream editor inspired by awk. It copies input graphs to its output, possibly transforming their structure and attributes, creating new graphs, or printing arbitrary information
gxl2dot	converts between graphs represented in GXL and in the DOT language. Unless a conversion type is specified using a flag, gxl2dot will deduce the type of conversion from the suffix of the input file, a `.dot` suffix causing a conversion from DOT to GXL, and a `.gxl` suffix causing a conversion from GXL to DOT
gxl2gv	converts between graphs represented in GXL and in the GV language
mm2gv	converts a sparse matrix of the Matrix Market format to a graph in the GV (formerly DOT) format
neato	draws undirected graphs using “spring” models. Input files must be formatted in the dot attributed graph language. By default, the output of neato is the input graph with layout coordinates appended
nop	reads a stream of graphs and prints each in pretty-printed (canonical) format on stdout. If no files are given, it reads from stdin
osage	draws clustered graphs. It takes any graph in DOT format as input
patchwork	draws clustered graphs using a squarified treemap layout. It takes any graph in DOT format as input
prune	reads directed graphs in the same format used by dot and removes subgraphs rooted at nodes specified on the command line via options
sccmap	decomposes digraphs into strongly connected components and an auxiliary map of the relationship between components. In this map, each component is collapsed into a node. The resulting graphs are printed to stdout
sfdp	draws undirected graphs using the “spring” model, but it uses a multi-scale approach to produce layouts of large graphs in a reasonably short time
tred	computes the transitive reduction of directed graphs, and prints the resulting graphs to standard output. This removes edges implied by transitivity. Nodes and subgraphs are not otherwise affected
twopi	draws graphs using a radial layout. Basically, one node is chosen as the center and put at the origin. The remaining nodes are placed on a sequence of concentric circles centered about the origin, each a fixed radial distance from the previous circle
unflatten	is a preprocessor to dot that is used to improve the aspect ratio of graphs having many leaves or disconnected nodes. The usual layout for such a graph is generally very wide or tall
vimdot	is a simple script which launches the gvim or vim editor along with a GUI window showing the dot output of the edited file
`libcdt.so`	manages run-time dictionaries using standard container data types: unordered set/multiset, ordered set/multiset, list, stack, and queue
`libcgraph.so`	supports graph programming by maintaining graphs in memory and reading and writing graph files. Graphs are composed of nodes, edges, and nested subgraphs
`libgvc.so`	provides a context for applications wishing to manipulate and render graphs. It provides command line parsing interfaces, common rendering code, and a plugin mechanism for renderers
`libpathplan.so`	contains functions to find the shortest path between two points in a simple polygon
`libxdot.so`	provides support for parsing and deparsing graphical operations specified by the xdot language

GTK-Doc-1.33.2

Introduction to GTK-Doc

The GTK-Doc package contains a code documenter. This is useful for extracting specially formatted comments from the code to create API documentation. This package is optional; if it is not installed, packages will not build the documentation. This does not mean that you will not have any documentation. If GTK-Doc is not available, the install process will copy any pre-built documentation to your system.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/gtk-doc/1.33/gtk-doc-1.33.2.tar.xz
Download MD5 sum: ea6563421abe964d02135ca0d5b8dd8e
Download size: 496 KB
Estimated disk space required: 13 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

GTK-Doc Dependencies

Required

docbook-xml-4.5, docbook-xsl-nons-1.79.2, itstool-2.0.7, and libxslt-1.1.39

Optional

For tests: dblatex or fop-2.9 (XML PDF support), GLib-2.78.4, Which-2.21, and Python modules lxml-4.9.4, parameterized, and yelp-tools

Note

The optional python modules above can be easily installed with the pip3 command.

Installation of GTK-Doc

Install GTK-Doc by running the following commands:

autoreconf -fiv           &&
./configure --prefix=/usr &&
make

The test suite will hang if the package (or a previous version) is not already installed.

Now, as the root user:

make install

To test the results, issue: make check. Some tests will fail depending on optionally installed packages.

Installed Programs: gtkdocize, gtkdoc-check, gtkdoc-depscan, gtkdoc-fixxref, gtkdoc-mkdb, gtkdoc-mkhtml, gtkdoc-mkhtml2, gtkdoc-mkman, gtkdoc-mkpdf, gtkdoc-rebase, gtkdoc-scan, and gtkdoc-scangobj

Installed Libraries: None

Installed Directories: /usr/share/gtk-doc and /usr/share/cmake/GtkDoc

Short Descriptions

gtkdoc*

these are all shell, or Python scripts used by package Makefile scripts to generate documentation for the package being built

Highlight-4.10

Introduction to Highlight

Highlight is an utility that converts source code to formatted text with syntax highlighting.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://www.andre-simon.de/zip/highlight-4.10.tar.bz2
Download MD5 sum: 187a16136f7aa4310e57eecb994b7ac4
Download size: 1.4 MB
Estimated disk space required: 24 MB (with gui)
Estimated build time: 0.3 SBU (Using parallelism=4; with gui)

Highlight Dependencies

Required

Boost-1.84.0 and Lua-5.4.6

Optional

(Qt-5.15.12 or qt-alternate-5.15.12) (to build the GUI front-end)

Installation of Highlight

For consistency, do not compress man pages.

sed -i '/GZIP/s/^/#/' makefile

To build Highlight run the following command:

make

To build the Qt5 GUI front-end, run the following command:

make doc_dir=/usr/share/doc/highlight-4.10/ gui

This package does not come with a test suite.

To install Highlight, run the following command as the root user:

make doc_dir=/usr/share/doc/highlight-4.10/ install

To install the GUI program, run the following command as the root user:

make install-gui

Command Explanations

doc_dir=/usr/share/doc/highlight-4.10/: installs the highlight documentation into a versioned directory. This parameter is also needed for make gui, because its value would be hardcoded into the gui executable. Note that the trailing “/” is necessary.

Installed Programs: highlight and highlight-gui (optional)

Installed Libraries: None

Installed Directories: /etc/highlight, /usr/share/doc/highlight-4.10, and /usr/share/highlight

Short Descriptions

highlight	is a universal source code to formatted text converter
highlight-gui	is the Qt5 interface to highlight.

ibus-1.5.29

Introduction to ibus

ibus is an Intelligent Input Bus. It is a new input framework for the Linux OS. It provides a fully featured and user friendly input method user interface.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/ibus/ibus/archive/refs/tags/1.5.29/ibus-1.5.29.tar.gz
Download MD5 sum: 2e29a7fb0f8c5ffcf42462fda45348fd
Download size: 1.4 MB
Estimated disk space required: 54 MB (add 3 MB for tests)
Estimated build time: 0.3 SBU (Using parallelism=4; add 0.6 SBU for tests)

Additional Downloads

Unicode Character Database: https://www.unicode.org/Public/zipped/15.1.0/UCD.zip

ibus Dependencies

Required

DConf-0.40.0, ISO Codes-4.16.0, and Vala-0.56.14

Optional

GTK-4.12.5 (to build IM module for it), GTK-Doc-1.33.2 (for generating API documentation), D-Bus Python-1.3.2 and PyGObject-3.46.0 (both to build the Python support library), libxkbcommon-1.6.0, Wayland-1.22.0 (both to build the Wayland support programs), EmojiOne, and libdbusmenu

Installation of ibus

First, install the Unicode Character Database as the root user:

mkdir -p               /usr/share/unicode/ucd &&
unzip -o ../UCD.zip -d /usr/share/unicode/ucd

Fix an issue with deprecated schema entries:

sed -e 's@/desktop/ibus@/org/freedesktop/ibus@g' \
    -i data/dconf/org.freedesktop.ibus.gschema.xml

If GTK-Doc-1.33.2 is not installed, remove the references to it:

if ! [ -e /usr/bin/gtkdocize ]; then
  sed '/docs/d;/GTK_DOC/d' -i Makefile.am configure.ac
fi

Install ibus by running the following commands:

SAVE_DIST_FILES=1 NOCONFIGURE=1 ./autogen.sh &&

PYTHON=python3                     \
./configure --prefix=/usr          \
            --sysconfdir=/etc      \
            --disable-python2      \
            --disable-appindicator \
            --disable-emoji-dict   \
            --disable-gtk2         \
            --disable-systemd-services &&
make

To test the results, issue: make -k check. The test named ibus-compose fails because it uses some locales not installed in LFS. The test named ibus-keypress will fail if running in a Wayland session.

Now, as the root user:

make install

Command Explanations

--disable-appindicator: This switch disables use of libdbusmenu. Omit if you installed the optional dependency.

--disable-emoji-dict: This switch disables the use of emoticon dictionaries. Omit if you installed the optional package.

--disable-gtk2: This switch removes the dependency on GTK+-2.

--enable-gtk4: This switch enables building the GTK 4 immodule. Use it if you have installed GTK 4.

--enable-python-library: This switch enables building the Python support library. Use it if you have installed the optional Python modules.

--enable-wayland: This switch enables building the Wayland support programs. It's automatically enabled if both libxkbcommon-1.6.0 and Wayland-1.22.0 are installed.

NOCONFIGURE=1: Prevent autogen.sh from running the generated configure script. We'll run the script manually instead of relying on autogen.sh to run it, because autogen.sh would set -fsanitize=address -fsanitize=leak in CFLAGS running configure, but those compiler options are not suitable for productive use and they may also cause a build failure.

PYTHON=python3: This environment variable makes the configure script look for Python 3. Use it if you want to build the Python 3 support library.

SAVE_DIST_FILES=1: This environment variable makes the autogen.sh script save some pre-generated header files instead of overwriting them when it is run. This prevents build failures when generating ibusemojigen.h.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Configuring Ibus

If GTK+-3 or GTK+-2 are installed and --disable-gtk{3,2} are not used, the ibus IM module for GTK+-3 or GTK+-2 will be installed. As the root user, update a cache file of GTK+-3 or GTK+-2 so the GTK-based applications can find the newly installed IM module and use ibus as an input method:

gtk-query-immodules-3.0 --update-cache

The command above updates the cache file for GTK+-3. For GTK+-2, use gtk-query-immodules-2.0 instead of gtk-query-immodules-3.0. GTK-4 does not require a cache file for IM modules.

Installed Programs: ibus, ibus-daemon, and ibus-setup

Installed Library: libibus-1.0.so and im-ibus.so (GTK+ Immodule)

Installed Directories: /etc/dconf/db/ibus.d, /usr/include/ibus-1.0, /usr/share/gtk-doc/html/ibus, and /usr/share/ibus

Short Descriptions

ibus-daemon	is the Intelligent Input Bus Daemon
ibus-setup	is the GTK+ program used to configure the ibus-daemon
`libibus-1.0.so`	contains the ibus API functions

ImageMagick-7.1.1-28

Introduction to ImageMagick

ImageMagick is a collection of tools and libraries to read, write, and manipulate an image in various image formats. Image processing operations are available from the command line. Bindings for Perl and C++ are also available.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.imagemagick.org/archive/releases/ImageMagick-7.1.1-28.tar.xz
Download MD5 sum: 954931222003bbc79c976db4d79e934c
Download size: 11 MB
Estimated disk space required: 210 MB, 45 MB installed (with typical dependencies; add 10 MB for checks)
Estimated build time: 0.7 SBU (with typical dependencies; add 0.7 SBU for checks, both using parallelism=4)

Note

The ImageMagick source releases are updated frequently and the version shown above may no longer be available from the download locations. You can download a more recent version and use the existing BLFS instructions to install it. Chances are that it will work just fine, but this has not been tested by the BLFS team. If the package version shown above is not available from the locations shown above, you can download it from the BLFS package server at Oregon State University: https://ftp.osuosl.org/pub/blfs/conglomeration/ImageMagick/.

ImageMagick Dependencies

The optional dependencies listed below should be installed if you need support for the specific format or the conversion tool the dependency provides. Additional information about the dependencies can be found in the Install-unix.txt file located in the source tree as well as issuing the ./configure --help command. A summary of this information, as well as some additional notes can be viewed on-line at https://imagemagick.org/script/install-source.php.

Optional System Utilities

Clang from LLVM-17.0.6, Cups-2.4.7, cURL-8.6.0, FFmpeg-6.1.1, fftw-3.3.10, p7zip-17.04 (LZMA), SANE-1.2.1, Wget-1.21.4, xdg-utils-1.2.1, xterm-390, Dmalloc, Electric Fence and PGP or GnuPG-2.4.4 (you'll have to do some hacking to use GnuPG), Profiles

Optional Graphics Libraries

JasPer-4.2.0, Little CMS-2.14, libgxps-0.3.2, libjpeg-turbo-3.0.1, libpng-1.6.42, libraw-0.21.2 (for dng files, needs the thread-safe libraw_r), librsvg-2.57.1, libtiff-4.6.0, libwebp-1.3.2, OpenJPEG-2.5.0, Pango-1.51.2, DjVuLibre, FlashPIX (libfpx), FLIF, JBIG-KIT, libheif with libde265 (both needed if converting macOS heic images), libjxl, libraqm, Liquid Rescale, OpenEXR, and RALCGM (or ralcgm)

Optional Graphics Utilities

Dejavu fonts, ghostscript-10.02.1, Gimp-2.10.36, Graphviz-10.0.1, Inkscape-1.3.2, Blender, corefonts, GhostPCL, Gnuplot, POV-Ray, and Radiance

Optional Conversion Tools

Enscript-1.6.6, Potrace-1.16, texlive-20230313 (or install-tl-unx) AutoTrace, GeoExpress Command Line Utilities, AKA MrSID Utilities (binary package), hp2xx, libwmf, UniConvertor, and Utah Raster Toolkit (or URT-3.1b)

Installation of ImageMagick

Install ImageMagick by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --enable-hdri     \
            --with-modules    \
            --with-perl       \
            --disable-static  &&
make

Now, as the root user:

make DOCUMENTATION_PATH=/usr/share/doc/imagemagick-7.1.1 install

To test the installation, issue: make check. Note that the EPS, PS, and PDF tests require a working Ghostscript. One test in 'make check' needs “Helvetica” from “Ghostscript Standard Fonts”, which are optionally installed in ghostscript-10.02.1 - that test, and one other, might fail, but all the validation can still pass.

Command Explanations

--enable-hdri: Enables building of a high dynamic range version of ImageMagick.

--with-modules: Enables support for dynamically loadable modules.

--with-perl: Enables building and installing of PerlMagick.

--disable-static: This switch prevents installation of static versions of the libraries.

--with-fftw: Enables support for the FFTW shared library.

--with-rsvg: Enables support for the librsvg library.

--with-autotrace: Enables support for the Autotrace library.

--with-wmf: Enables support for the libwmf library.

--with-gvc: Enables support for GraphViz.

--with-security-policy=open|limited|secure|websafe: If you wish to enforce a policy other than the default 'open' see www/security-policy.html in the source for details.

--with-windows-font-dir= <Some/Directory>: This option specifies the directory where the Windows CoreFonts are installed.

--with-dejavu-font-dir= <Some/Directory>: This option specifies the directory where the DejaVu fonts are installed.

The options and parameters listed above are the only ones you should have to pass to the configure script to activate all the delegate dependencies. All other dependencies will be automatically detected and utilized in the build if they are installed.

Installed Programs: magick, Magick++-config, MagickCore-config, and MagickWand-config. (animate, compare, composite, conjure, convert, display, identify, import, magick-script, mogrify, montage, and stream are all symbolic links to magick)

Installed Libraries: libMagickCore-7.Q16HDRI.so, libMagickWand-7.Q16HDRI.so and libMagick++-7.Q16HDRI.so

Installed Directories: /etc/ImageMagick-7, /usr/include/ImageMagick-7, /usr/lib/ImageMagick-7.1.1, /usr/lib/perl5/site_perl/5.38/{,auto}/Image/Magick, /usr/share/doc/ImageMagick-7.1.1, and /usr/share/ImageMagick-7

Short Descriptions

animate	animates a sequence of images
compare	compares an image to a reconstructed image
composite	composites various images into the given base image
conjure	processes a MSL script to create an image
convert	converts image(s) from one format to another
display	displays an image
identify	describes the format and characteristics of an image file
import	captures an X window
magick	convert between image formats as well as resize an image, blur, crop, despeckle, dither, draw on, flip, join, re-sample and much more
Magick{++,Core,Wand}-config	show information about the installed versions of the ImageMagick libraries
mogrify	transforms an image
montage	composites various images into a new image
stream	streams one or more pixel components of an image or portion of the image to your choice of storage formats
`Image::Magick`	allows the reading, manipulation and writing of a large number of image file formats using the ImageMagick library. Run make in the `PerlMagick/demo` directory of the package source tree after the package is installed to see a nice demo of the module's capabilities
`libMagickCore-7.Q16HDRI.so`	provides the C API for ImageMagick
`libMagickWand-7.Q16HDRI.so`	is the recommended C API for ImageMagick. Unlike the MagickCore API it uses only a few opaque types
`libMagick++-7.Q16HDRI.so`	provides the C++ API for ImageMagick

ISO Codes-4.16.0

Introduction to ISO Codes

The ISO Codes package contains a list of country, language and currency names and it is used as a central database for accessing this data.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.debian.org/debian/pool/main/i/iso-codes/iso-codes_4.16.0.orig.tar.xz
Download MD5 sum: 5760b5a359301397cc3ab2baa165c31c
Download size: 3.7 MB
Estimated disk space required: 95 MB
Estimated build time: 0.1 SBU (with tests)

Installation of ISO Codes

The directory is called iso-codes-4.16.0.

Install ISO Codes by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Note

If you install ISO codes over a previous installed version, the install step will fail when creating some symlinks. In order to properly update them, run:

sed -i '/^LN_S/s/s/sfvn/' */Makefile

Now, as the root user:

make install

Installed Programs: None

Installed Libraries: None

Installed Directory: /usr/share/iso-codes, /usr/share/xml/iso-codes

lsof-4.99.0

Introduction to lsof

The lsof package is useful to LiSt Open Files for a given running application or process.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/lsof-org/lsof/releases/download/4.99.0/lsof-4.99.0.tar.gz
Download MD5 sum: 8c858675f6d6e137df9b4e26ad6c46e8
Download size: 1.1 MB
Estimated disk space required: 14 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

lsof Dependencies

Required

libtirpc-1.3.4

Optional

Nmap-7.94 (with a symbolic link nc pointing to ncat in /usr/bin; used in tests)

Kernel Configuration

To run the tests, the following option should be enabled in the kernel configuration:

General setup --->
  [*] POSIX Message Queues                                        [POSIX_MQUEUE]

Installation of lsof

Install lsof by running the following commands:

./configure --prefix=/usr --disable-static &&
make

The tests should be run as the root user. They require that the POSIX message queues are enabled in the kernel, and that Nmap-7.94 be installed with a symbolic link /usr/bin/nc pointing to ncat.

make check

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Program: lsof

Installed Libraries: liblsof.so

Installed Directories: None

Short Descriptions

lsof	lists open files for running processes
`liblsof.so`	contains an interface for applications to list open files

mandoc-1.14.6

Introduction to mandoc

mandoc is an utility to format manual pages.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://mandoc.bsd.lv/snapshots/mandoc-1.14.6.tar.gz
Download MD5 sum: f0adf24e8fdef5f3e332191f653e422a
Download size: 684 KB
Estimated disk space required: 22 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

Installation of mandoc

Many utilities provided by mandoc conflicts with Man-DB in LFS. Only build the mandoc command:

./configure &&
make mandoc

To test the package, issue: make regress.

Now, as the root user:

install -vm755 mandoc   /usr/bin &&
install -vm644 mandoc.1 /usr/share/man/man1

Installed Programs: mandoc

Short Descriptions

mandoc

Formats manual pages

pinentry-1.2.1

Introduction to PIN-Entry

The PIN-Entry package contains a collection of simple PIN or pass-phrase entry dialogs which utilize the Assuan protocol as described by the Ägypten project. PIN-Entry programs are usually invoked by the gpg-agent daemon, but can be run from the command line as well. There are programs for various text-based and GUI environments, including interfaces designed for Ncurses (text-based), and for the common GTK and Qt toolkits.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.gnupg.org/ftp/gcrypt/pinentry/pinentry-1.2.1.tar.bz2
Download MD5 sum: be9b0d4bb493a139d2ec20e9b6872d37
Download size: 536 KB
Estimated disk space required: 5.6 MB
Estimated build time: less than 0.1 SBU

PIN-Entry Dependencies

Required

libassuan-2.5.6 and libgpg-error-1.47

Optional

Emacs-29.2, FLTK-1.3.9, Gcr-3.41.2, GTK+-2.24.33, KDE Frameworks-5.115.0 (or kwayland-5.115.0 for lxqt), libsecret-0.21.3, (Qt-5.15.12 or qt-alternate-5.15.12), and efl

Installation of PIN-Entry

Install PIN-Entry by running the following commands:

./configure --prefix=/usr --enable-pinentry-tty &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--enable-inside-emacs=yes/no: Default is no.

--enable-pinentry-qt=yes/no: Default is yes.

--enable-pinentry-gtk2=yes/no: Default is yes. Even if other pinentry-* is installed, pinentry will be a symlink to pinentry-gtk-2.

--enable-pinentry-gnome3=yes/no: Default is yes. Actually, it uses Gcr for the pinentry dialog.

--enable-pinentry-tty: Default is 'maybe'.

Installed Programs: pinentry (symlink), pinentry-curses, pinentry-emacs, pinentry-fltk, pinentry-gnome3, pinentry-gtk-2, pinentry-qt, and pinentry-tty

Installed Libraries: None

Installed Directory: None

Short Descriptions

pinentry	is a symbolic link to the default PIN-Entry program
pinentry-curses	is an Ncurses text-based PIN-Entry helper program
pinentry-emacs	is an Emacs version of the PIN-Entry helper program
pinentry-fltk	is a FLTK PIN-Entry helper program
pinentry-gnome3	is a GNOME-3 PIN-Entry helper program
pinentry-gtk-2	is a GTK+2 PIN-Entry helper program
pinentry-qt	is a Qt4 or 5 PIN-Entry helper program
pinentry-tty	is a tty PIN-Entry helper program

Screen-4.9.1

Introduction to Screen

Screen is a terminal multiplexor that runs several separate processes, typically interactive shells, on a single physical character-based terminal. Each virtual terminal emulates a DEC VT100 plus several ANSI X3.64 and ISO 2022 functions and also provides configurable input and output translation, serial port support, configurable logging, multi-user support, and many character encodings, including UTF-8. Screen sessions can be detached and resumed later on a different terminal.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/screen/screen-4.9.1.tar.gz
Download MD5 sum: 9a9bdc956bd93e4f0cb9e48678889e26
Download size: 1020 KB
Estimated disk space required: 9.5 MB
Estimated build time: 0.1 SBU

Screen Dependencies

Optional

Linux-PAM-1.6.0

Installation of Screen

Install Screen by running the following commands:

sh autogen.sh                                 &&
./configure --prefix=/usr                     \
            --infodir=/usr/share/info         \
            --mandir=/usr/share/man           \
            --with-socket-dir=/run/screen     \
            --with-pty-group=5                \
            --with-sys-screenrc=/etc/screenrc &&

sed -i -e "s%/usr/local/etc/screenrc%/etc/screenrc%" {etc,doc}/* &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&
install -m 644 etc/etcscreenrc /etc/screenrc

Command Explanations

--with-socket-dir=/run/screen: This option places the per-user sockets in a standard location.

--with-sys-screenrc=/etc/screenrc: This option places the global screenrc file in /etc.

--with-pty-group=5: This option sets the gid to the value used by LFS.

sed -i -e "s%/usr/local/etc/screenrc%/etc/screenrc%" {etc,doc}/*: This command corrects the configuration and documentation files to the location that is used here for the global screenrc file.

Configuring Screen

Config Files

/etc/screenrc and ~/.screenrc

Configuration Information

You may want to look at the example configuration file that was installed and customize it for your needs.

Installed Program: screen (symlink) and screen-4.9.1

Installed Libraries: None

Installed Directory: /usr/share/screen and /run/screen

Short Descriptions

screen

is a terminal multiplexor with VT100/ANSI terminal emulation

shared-mime-info-2.4

Introduction to Shared Mime Info

The Shared Mime Info package contains a MIME database. This allows central updates of MIME information for all supporting applications.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.freedesktop.org/xdg/shared-mime-info/-/archive/2.4/shared-mime-info-2.4.tar.gz
Download MD5 sum: aac56db912b7b12a04fb0018e28f2f36
Download size: 7.5 MB
Estimated disk space required: 26 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

Additional Downloads

Optional download, required to run the test suite: https://anduin.linuxfromscratch.org/BLFS/xdgmime/xdgmime.tar.xz

xdgmime md5sum: 7dfb4446705d345d3acd672024049e86

Shared Mime Info Dependencies

Required

GLib-2.78.4 and libxml2-2.12.5

Optional

xmlto-0.0.28

Installation of Shared Mime Info

Install Shared Mime Info by running the following commands:

If you wish to run the test suite, you must first extract the xdgmime tarball into the current directory, and compile it so that meson can find it:

tar -xf ../xdgmime.tar.xz &&
make -C xdgmime

Now build the package:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release -Dupdate-mimedb=true .. &&
ninja

If you have followed the instructions above to build xdgmime, to test the result issue ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dupdate-mimedb=true: This parameter tells the build system to run update-mime-database during installation. Otherwise, this must be done manually in order to be able to use the MIME database.

Installed Program: update-mime-database

Installed Library: None

Installed Directory: /usr/share/mime

Short Descriptions

update-mime-database

assists in adding MIME data to the database

Sharutils-4.15.2

Introduction to Sharutils

The Sharutils package contains utilities that can create 'shell' archives.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/sharutils/sharutils-4.15.2.tar.xz
Download MD5 sum: 5975ce21da36491d7aa6dc2b0d9788e0
Download size: 1.1 MB
Estimated disk space required: 22 MB (with the test suite)
Estimated build time: 0.4 SBU (with the test suite)

Installation of Sharutils

Fix a heap buffer overflow, and an issue exposed by GCC-10:

sed -i 's/BUFSIZ/rw_base_size/' src/unshar.c &&
sed -i '/program_name/s/^/extern /' src/*opts.h

Install Sharutils by running the following commands:

sed -i 's/IO_ftrylockfile/IO_EOF_SEEN/' lib/*.c        &&
echo "#define _IO_IN_BACKUP 0x100" >> lib/stdio-impl.h &&

./configure --prefix=/usr &&
make

To test the results, issue make check.

Now, as the root user:

make install

Installed Programs: shar, unshar, uudecode and uuencode

Installed Libraries: None

Installed Directories: None

Short Descriptions

shar	creates "shell archives" (or shar files) which are in text format and can be mailed
unshar	unpacks a shar file
uudecode	reads a file (or by default the standard input) and writes an encoded version to the standard output. The encoding uses only printing ASCII characters
uuencode	reads a file (or by default the standard input) and decodes the uuencoded version to the standard output

telepathy-mission-control-5.16.6

Introduction to Telepathy Mission Control

Telepathy Mission Control is an account manager and channel dispatcher for the Telepathy framework, allowing user interfaces and other clients to share connections to real-time communication services without conflicting.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-5.16.6.tar.gz
Download MD5 sum: 911e990c7755eb98a8022223f649405d
Download size: 1.1 MB
Estimated disk space required: 28 MB
Estimated build time: 0.2 SBU

Telepathy Mission Control Dependencies

Required

telepathy-glib-0.24.2

Optional

D-Bus Python-1.3.2 (for the “twisted” tests), GTK-Doc-1.33.2, UPower-1.90.2, and Twisted (for the “twisted” tests)

Installation of Telepathy Mission Control

Install Telepathy Mission Control by running the following commands:

PYTHON=python3 \
./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

PYTHON=python3: prevents using Python2 if it is installed.

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: mc-tool, mc-wait-for-name and mission-control-5 (library executable)

Installed Libraries: libmission-control-plugins.so

Installed Directories: /usr/include/mission-control-5.5 and /usr/share/gtk-doc/html/mission-control-plugins

Short Descriptions

mc-tool	is a command line tool used to manipulate Mission Control accounts
mc-wait-for-name	waits for a D-Bus bus name that will be provided automatically by the desktop session
mission-control-5	is a D-Bus service which runs on the session bus to implement AccountManager and ChannelDispatcher services described in the Telepathy D-Bus specification
`libmission-control-plugins.so`	contains Telepathy Mission Control plugin API functions

tidy-html5-5.8.0

Introduction to Tidy HTML5

The Tidy HTML5 package contains a command line tool and libraries used to read HTML, XHTML and XML files and write cleaned up markup. It detects and corrects many common coding errors and strives to produce visually equivalent markup that is both W3C compliant and compatible with most browsers.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/htacg/tidy-html5/archive/5.8.0/tidy-html5-5.8.0.tar.gz
Download MD5 sum: 0f6c55ef651e258adbe5750f555af50f
Download size: 992 KB
Estimated disk space required: 11 MB
Estimated build time: 0.2 SBU

Tidy HTML5 Dependencies

Required

Installation of Tidy HTML5

Install Tidy HTML5 by running the following commands:

cd build/cmake &&

cmake -DCMAKE_INSTALL_PREFIX=/usr \
      -DCMAKE_BUILD_TYPE=Release  \
      -DBUILD_TAB2SPACE=ON        \
      ../..    &&

make

This package does not come with a test suite.

Now, as the root user:

make install &&
rm -fv /usr/lib/libtidy.a &&
install -v -m755 tab2space /usr/bin

Command Explanations

-DCMAKE_BUILD_TYPE=Release: This switch is used to build the release library without any debug `assert` in the code.

-DBUILD_TAB2SPACE=ON: This switch is used to enable building the tab2space utility.

Configuring Tidy HTML5

Config Files

The absolute path of the file specified in HTML_TIDY.

Configuration Information

The default configuration options can be set in the file defined in HTML_TIDY. Additional configuration options can be passed to tidy via command line parameters or the -config <file> parameter.

Installed Programs: tab2space and tidy

Installed Library: libtidy.so

Installed Directory: /usr/share/doc/tidy-5.8.0

Short Descriptions

tab2space	is a utility to expand tabs and ensure consistent line endings
tidy	validates, corrects, and pretty-prints HTML files
`libtidy.so`	library provides the Tidy HTML5 API functions to tidy and can also be called by other programs

Time-1.9

Introduction to Time

The time utility is a program that measures many of the CPU resources, such as time and memory, that other programs use. The GNU version can format the output in arbitrary ways by using a printf-style format string to include various resource measurements.

Although the shell has a builtin command providing similar functionalities, this utility is required by the LSB.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/time/time-1.9.tar.gz
Download MD5 sum: d2356e0fe1c0b85285d83c6b2ad51b5f
Download size: 584 KB
Estimated disk space required: 4.0 MB (with tests)
Estimated build time: 0.1 SBU (with tests)

Installation of Time

Install Time by running the following commands:

./configure --prefix=/usr &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Installed Program: time

Installed Library: None

Installed Directory: None

Short Descriptions

time

reports various statistics about an executed command

tree-2.1.1

Introduction to tree

The tree application is useful to display a dictionary tree's contents, including files, directories, and links.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.com/OldManProgrammer/unix-tree/-/archive/2.1.1/unix-tree-2.1.1.tar.bz2
Download MD5 sum: 85f9a6d1e48f1d5262a9b2d58d47431f
Download size: 52 KB
Estimated disk space required: 732 KB
Estimated build time: less than 0.1 SBU

Installation of tree

Install tree by running the following commands:

make

This package does not come with a test suite.

Now, as the root user:

make PREFIX=/usr MANDIR=/usr/share/man install

Installed Program: tree

Installed Libraries: None

Installed Directories: None

Short Descriptions

tree

displays a directory tree in a terminal

unixODBC-2.3.12

Introduction to unixODBC

The unixODBC package is an Open Source ODBC (Open DataBase Connectivity) sub-system and an ODBC SDK for Linux, Mac OSX, and UNIX. ODBC is an open specification for providing application developers with a predictable API with which to access data sources. Data sources include optional SQL Servers and any data source with an ODBC Driver. unixODBC contains the following components used to assist with the manipulation of ODBC data sources: a driver manager, an installer library and command line tool, command line tools to help install a driver and work with SQL, drivers and driver setup libraries.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/lurcher/unixODBC/releases/download/2.3.12/unixODBC-2.3.12.tar.gz
Download MD5 sum: d62167d85bcb459c200c0e4b5a63ee48
Download size: 1.7 MB
Estimated disk space required: 28 MB
Estimated build time: 0.2 SBU (using parallelism=4)

unixODBC Dependencies

Optional

Mini SQL

Installation of unixODBC

Install unixODBC by running the following commands:

./configure --prefix=/usr \
            --sysconfdir=/etc/unixODBC &&
make

This package does not come with a test suite.

Now, as the root user:

make install &&

find doc -name "Makefile*" -delete                &&
chmod 644 doc/{lst,ProgrammerManual/Tutorial}/*   &&

install -v -m755 -d /usr/share/doc/unixODBC-2.3.12 &&
cp      -v -R doc/* /usr/share/doc/unixODBC-2.3.12

Command Explanations

--enable-drivers: This parameter enables building the drivers that were installed by default in previous versions.

--enable-drivers-conf: This parameter enables building the driver configuration libraries that were installed by default in previous versions.

Configuring unixODBC

Config Files

/etc/unixODBC/*

Configuration Information

The files in /etc/unixODBC are meant to be configured by the system administrator (or the ODBC site administrator if appropriate privileges are granted to /etc/unixODBC). These files are not meant to be directly edited. The ODBC installer library is responsible for reading and writing the unixODBC config files.

Unfortunately, there are not many man, or any info pages for the various programs available in the unixODBC package. Along with the information in the “Short Descriptions” below and the documentation installed in /usr/share/doc/unixODBC-2.3.12, there are many README files throughout the source tree where the use and functionality of the programs can be found. Additionally, you can use the parameter -? for syntax and usage information. Lastly, the unixODBC web site at http://www.unixodbc.org/ has very good information.

Installed Programs: dltest, isql, iusql, odbc_config, odbcinst, and slencheck

Installed Libraries: libodbc.so, libodbccr.so, and libodbcinst.so

Installed Directories: /etc/unixODBC and /usr/share/doc/unixODBC-2.3.12

Short Descriptions

dltest	is a utility used to check a shared library to see if it can be loaded and if a given symbol exists in it
isql	is a utility which can be used to submit SQL to a data source and to format/output results. It can be used in batch or interactive mode
iusql	provides the same functionality as the isql program
odbc_config	is used to find out details about the installation of the unixODBC package
odbcinst	is a utility created for install script/RPM writers. It is a command line interface to key functionality in the `libodbcinst` library. It does not copy any files (i.e., libraries) but it will modify the ODBC System Information for the user
slencheck	is a utility which attempts to check whether an ODBC driver was built with 32-bit or 64-bit SQLLEN types

xdg-dbus-proxy-0.1.5

Introduction to xdg-dbus-proxy

The xdg-dbus-proxy package contains a filtering proxy for D-Bus connections. This is useful for forwarding data in and out of a sandbox.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/flatpak/xdg-dbus-proxy/releases/download/0.1.5/xdg-dbus-proxy-0.1.5.tar.xz
Download (FTP):
Download MD5 sum: b496f34b0fa4747a66eb5adb63b7d626
Download size: 124 KB
Estimated disk space required: 1.4 MB
Estimated build time: less than 0.1 SBU

xdg-dbus-proxy Dependencies

Required

Installation of xdg-dbus-proxy

Install xdg-dbus-proxy by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

To test the results, issue: ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Programs: xdg-dbus-proxy

Installed Libraries: None

Installed Directories: None

Short Descriptions

xdg-dbus-proxy

is a filtering proxy for D-Bus connections

Xdg-user-dirs-0.18

Introduction to Xdg-user-dirs

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.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://user-dirs.freedesktop.org/releases/xdg-user-dirs-0.18.tar.gz
Download MD5 sum: dc7decea7ffb58cd067eff1fe1798cae
Download size: 267 KB
Estimated disk space required: 3.0 MB
Estimated build time: less than 0.1 SBU

Xdg-user-dirs Dependencies

Optional

docbook-xml-4.5, docbook-xsl-nons-1.79.2, and libxslt-1.1.39 (all three for building the man pages)

Installation of Xdg-user-dirs

Install xdg-user-dirs by running the following commands:

./configure --prefix=/usr           \
            --sysconfdir=/etc       \
            --disable-documentation &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--disable-documentation: Disable the installation of the man pages. Remove this switch if you've installed the optional dependencies and you wish to install the man pages of this package.

Configuring Xdg-user-dirs

Config Files

~/.config/user-dirs.dirs, /etc/xdg/user-dirs.conf, and /etc/xdg/user-dirs.defaults. Those default locations can be overridden by XDG_CONFIG_HOME and XDG_CONFIG_DIRS

Installed Programs: xdg-user-dir and xdg-user-dirs-update

Installed Library: None

Installed Directory: None

Short Descriptions

xdg-user-dir	looks up the current path for one of the XDG user directories
xdg-user-dirs-update	creates localized versions of the user directories

Chapter 12. System Utilities

This chapter contains mainly hardware utilities. It also contains some applications used by other applications in the book for installation or configuration purposes.

AccountsService-23.13.9

Introduction to AccountsService

The AccountsService package provides a set of D-Bus interfaces for querying and manipulating user account information and an implementation of those interfaces based on the usermod(8), useradd(8), and userdel(8) commands.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/accountsservice/accountsservice-23.13.9.tar.xz
Download MD5 sum: 03dccfe1b306b7ca19743e86d118e64d
Download size: 621 KB
Estimated disk space required: 9.8 MB (add 0.5 MB for tests)
Estimated build time: less than 0.1 SBU (with tests)

AccountsService Dependencies

Required

Polkit-124

Optional

GTK-Doc-1.33.2 and xmlto-0.0.28

Optional (for tests)

dbusmock-0.30.2 and PyGObject-3.46.0

Installation of AccountsService

First, rename a directory whose presence prevents the build system from running if dbusmock-0.30.2 is not installed:

mv tests/dbusmock{,-tests}

Then fix a test script so that the new directory is found, and adapt it for Python 3.12.0 or later:

sed -e '/accounts_service\.py/s/dbusmock/dbusmock-tests/' \
    -e 's/assertEquals/assertEqual/'                      \
    -i tests/test-libaccountsservice.py

Fix one test that fails if the en_IE.UTF-8 locale is not installed:

sed -i '/^SIMULATED_SYSTEM_LOCALE/s/en_IE.UTF-8/en_HK.iso88591/' tests/test-daemon.py

Install AccountsService by running the following commands:

mkdir build &&
cd    build &&

meson setup ..            \
      --prefix=/usr       \
      --buildtype=release \
      -Dadmin_group=adm   \
      -Delogind=true      \
      -Dsystemdsystemunitdir=no &&
ninja

To test the package, issue ninja test.

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Dadmin_group=adm: This switch sets the group for administrator accounts.

-Ddocbook=true: This switch enables building the D-Bus interface API documentation (needs xmlto-0.0.28).

-Dgtk_doc=true: This switch enables building the libaccountsservice API documentation (needs GTK-Doc-1.33.2).

-Dvapi=false: This switch disables building the vala bindings. Use it if you have not installed Vala-0.56.14.

Configuring AccountsService

To allow users in the adm group to be listed as Administrators, execute the following commands as the root user:

cat > /etc/polkit-1/rules.d/40-adm.rules << "EOF"
polkit.addAdminRule(function(action, subject) {
   return ["unix-group:adm"];
   });
EOF

Installed Programs: accounts-daemon (in /usr/libexec)

Installed Libraries: libaccountsservice.so

Installed Directories: /usr/include/accountsservice-1.0, /usr/share/accountsservice, /usr/share/gtk-doc/html/libaccountsservice (optional), and /var/lib/AccountsService

Short Descriptions

accounts-daemon	is the AccountsService daemon
`libaccountsservice.so`	contains the AccountsService API functions

acpid-2.0.34

Introduction to acpid

The acpid (Advanced Configuration and Power Interface event daemon) is a completely flexible, totally extensible daemon for delivering ACPI events. It listens on netlink interface and when an event occurs, executes programs to handle the event. The programs it executes are configured through a set of configuration files, which can be dropped into place by packages or by the user.

Note

Some other packages may handle some ACPI events as well and they may conflict with this package. For example, elogind-252.9 (read the documentation for Handle*= in logind.conf(5) for details) and UPower-1.90.2 (used by many desktop environments such as GNOME, KDE, and XFCE for handling ACPI events). If you've installed such a package and it's enough for your use case, this package is probably not needed. If you really need this package, you must be careful configuring it and the other packages handling ACPI events to avoid conflicts. Notably, elogind-252.9 handles some ACPI events by default, so the handling of these events by elogind-252.9 should be disabled first if handling these events with acpid (again, read logind.conf(5) for details).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/acpid2/acpid-2.0.34.tar.xz
Download MD5 sum: 988c2e3fd5ba0ea4492d3ba7273af295
Download size: 160 KB
Estimated disk space required: 1.9 MB
Estimated build time: less than 0.1 SBU

Installation of acpid

Install acpid by running the following commands:

./configure --prefix=/usr \
            --docdir=/usr/share/doc/acpid-2.0.34 &&
make

This package does not come with a test suite.

Now, as the root user:

make install                         &&
install -v -m755 -d /etc/acpi/events &&
cp -r samples /usr/share/doc/acpid-2.0.34

Configuring acpid

acpid is configured by user defined events. Place event files under /etc/acpi/events directory. If an event occurs, acpid recurses through the event files in order to see if the regex defined after "event" matches. If they do, action is executed.

The following brief example will suspend the system when the laptop lid is closed (it requires pm-utils-1.4.1). The example also disables the default handling of the lid close event by elogind-252.9 when the system is on battery and not connected to any external monitor, in order to avoid a conflict:

cat > /etc/acpi/events/lid << "EOF"
event=button/lid
action=/etc/acpi/lid.sh
EOF

cat > /etc/acpi/lid.sh << "EOF"
#!/bin/sh
/bin/grep -q open /proc/acpi/button/lid/LID/state && exit 0
/usr/sbin/pm-suspend
EOF
chmod +x /etc/acpi/lid.sh

mkdir -pv /etc/elogind/logind.conf.d
echo HandleLidSwitch=ignore > /etc/elogind/logind.conf.d/acpi.conf

Unfortunately, not every computer labels ACPI events in the same way (for example, the lid may be recognized as LID0 instead of LID). To determine how your buttons are recognized, use the acpi_listen tool. Also, look in the samples directory under /usr/share/doc/acpid-2.0.34 for more examples.

Boot Script

To automatically start acpid when the system is rebooted, install the /etc/rc.d/init.d/acpid boot script from the blfs-bootscripts-20240209 package.

make install-acpid

Installed Programs: acpid, acpi_listen, and kacpimon

Installed Libraries: None

Installed Directories: /etc/acpi and /usr/share/doc/acpid-2.0.34

Short Descriptions

acpid	is a program that listens for ACPI events and executes the rules that match the received event
acpi_listen	is a simple tool which connects to acpid and listens for events
kacpimon	is a monitor program that connects to three sources of ACPI events (events file, netlink and input layer) and then reports on what it sees while it is connected

at-3.2.5

Introduction to at

The at package provides delayed job execution and batch processing. It is required for Linux Standards Base (LSB) conformance.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://anduin.linuxfromscratch.org/BLFS/at/at_3.2.5.orig.tar.gz
Download MD5 sum: ca3657a1c90d7c3d252e0bc17feddc6e
Download size: 130 KB
Estimated disk space required: 1.9 MB (including tests)
Estimated build time: less than 0.1 SBU

at Dependencies

Required

An MTA

Optional

Linux-PAM-1.6.0

Installation of at

Before building at, as the root user you should create the group and user atd which will run the atd daemon:

groupadd -g 17 atd                                                  &&
useradd -d /dev/null -c "atd daemon" -g atd -s /bin/false -u 17 atd

Install at with the following commands:

./configure --with-daemon_username=atd        \
            --with-daemon_groupname=atd       \
            --with-jobdir=/var/spool/atjobs   \
            --with-atspool=/var/spool/atspool \
            SENDMAIL=/usr/sbin/sendmail       &&
make -j1

To test the results, issue: make test.

Now, as the root user:

make install docdir=/usr/share/doc/at-3.2.5 \
             atdocdir=/usr/share/doc/at-3.2.5

Configuring at

Config Files

/etc/at.allow and /etc/at.deny determines who can submit jobs via at or batch.

Linux PAM Configuration

If At has been built with Linux PAM support, you need to create a PAM configuration file, to get it working correctly with BLFS.

Issue the following commands as the root user to create the configuration file for Linux PAM:

cat > /etc/pam.d/atd << "EOF"
# Begin /etc/pam.d/atd

auth     required pam_unix.so
account  required pam_unix.so
password required pam_unix.so
session  required pam_unix.so

# End /etc/pam.d/atd
EOF

Boot Script

Install the /etc/init.d/atd init script from the blfs-bootscripts-20240209 package.

make install-atd

Installed Programs: at, atd, atq (symlink), atrm (symlink), atrun, and batch

Installed Libraries: None

Installed Directories: /usr/share/doc/at-3.2.5

Short Descriptions

at	queues, examines or deletes jobs for later execution
atd	is the daemon that runs jobs queued for later execution
atq	lists the user's pending jobs, or all jobs, if superuser
atrm	deletes jobs, identified by their job number
atrun	runs jobs queued for later execution
batch	is a script that executes commands when system load levels permit

autofs-5.1.9

Introduction to Autofs

Autofs controls the operation of the automount daemons. The automount daemons automatically mount filesystems when they are accessed and unmount them after a period of inactivity. This is done based on a set of pre-configured maps.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/linux/daemons/autofs/v5/autofs-5.1.9.tar.xz
Download MD5 sum: 06fb59a03c82364a0d788435b6853d70
Download size: 328 KB
Estimated disk space required: 5.7 MB
Estimated build time: less than 0.1 SBU

Autofs Dependencies

Required

libtirpc-1.3.4 and rpcsvc-proto-1.4.4

Optional

nfs-utils-2.6.4, libnsl-2.0.1, libxml2-2.12.5, MIT Kerberos V5-1.21.2, OpenLDAP-2.6.7 (client only), and Cyrus SASL-2.1.28

Kernel Configuration

Verify that automounter kernel support has been enabled:

File systems --->
  <*/M> Kernel automounter support (supports v3, v4 and v5)          [AUTOFS_FS]

Optionally, enable the following options in the kernel configuration:

File systems --->
  [*] Network File Systems --->                            [NETWORK_FILESYSTEMS]
    <*/M> NFS client support                                            [NFS_FS]
    <*/M> SMB3 and CIFS support (advanced network filesystem)             [CIFS]

Recompile and install the new kernel, if necessary.

Installation of Autofs

Install Autofs by running the following commands:

./configure --prefix=/usr             \
            --with-mapdir=/etc/autofs \
            --with-libtirpc           \
            --without-openldap        \
            --mandir=/usr/share/man   &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Caution

If autofs is already installed on your system, be sure to backup your configuration files. They'll be overwritten by the following command.

Install the default configuration files, still as the root user:

make install_samples

Command Explanations

--with-libtirpc: This switch forces the package to use libtirpc for RPC functionality instead of relying on implementation from Glibc, which was removed in LFS 8.1.

--without-openldap: This switch disables openldap if found. If openldap is desired, omit this switch. Note that openldap support in autofs requires MIT Kerberos V5-1.21.2.

Configuring Autofs

Config Files

/etc/sysconfig/autofs.conf, /etc/autofs/auto.master, /etc/autofs/auto.misc, and /etc/autofs/auto.net

Configuration Information

The installation process creates auto.master, auto.misc, auto.smb, and auto.net. Replace the auto.master file with the following commands as the root user:

mv /etc/autofs/auto.master /etc/autofs/auto.master.bak &&
cat > /etc/autofs/auto.master << "EOF"
# Begin /etc/autofs/auto.master

/media/auto  /etc/autofs/auto.misc  --ghost
#/home        /etc/autofs/auto.home

# End /etc/autofs/auto.master
EOF

This file creates a new media directory, /media/auto that will overlay any existing directory of the same name. In this example, the file, /etc/autofs/auto.misc, has a line:

cd   -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

that will mount a cdrom as /media/auto/cd if that directory is accessed. The --ghost option tells the automounter to create “ghost” versions (i.e. empty directories) of all the mount points listed in the configuration file regardless whether any of the file systems are actually mounted or not. This is very convenient and highly recommended, because it will show you the available auto-mountable file systems as existing directories, even when their file systems aren't currently mounted. Without the --ghost option, you'll have to remember the names of the directories. As soon as you try to access one of them, the directory will be created and the file system will be mounted. When the file system gets unmounted again, the directory is destroyed too, unless the --ghost option was given.

Note

An alternative method would be to specify another automount location such as /var/lib/auto/cdrom and create a symbolic link from /media/cdrom to the automount location.

The auto.misc file must be configured to your working hardware. The loaded configuration file should load your cdrom if /dev/cdrom is active or it can be edited to match your device setup. Examples for floppies are available in the file and easily activated. Documentation for this file is available using the man 5 autofs command.

In the second line, if enabled, a user's home directory would be mounted via NFS upon login. The /etc/home.auto would need to exist and have an entry similar to:

joe  example.org:/export/home/joe

where the directory /export/home/joe is exported via NFS from the system example.org. NFS shares are covered on the next page.

This package could also be used to mount SMB shares, however that feature is not configured in these instructions. For additional configuration information, see the man pages for auto.master(5). There are also web resources such as this AUTOFS HOWTO available.

Boot Script

autofs installs its own boot script, but it has no capability for logging or visual conformance with other BLFS scripts. It will be replaced by an enhanced version.

Install the /etc/init.d/autofs mount script included with the blfs-bootscripts-20240209 package.

make install-autofs

The time-out variable is set in /etc/sysconfig/autofs.conf. The installed file sets a default of 60 seconds of inactivity before unmounting the device. A much shorter time may be necessary to protect buffer writing to a floppy if users tend to remove the media prior to the timeout setting.

Installed Program: automount

Installed Libraries: libautofs.so. lookup_dir.so, lookup_file.so, lookup_files.so (symlink to lookup_file.so), lookup_hosts.so, lookup_ldap.so (optional), lookup_multi.so, lookup_nis.so (symlink to lookup_yp.so), lookup_program.so, lookup_userhome.so, lookup_yp.so, mount_afs.so, mount_autofs.so, mount_bind.so, mount_changer.so, mount_ext2.so, mount_ext3.so (symlink to mount_ext2.so), mount_ext4.so (symlink to mount_ext2.so), mount_generic.so, mount_nfs.so, mount_nfs4.so (symlink to mount_nfs.so), parse_amd.so, and parse_sun.so

Installed Directories: /usr/lib/autofs and /etc/autofs

Short Descriptions

automount

is the daemon that performs the mounting when a request is made for the device

BlueZ-5.72

Introduction to BlueZ

The BlueZ package contains the Bluetooth protocol stack for Linux.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
Download MD5 sum: fcacd4d6d65f7da141977a2beb1ba78f
Download size: 2.3 MB
Estimated disk space required: 81 MB (add 84 MB for tests)
Estimated build time: 0.4 SBU (using parallelism=4; with tests)

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/bluez-5.72-obexd_without_systemd-1.patch

BlueZ Dependencies

Required

dbus-1.14.10, GLib-2.78.4, and libical-3.0.17

Optional

docutils-0.20.1 (to generate man pages)

Kernel Configuration

If you are building this package to use bluetooth devices (rather than as a build dependency), enable the following options in the kernel configuration, also the options in the “Cryptographic API” section if you intend to run the tests, and recompile the kernel if necessary:

General setup --->
  # If it is disabled, [TIMERFD] and [EVENTFD] will be hidden and
  # enabled implicitly.  We DO NOT recommend to enable [EXPERT]
  # unless you are really an expert user:
  [ /*] Configure standard kernel features (expert users) --->          [EXPERT]
    [*] Enable timerfd() system call                                   [TIMERFD]
    [*] Enable eventfd() system call                                   [EVENTFD]

[*] Networking support --->                                                [NET]
  <*/M> Bluetooth subsystem support --->                                    [BT]
    [*]   Bluetooth Classic (BR/EDR) features                         [BT_BREDR]
    <*/M>   RFCOMM protocol support                                  [BT_RFCOMM]
    [*]       RFCOMM TTY support                                 [BT_RFCOMM_TTY]
    <*/M>   BNEP protocol support                                      [BT_BNEP]
    [*]       Multicast filter support                       [BT_BNEP_MC_FILTER]
    [*]       Protocol filter support                     [BT_BNEP_PROTO_FILTER]
    <*/M>   HIDP protocol support                                      [BT_HIDP]
    Bluetooth device drivers --->
      # Select the appropriate drivers for your bluetooth hardware.
      # There are more vendor-specific drivers not listed here:
      < /*/M> HCI USB driver                                       [BT_HCIBTUSB]
      < /*/M> HCI SDIO driver                                     [BT_HCIBTSDIO]
      < /*/M> HCI UART driver                                       [BT_HCIUART]
  <*/M> RF switch subsystem support --->                                [RFKILL]

-*- Cryptographic API --->                                              [CRYPTO]
  Crypto core or helper --->
    <*/M> Userspace cryptographic algorithm configuration          [CRYPTO_USER]
  Block ciphers --->
    <*/M> AES (Advanced Encryption Standard)                        [CRYPTO_AES]
  AEAD (authenticated encryption with associated data) ciphers --->
    <*/M> CCM (Counter with Cipher Block Chaining-MAC)              [CRYPTO_CCM]
  Hashes, digests, and MACs --->
    <*/M> CMAC (Cipher-based MAC)                                  [CRYPTO_CMAC]
  Userspace interface --->
    <*/M> Hash algorithms                                 [CRYPTO_USER_API_HASH]
    <*/M> Symmetric key cipher algorithms             [CRYPTO_USER_API_SKCIPHER]
    <*/M> AEAD cipher algorithms                          [CRYPTO_USER_API_AEAD]

Installation of BlueZ

Now, make some changes needed for SystemV systems:

patch -Np1 -i ../bluez-5.72-obexd_without_systemd-1.patch

Install BlueZ by running the following commands:

./configure --prefix=/usr         \
            --sysconfdir=/etc     \
            --localstatedir=/var  \
            --enable-library      \
            --disable-manpages    \
            --disable-systemd     &&
make

To test the results, issue: make check.

Now, as the root user:

make install &&
ln -svf ../libexec/bluetooth/bluetoothd /usr/sbin

Install the main configuration file as the root user:

install -v -dm755 /etc/bluetooth &&
install -v -m644 src/main.conf /etc/bluetooth/main.conf

If desired, install the API documentation as the root user:

install -v -dm755 /usr/share/doc/bluez-5.72 &&
install -v -m644 doc/*.txt /usr/share/doc/bluez-5.72

Command Explanations

--disable-manpages: This switch disables generating the manual pages because of the reliance on 'rst2man' in docutils. Remove this switch if you have docutils-0.20.1 installed and wish to generate the manual pages.

--enable-library: This switch enables building the BlueZ 4 compatibility library which is required by some applications.

--disable-systemd: This switch is needed because systemd is not part of LFS/BLFS. If you are using systemd, remove this switch.

ln -svf ../libexec/bluetooth/bluetoothd /usr/sbin: This command makes access to the bluetooth daemon more convenient.

Configuring BlueZ

Configuration Files

/etc/bluetooth/main.conf is installed automatically during the install. Additionally, there are three supplementary configuration files. /etc/sysconfig/bluetooth is installed as a part of the boot script below. In addition, you optionally can install the following, as the root user:

cat > /etc/bluetooth/rfcomm.conf << "EOF"
# Start rfcomm.conf
# Set up the RFCOMM configuration of the Bluetooth subsystem in the Linux kernel.
# Use one line per command
# See the rfcomm man page for options


# End of rfcomm.conf
EOF

cat > /etc/bluetooth/uart.conf << "EOF"
# Start uart.conf
# Attach serial devices via UART HCI to BlueZ stack
# Use one line per device
# See the hciattach man page for options

# End of uart.conf
EOF

Boot Script

To automatically start the bluetoothd daemon when the system is rebooted, install the /etc/rc.d/init.d/bluetooth bootscript from the blfs-bootscripts-20240209 package.

make install-bluetooth

Installed Programs: bluemoon, bluetoothctl, bluetoothd (symlink), btattach, btmon, hex2hcd, l2ping, l2test, mpris-proxy, and rctest

Installed Library: libbluetooth.so

Installed Directories: /etc/bluetooth, /usr/{include,libexec}/bluetooth, and /usr/share/doc/bluez-5.72

Short Descriptions

bluemoon	is a Bluemoon configuration utility
bluetoothctl	is the interactive Bluetooth control program
bluetoothd	is the Bluetooth daemon
btmon	provides access to the Bluetooth subsystem monitor infrastructure for reading HCI traces
hex2hcd	is used to convert a file needed by Broadcom devices to hcd (Broadcom bluetooth firmware) format
l2ping	is used to send a L2CAP echo request to the Bluetooth MAC address given in dotted hex notation
l2test	is a L2CAP testing program
rctest	is used to test RFCOMM communications on the Bluetooth stack
`libbluetooth.so`	contains the BlueZ 4 API functions

Bubblewrap-0.8.0

Introduction to Bubblewrap

Bubblewrap is a setuid implementation of user namespaces, or sandboxing, that provides access to a subset of kernel user namespace features. Bubblewrap allows user owned processes to run in an isolated environment with limited access to the underlying filesystem.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/containers/bubblewrap/releases/download/v0.8.0/bubblewrap-0.8.0.tar.xz
Download MD5 sum: fc0e14bc26df76225e8f8cc2df9fb657
Download size: 148 KB
Estimated disk space required: 3.4 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

Bubblewrap Dependencies

Optional

libxslt-1.1.39 (to generate manual pages) and libseccomp-2.5.5 (built with python bindings, for tests)

Kernel Configuration

When this package began, upstream expected it could be installed suid-root. That was a long time ago, suid-root is generally considered a bad idea. As well as the default namespaces, this package requires the optional User namespace to be enabled. If that has not yet been enabled, select the following option in the kernel configuration and recompile the kernel:

General setup --->
  -*- Namespaces support --->                                       [NAMESPACES]
    [*] User namespace                                                 [USER_NS]

Installation of Bubblewrap

Install Bubblewrap by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr --buildtype=release .. &&
ninja

Next, if you desire to run the test suite, fix an issue caused by the merged-/usr configuration in LFS:

sed 's@symlink usr/lib64@ro-bind-try /lib64@' -i ../tests/libtest.sh

To test the results, issue (as a user other than the root user): ninja test

Now, as the root user:

ninja install

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

Installed Program: bwrap

Installed Libraries: None

Installed Directories: None

Short Descriptions

bwrap

generates a sandbox for a program to run in

Colord-1.4.7

Introduction to Colord

Colord is a system service that makes it easy to manage, install, and generate color profiles. It is used mainly by GNOME Color Manager for system integration and use when no users are logged in.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/colord/releases/colord-1.4.7.tar.xz
Download MD5 sum: 94bd795efa1931a34990345e4ac439a8
Download size: 1.7 MB
Estimated disk space required: 18 MB (with tests)
Estimated build time: 0.4 SBU (with tests)

Colord Dependencies

Required

dbus-1.14.10, GLib-2.78.4, Little CMS-2.14, Polkit-124, and SQLite-3.45.1

Optional

gnome-desktop-44.0 and colord-gtk-0.3.1 (to build the example tools), DocBook-utils-0.6.14, GTK-Doc-1.33.2, libxslt-1.1.39, SANE-1.2.1, ArgyllCMS, and Bash Completion

Installation of Colord

There should be a dedicated user and group to take control of the colord daemon after it has started. Issue the following commands as the root user:

groupadd -g 71 colord &&
useradd -c "Color Daemon Owner" -d /var/lib/colord -u 71 \
        -g colord -s /bin/false colord

Install Colord by running the following commands:

mkdir build &&
cd    build &&

meson setup ..                 \
      --prefix=/usr            \
      --buildtype=release      \
      -Ddaemon_user=colord     \
      -Dvapi=true              \
      -Dsystemd=false          \
      -Dlibcolordcompat=true   \
      -Dargyllcms_sensor=false \
      -Dbash_completion=false  \
      -Ddocs=false             \
      -Dman=false              &&
ninja

Now, as the root user:

ninja install

To test the results, issue: ninja test. One test, colord-self-test-daemon, will fail if the package is already installed. The test suite must be run with the system-wide D-Bus Daemon running.

Command Explanations

--buildtype=release: Specify a buildtype suitable for stable releases of the package, as the default may produce unoptimized binaries.

-Ddaemon_user=colord: This switch is used so the colord daemon will run as an unprivileged user instead of the root user.

-Dvapi=true: This switch enables building the Vala bindings. Remove if you don't have Vala-0.56.14 installed.

-Dsystemd=false: This switch disables support for systemd login in Colord applications.

-Dlibcolordcompat=true: This switch enables building a compatibility library for older packages that use Colord.

-Dargyllcms_sensor=false: This switch disables the ArgLLCMS sensor driver. Omit if you have ArgyllCMS installed and wish to use it.

-Dbash_completion=false: This switch disables Bash Completion support for Colord applications.

-Ddocs=false: This switch disables building of documentation. Omit if you have GTK-Doc-1.33.2 available.

-Dman=false: This switch disables building of man pages. Omit if you have DocBook-utils-0.6.14 available. Namespaced versions of the docbook-xsl stylesheets are also required.

Installed Programs: cd-create-profile, cd-fix-profile, cd-iccdump, cd-it8, and colormgr

Installed Libraries: libcolord.so, libcolordcompat.so, libcolordprivate.so, and libcolorhug.so

Installed Directories: /usr/include/colord-1, /usr/lib/colord-{plugins,sensors}, /usr/share/color{d}, /usr/share/gtk-doc/html/colord, and /var/lib/colord

Short Descriptions

cd-create-profile	is the Color Manager Profile Creation Tool
cd-fix-profile	is a tool used to fix metadata in ICC profiles
cd-iccdump	dumps the contents of an ICC profile as human readable text
cd-it8	is the Color Manager Testing Tool
colormgr	is a text-mode program that allows you to interact with colord on the command line
`libcolord.so`	contains the Colord API functions
`libcolordcompat.so`	contains legacy API functions for compatibility with older applications
`libcolordprivate.so`	contains internal API functions for the programs included with Colord
`libcolorhug.so`	contains a simple display hardware colorimiter

cpio-2.15

Introduction to cpio

The cpio package contains tools for archiving.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/cpio/cpio-2.15.tar.bz2
Download MD5 sum: 3394d444ca1905ea56c94b628b706a0b
Download size: 1.6 MB
Estimated disk space required: 21 MB (with tests and docs)
Estimated build time: 0.3 SBU (with tests and docs)

CPIO Dependencies

Optional

texlive-20230313 (or install-tl-unx)

Installation of cpio

Install cpio by running the following commands:

./configure --prefix=/usr \
            --enable-mt   \
            --with-rmt=/usr/libexec/rmt &&
make &&
makeinfo --html            -o doc/html      doc/cpio.texi &&
makeinfo --html --no-split -o doc/cpio.html doc/cpio.texi &&
makeinfo --plaintext       -o doc/cpio.txt  doc/cpio.texi

If you have texlive-20230313 installed and wish to create PDF or Postscript documentation, issue one or both of the following commands:

make -C doc pdf &&
make -C doc ps

To test the results, issue: make check.

Now, as the root user:

make install &&
install -v -m755 -d /usr/share/doc/cpio-2.15/html &&
install -v -m644    doc/html/* \
                    /usr/share/doc/cpio-2.15/html &&
install -v -m644    doc/cpio.{html,txt} \
                    /usr/share/doc/cpio-2.15

If you built PDF or Postscript documentation, install it by issuing the following commands as the root user:

install -v -m644 doc/cpio.{pdf,ps,dvi} \
                 /usr/share/doc/cpio-2.15

Command Explanations

--enable-mt: This parameter forces the building and installation of the mt program.

--with-rmt=/usr/libexec/rmt: This parameter inhibits building the rmt program as it is already installed by the Tar package in LFS.

Installed Programs: cpio and mt

Installed Libraries: None

Installed Directories: /usr/share/doc/cpio-2.15

Short Descriptions

cpio	copies files to and from archives
mt	controls magnetic tape drive operations

cups-pk-helper-0.2.7

Introduction to cups-pk-helper

The cups-pk-helper package contains a PolicyKit helper used to configure Cups with fine-grained privileges.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/cups-pk-helper/releases/cups-pk-helper-0.2.7.tar.xz
Download MD5 sum: 0cdadec9ea8f88b7fc7af8ca206da2bd
Download size: 56 KB
Estimated disk space required: 5.3 MB
Estimated build time: 0.1 SBU

cups-pk-helper Dependencies

Required

Cups-2.4.7 and Polkit-124

Installation of cups-pk-helper

Install cups-pk-helper by running the following commands:

mkdir build &&
cd    build &&

meson setup --prefix=/usr .. &&
ninja

This package does not come with a test suite.

Now, as the root user:

ninja install

Installed Programs: cups-pk-helper-mechanism (library executable)

Installed Libraries: None

Installed Directories: None

dbus-1.14.10

Introduction to D-Bus

D-Bus is a message bus system, a simple way for applications to talk to one another. D-Bus supplies both a system daemon (for events such as “new hardware device added” or “printer queue changed”) and a per-user-login-session daemon (for general IPC needs among user applications). Also, the message bus is built on top of a general one-to-one message passing framework, which can be used by any two applications to communicate directly (without going through the message bus daemon).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://dbus.freedesktop.org/releases/dbus/dbus-1.14.10.tar.xz
Download MD5 sum: 46070a3487817ff690981f8cd2ba9376
Download size: 1.3 MB
Estimated disk space required: 23 MB (add 25 MB for tests)
Estimated build time: 0.2 SBU (add 1.5 SBU for tests)

D-Bus Dependencies

Optional

For the tests: D-Bus Python-1.3.2, PyGObject-3.46.0, and Valgrind-3.22.0; for documentation: Doxygen-1.10.0, xmlto-0.0.28, Ducktype, and Yelp Tools

Installation of D-Bus

Install D-Bus by running the following commands (you may wish to review the output from ./configure --help first and add any desired parameters to the configure command shown below):

./configure --prefix=/usr                        \
            --sysconfdir=/etc                    \
            --localstatedir=/var                 \
            --runstatedir=/run                   \
            --disable-doxygen-docs               \
            --disable-xml-docs                   \
            --disable-static                     \
            --with-systemduserunitdir=no         \
            --with-systemdsystemunitdir=no       \
            --docdir=/usr/share/doc/dbus-1.14.10  \
            --with-system-socket=/run/dbus/system_bus_socket &&
make

See below for test instructions.

Now, as the root user:

make install

If you are using a DESTDIR install, dbus-daemon-launch-helper needs to be fixed afterwards. Issue, as root user:

chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &&
chmod -v      4750       /usr/libexec/dbus-daemon-launch-helper

If you are still building your system in chroot or you did not start the daemon yet, but you want to compile some packages that require D-Bus, generate the D-Bus UUID to avoid warnings when compiling some packages with the following command as the root user:

dbus-uuidgen --ensure

If using elogind-252.9, create a symlink to the /var/lib/dbus/machine-id file:

ln -sfv /var/lib/dbus/machine-id /etc

Many tests are disabled unless both D-Bus Python-1.3.2 and PyGObject-3.46.0 have been installed. They must be run as an unprivileged user from a local session with bus address. To run the standard tests issue make check.

If you want to run the unit regression tests, configure requires additional parameters which expose additional functionality in the binaries that are not intended to be used in a production build of D-Bus. If you would like to run the tests, issue the following commands (for the tests, you don't need to build the docs):

make distclean                                    &&
PYTHON=python3 ./configure --enable-tests         \
                           --enable-asserts       \
                           --disable-doxygen-docs \
                           --disable-xml-docs     &&
make                                              &&
make check

One test, test-autolaunch, is known to fail. There have also been reports that the tests may fail if running inside a Midnight Commander shell. You may get out-of-memory error messages when running the tests. These are normal and can be safely ignored.

Command Explanations

--disable-doxygen-docs: This switch disables doxygen documentation build and install, if you have doxygen installed. If doxygen is installed, and you wish to build them, remove this parameter.

--disable-xml-docs: This switch disables html documentation build and install, if you have xmlto installed. If xmlto is installed, and you wish to build them, remove this parameter.

--disable-static: This switch prevents installation of static versions of the libraries.

--with-systemd{user,system}unitdir=no: These switches disable installation of systemd units on elogind based systems.

--with-system-socket=/run/dbus/system_bus_socket: This parameter specifies the location of the system bus socket.

--enable-tests: Builds extra parts of the code to support all tests. Do not use on a production build.

--enable-embedded-tests: Builds extra parts of the code to support only unit tests. Do not use on a production build.

--enable-asserts: Enables debugging code to run assertions for statements normally assumed to be true. This prevents a warning that '--enable-tests' on its own is only useful for profiling and might not give true results for all tests, but adds its own NOTE that this should not be used in a production build.

Configuring D-Bus

Config Files

/etc/dbus-1/session.conf, /etc/dbus-1/system.conf and /etc/dbus-1/system.d/*

Configuration Information

The configuration files listed above should probably not be modified. If changes are required, you should create /etc/dbus-1/session-local.conf and/or /etc/dbus-1/system-local.conf and make any desired changes to these files.

If any packages install a D-Bus .service file outside of the standard /usr/share/dbus-1/services directory, that directory should be added to the local session configuration. For instance, /usr/local/share/dbus-1/services can be added by performing the following commands as the root user:

cat > /etc/dbus-1/session-local.conf << "EOF"
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- Search for .service files in /usr/local -->
  <servicedir>/usr/local/share/dbus-1/services</servicedir>

</busconfig>
EOF

D-Bus Session Daemon

To automatically start dbus-daemon when the system is rebooted, install the /etc/rc.d/init.d/dbus bootscript from the blfs-bootscripts-20240209 package.

make install-dbus

If this is the first time to install D-Bus on the system and you are not operating in a chroot environment, you can immediately start dbus-daemon without rebooting the system:

/etc/init.d/dbus start

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 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 available parameters and options. Here are some suggestions and examples:

Add dbus-launch to the line in the ~/.xinitrc file that starts your graphical desktop environment.
If you use gdm or some other display manager that calls the ~/.xsession file, you can add dbus-launch to the line in your ~/.xsession file that starts your graphical desktop environment. The syntax would be similar to the example in the ~/.xinitrc file.
The examples shown previously use dbus-launch to specify a program to be run. This has the benefit (when also using the --exit-with-x11 parameter) of stopping the session daemon when the specified program is stopped. You can also start the session daemon in your system or personal startup scripts by adding the following lines:
```
# Start the D-Bus session daemon
eval `dbus-launch`
export DBUS_SESSION_BUS_ADDRESS
```
This method will not stop the session daemon when you exit your shell, therefore you should add the following line to your ~/.bash_logout file:
```
# Kill the D-Bus session daemon
kill $DBUS_SESSION_BUS_PID
```

Installed Programs: dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor, dbus-run-session, dbus-send, dbus-test-tool, dbus-update-activation-environment, and dbus-uuidgen

Installed Library: libdbus-1.so

Installed Directories: /etc/dbus-1, /usr/{include,lib}/dbus-1.0, /usr/lib/cmake/DBus1, /usr/share/dbus-1, /usr/share/xml/dbus-1, /usr/share/doc/dbus-1.14.10, and /var/{lib,run}/dbus

Short Descriptions

dbus-cleanup-sockets	is used to clean up leftover sockets in a directory
dbus-daemon	is the D-Bus message bus daemon
dbus-launch	is used to start dbus-daemon from a shell script. It would normally be called from a user's login scripts
dbus-monitor	is used to monitor messages going through a D-Bus message bus
dbus-run-session	starts a process as a new D-Bus session
dbus-send	is used to send a message to a D-Bus message bus
dbus-test-tool	is a D-Bus traffic generator and test tool; it is a multi-purpose tool for debugging and profiling D-Bus
dbus-update-activation-environment	is used to update the environment used for D-Bus session services; it updates the list of environment variables used by dbus-daemon --session when it activates session services without using systemd
dbus-uuidgen	is used to generate a universally unique ID
`libdbus-1.so`	contains the API functions used by the 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

elogind-252.9

Introduction to elogind

elogind is the systemd project's "logind", extracted to be a standalone daemon. It integrates with Linux-PAM-1.6.0 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 interface, and also through the file system using systemd's standard /run/systemd layout.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/elogind/elogind/archive/v252.9/elogind-252.9.tar.gz
Download MD5 sum: 2be2c43298e2fc41c5bee33dde605f01
Download size: 1.8 MB
Estimated disk space required: 45 MB (with tests)
Estimated build time: 0.3 SBU (with parallelism=4)

elogind Dependencies

Optional

lxml-4.9.4, zsh-5.9, Valgrind-3.22.0 (needed for tests), audit-userspace, bash-completion, kexec, and SELinux

Editor Notes: https://wiki.linuxfromscratch.org/blfs/wiki/Logind

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel if necessary:

File systems --->
  [*] Inotify support for userspace                               [INOTIFY_USER]
  Pseudo filesystems --->
    [*] Tmpfs virtual memory file system support (former shm fs)         [TMPFS]
    [*]   Tmpfs POSIX Access Control Lists                     [TMPFS_POSIX_ACL]

In addition, some tests need the userspace cryptographic kernel API, which is enabled with:

-*- Cryptographic API --->                                              [CRYPTO]
  Crypto core or helper --->
    <*/M> Userspace cryptographic algorithm configuration          [CRYPTO_USER]
  Userspace interface --->
    <*/M> Hash algorithms                                 [CRYPTO_USER_API_HASH]

Installation of elogind

Install elogind by running the following commands:

mkdir build &&
cd    build &&

meson setup ..                              \
      --prefix=/usr                         \
      --buildtype=release                   \
      -Dman=auto                            \
      -Ddocdir=/usr/share/doc/elogind-252.9 \
      -Dcgroup-controller=elogind           \
      -Ddev-kvm-mode=0660                   \
      -Ddbuspolicydir=/etc/dbus-1/system.d &&
ninja

To test the results, issue: ninja test. A few tests are skipped if not run with root privileges. Two tests named test-fs-util and test-id128 require the /etc/machine-id symlink, so they will fail if this symlink is not created following the instruction in dbus-1.14.10 yet.

Now, as the root user:

ninja install                                           &&
ln -sfv  libelogind.pc /usr/lib/pkgconfig/libsystemd.pc &&
ln -sfvn elogind /usr/include/systemd

Command Explanations

-Ddocdir=/usr/share/doc/elogind-252.9: This is needed to install documentation in a versioned directory.

-Dcgroup-controller=elogind: This switch is necessary to build this package when the kernel is not built with CONFIG_CGROUPS enabled. Note that elogind strictly needs a kernel with CONFIG_CGROUPS enabled at runtime, but this switch will allow building the package first.

-Ddbuspolicydir=/etc/dbus-1/system.d: This switch sets the location of the D-Bus policy directory.

-Ddev-kvm-mode=0660: The LFS udev rule sets the mode of /dev/kvm to 0660. This option ensures the elogind udev rules consistent with the LFS configuration.

-Dman=auto: The default value of this switch is false. Setting it to auto allows building and installing the man pages if the recommended dependencies are installed.

-Dhtml=auto: The default value of this switch is false. Setting it to auto allows building and installing the html documentation if the recommended dependencies are installed.

-Ddefault-kill-user-processes=false: Determines whether the processes of a user should be killed when the user logs out. The default is true, but this defeats the traditional use of screen or tmux. This can also be changed in the configuration file (see below).

ln -s ...: These commands install symlinks so that software packages can find the systemd-compatible library and headers.

Configuring elogind

Config File

/etc/elogind/logind.conf

Configuration Information

The installed file /etc/elogind/logind.conf contains all the possible options with their defaults, commented out. You may wish to disable automatically killing user processes when the user logs out, by running, as the root user:

sed -e '/\[Login\]/a KillUserProcesses=no' \
    -i /etc/elogind/logind.conf

Each user will need to register a user session using 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 commands as the root user:

cat >> /etc/pam.d/system-session << "EOF" &&
# Begin elogind addition

session  required    pam_loginuid.so
session  optional    pam_elogind.so

# End elogind addition
EOF
cat > /etc/pam.d/elogind-user << "EOF"
# Begin /etc/pam.d/elogind-user

account  required    pam_access.so
account  include     system-account

session  required    pam_env.so
session  required    pam_limits.so
session  required    pam_unix.so
session  required    pam_loginuid.so
session  optional    pam_keyinit.so force revoke
session  optional    pam_elogind.so

auth     required    pam_deny.so
password required    pam_deny.so

# End /etc/pam.d/elogind-user
EOF

Note

After completion of elogind, you should check that it functions properly. First ensure that dbus is running. It may be easiest to do this by rebooting the system. After logging in again, run the command loginctl. The result should indicate that a SESSION and a SEAT have been created.

Installed Programs: busctl, elogind-inhibit, and loginctl

Installed Library: libelogind.so

Installed Directories: /usr/lib/elogind, /etc/elogind, /usr/include/elogind, and /usr/share/doc/elogind-252.9

Short Descriptions

busctl	is used to introspect and monitor the D-Bus bus
elogind-inhibit	is used to execute a program with a shutdown, sleep or idle inhibitor lock taken
loginctl	is used to introspect and control the state of the elogind Login Manager
`libelogind.so`	is the main elogind utility library

blocaled-0.5

Introduction to blocaled

blocaled is an implementation of the org.freedesktop.locale1 D-Bus protocol, which normally comes with systemd. It is needed by the GNOME desktop.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/lfs-book/blocaled/releases/download/v0.5/blocaled-0.5.tar.xz
Download MD5 sum: 04d9833d0dfbf3609b0d8f6d276812ff
Download size: 262 KB
Estimated disk space required: 4.2 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)

blocaled Dependencies

Required

Polkit-124 and libdaemon-0.14

Installation of blocaled

Install blocaled by running the following commands:

./configure --prefix=/usr --sysconfdir=/etc &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Configuring blocaled

Config Files

/etc/blocaled.conf

Configuration Information

/etc/blocaled.conf contains the location of the settings files used by blocaled. The defaults are suitable for BLFS. Information about the entries is available as comments in the file.

The org.freedesktop.locale1 protocol is unable to export locale variables. Locale settings are stored by default in /etc/locale.conf. We need to retrieve them in the bash profile. As the root user, issue:

cat > /etc/profile.d/i18n.sh << "EOF"
# Begin /etc/profile.d/i18n.sh

if [ -r /etc/locale.conf ]; then source /etc/locale.conf; fi

if [ -n "$LANG" ];              then export LANG; fi
if [ -n "$LC_TYPE" ];           then export LC_TYPE; fi
if [ -n "$LC_NUMERIC" ];        then export LC_NUMERIC; fi
if [ -n "$LC_TIME" ];           then export LC_TIME; fi
if [ -n "$LC_COLLATE" ];        then export LC_COLLATE; fi
if [ -n "$LC_MONETARY" ];       then export LC_MONETARY; fi
if [ -n "$LC_MESSAGES" ];       then export LC_MESSAGES; fi
if [ -n "$LC_PAPER" ];          then export LC_PAPER; fi
if [ -n "$LC_NAME" ];           then export LC_NAME; fi
if [ -n "$LC_ADDRESS" ];        then export LC_ADDRESS; fi
if [ -n "$LC_TELEPHONE" ];      then export LC_TELEPHONE; fi
if [ -n "$LC_MEASUREMENT" ];    then export LC_MEASUREMENT; fi
if [ -n "$LC_IDENTIFICATION" ]; then export LC_IDENTIFICATION; fi

# End /etc/profile.d/i18n.sh
EOF

Then the /etc/locale file should be generated, as the root user:

cat > /etc/locale.conf << EOF
# Begin /etc/locale.conf

LANG=$LANG

# End /etc/locale.conf
EOF

If you plan to run an X (or Wayland) Window system, you may want to set up your X keyboard. The best way to do it is to retrieve the settings from /etc/sysconfig/console, and feed them to the blocaled daemon. As the root user:

source /etc/sysconfig/console &&
KEYMAP=${KEYMAP:-us}          &&

gdbus call --system                                             \
           --dest org.freedesktop.locale1                       \
           --object-path /org/freedesktop/locale1               \
           --method org.freedesktop.locale1.SetVConsoleKeyboard \
           "$KEYMAP" "$KEYMAP_CORRECTIONS" true true

This should create or modify the Xorg configuration file (default is /etc/X11/xorg.conf.d/30-keyboard.conf) to match the keyboard settings set in KEYMAP.

Installed Program: blocaled (in /usr/libexec)

Installed Library: None

Installed Directory: /usr/share/blocaled

Short Descriptions

blocaled

is the daemon implementing the org.freedesktop.locale1 D-Bus protocol

Fcron-3.2.1

Introduction to Fcron

The Fcron package contains a periodical command scheduler which aims at replacing Vixie Cron.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://fcron.free.fr/archives/fcron-3.2.1.src.tar.gz
Download MD5 sum: bd4996e941a40327d11efc5e3fd1f839
Download size: 587 KB
Estimated disk space required: 5.1 MB
Estimated build time: 0.1 SBU

Fcron Dependencies

Optional

An MTA, text editor (default is vi from the Vim-9.1.0041 package), Linux-PAM-1.6.0, and DocBook-utils-0.6.14

Installation of Fcron

Fcron uses the cron facility of syslog to log all messages. Since LFS does not set up this facility in /etc/syslog.conf, it needs to be done prior to installing Fcron. This command will append the necessary line to the current /etc/syslog.conf (perform as the root user):

cat >> /etc/syslog.conf << "EOF"
# Begin fcron addition to /etc/syslog.conf

cron.* -/var/log/cron.log

# End fcron addition
EOF

The configuration file has been modified, so reloading the sysklogd daemon will activate the changes (again as the root user).

/etc/rc.d/init.d/sysklogd reload

For security reasons, an unprivileged user and group for Fcron should be created (perform as the root user):

groupadd -g 22 fcron &&
useradd -d /dev/null -c "Fcron User" -g fcron -s /bin/false -u 22 fcron

Now fix some locations hard coded in the documentation:

find doc -type f -exec sed -i 's:/usr/local::g' {} \;

Install Fcron by running the following commands:

./configure --prefix=/usr          \
            --sysconfdir=/etc      \
            --localstatedir=/var   \
            --without-sendmail     \
            --with-boot-install=no \
            --with-systemdsystemunitdir=no &&
make

This package does not come with a test suite.

Now, as the root user:

make install

DESTDIR install must be done as root user. Furthermore, if PAM configuration files should be installed in /etc/pam.d, you have to create this directory in the DESTDIR before doing the install.

Command Explanations

--without-sendmail: By default, Fcron will attempt to use the sendmail command from an MTA package to email you the results of the fcron script. This switch is used to disable default email notification. Omit the switch to enable the default. Alternatively, you can use the --with-sendmail=</path/to/MTA command> to use a different mailer command.

--with-boot-install=no: This prevents installation of the bootscript included with the package.

--with-systemdsystemunitdir=no: This prevents building the systemd units, which are not needed for a SYS V system.

--with-editor=</path/to/editor>: This switch allows you to set the default text editor.

--with-dsssl-dir=</path/to/dsssl-stylesheets>: May be used if you have DocBook-utils-0.6.14 installed. Currently, the dsssl stylesheets are located at /usr/share/sgml/docbook/dsssl-stylesheets-1.79.

Configuring Fcron

Config Files

/etc/fcron.conf, /etc/fcron.allow, and /etc/fcron.deny

Configuration Information

There are no required changes in any of the config files. Configuration information can be found in the man page for fcron.conf.

fcron scripts are written using fcrontab. Refer to the fcrontab man page for proper parameters to address your situation.

If Linux-PAM is installed, two PAM configuration files are installed in etc/pam.d. Alternatively if etc/pam.d is not used, the installation will append two configuration sections to the existing /etc/pam.conf file. You should ensure the files match your preferences. Modify them as required to suit your needs.

Periodic Jobs

If you would like to set up a periodic hierarchy for the root user, first issue the following commands (as the root user) to create the /usr/bin/run-parts script:

cat > /usr/bin/run-parts << "EOF" &&
#!/bin/sh
# run-parts:  Runs all the scripts found in a directory.
# from Slackware, by Patrick J. Volkerding with ideas borrowed
# from the Red Hat and Debian versions of this utility.

# keep going when something fails
set +e

if [ $# -lt 1 ]; then
  echo "Usage: run-parts <directory>"
  exit 1
fi

if [ ! -d $1 ]; then
  echo "Not a directory: $1"
  echo "Usage: run-parts <directory>"
  exit 1
fi

# There are several types of files that we would like to
# ignore automatically, as they are likely to be backups
# of other scripts:
IGNORE_SUFFIXES="~ ^ , .bak .new .rpmsave .rpmorig .rpmnew .swp"

# Main loop:
for SCRIPT in $1/* ; do
  # If this is not a regular file, skip it:
  if [ ! -f $SCRIPT ]; then
    continue
  fi
  # Determine if this file should be skipped by suffix:
  SKIP=false
  for SUFFIX in $IGNORE_SUFFIXES ; do
    if [ ! "$(basename $SCRIPT $SUFFIX)" = "$(basename $SCRIPT)" ]; then
      SKIP=true
      break
    fi
  done
  if [ "$SKIP" = "true" ]; then
    continue
  fi
  # If we've made it this far, then run the script if it's executable:
  if [ -x $SCRIPT ]; then
    $SCRIPT || echo "$SCRIPT failed."
  fi
done

exit 0
EOF
chmod -v 755 /usr/bin/run-parts

Next, create the directory layout for the periodic jobs (again as the root user):

install -vdm754 /etc/cron.{hourly,daily,weekly,monthly}

Finally, add the run-parts to the system fcrontab (while still the root user):

cat > /var/spool/fcron/systab.orig << "EOF"
&bootrun 01 * * * * root run-parts /etc/cron.hourly
&bootrun 02 4 * * * root run-parts /etc/cron.daily
&bootrun 22 4 * * 0 root run-parts /etc/cron.weekly
&bootrun 42 4 1 * * root run-parts /etc/cron.monthly
EOF

Boot Script

Install the /etc/rc.d/init.d/fcron init script from the blfs-bootscripts-20240209 package.

make install-fcron

Finally, again as the root user, start fcron and generate the /var/spool/fcron/systab file:

/etc/rc.d/init.d/fcron start &&
fcrontab -z -u systab

Installed Programs: fcron, fcrondyn, fcronsighup, and fcrontab

Installed Libraries: None

Installed Directories: /usr/share/doc/fcron-3.2.1 and /var/spool/fcron

Short Descriptions

fcron	is the scheduling daemon
fcrondyn	is a user tool intended to interact with a running fcron daemon
fcronsighup	instructs fcron to reread the Fcron tables
fcrontab	is a program used to install, edit, list and remove the tables used by fcron

GPM-1.20.7

Introduction to GPM

The GPM (General Purpose Mouse daemon) package contains a mouse server for the console and xterm. It not only provides cut and paste support generally, but its library component is used by various software such as Links to provide mouse support to the application. It is useful on desktops, especially if following (Beyond) Linux From Scratch instructions; it's often much easier (and less error prone) to cut and paste between two console windows than to type everything by hand!

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://anduin.linuxfromscratch.org/BLFS/gpm/gpm-1.20.7.tar.bz2
Download MD5 sum: bf84143905a6a903dbd4d4b911a2a2b8
Download size: 820 KB
Estimated disk space required: 7.4 MB
Estimated build time: 0.1 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/gpm-1.20.7-consolidated-1.patch

GPM Dependencies

Optional

texlive-20230313 (for documentation)

Kernel Configuration

Enable the following option in the kernel configuration and recompile the kernel if necessary:

Device Drivers --->
  Input device support --->
    -*-   Generic input layer (needed for keyboard, mouse, ...)          [INPUT]
    <*/M>   Mouse interface                                     [INPUT_MOUSEDEV]

Installation of GPM

Install GPM by running the following commands:

patch -Np1 -i ../gpm-1.20.7-consolidated-1.patch                &&
./autogen.sh                                                    &&
./configure --prefix=/usr --sysconfdir=/etc ac_cv_path_emacs=no &&
make

If texlive-20230313 is installed, build the GPM manual as dvi, ps, and pdf formats:

make -C doc gpm.{dvi,ps} &&
dvipdfm doc/gpm.dvi -o doc/gpm.pdf

This package does not come with a test suite.

Now, as the root user:

make install                                          &&

install-info --dir-file=/usr/share/info/dir           \
             /usr/share/info/gpm.info                 &&

rm -fv /usr/lib/libgpm.a                              &&
ln -sfv libgpm.so.2.1.0 /usr/lib/libgpm.so            &&
install -v -m644 conf/gpm-root.conf /etc              &&

install -v -m755 -d /usr/share/doc/gpm-1.20.7/support &&
install -v -m644    doc/support/*                     \
                    /usr/share/doc/gpm-1.20.7/support &&
install -v -m644    doc/{FAQ,HACK_GPM,README*}        \
                    /usr/share/doc/gpm-1.20.7

If texlive-20230313 is installed and you've built GPM manual as dvi, ps, and pdf formats, install them as the root user:

install -vm644 doc/gpm.{dvi,ps,pdf} /usr/share/doc/gpm-1.20.7

Command Explanations

./autogen.sh: This command creates the missing configure script.

ac_cv_path_emacs=no: This variable works around an issue causing the package fail to build with Emacs-29.2 installed. It also suppresses the installations of some “Emacs support files” shipped with GPM. These files are quite outdated and they should be superseded with Emacs-29.2 built-in GPM support. If you need to use Emacs-29.2 in Linux console with mouse support, you should install (or reinstall) Emacs-29.2 after GPM.

install-info ...: This package installs a .info file, but does not update the system dir file. This command makes the update.

ln -v -sfn libgpm.so.2.1.0 /usr/lib/libgpm.so: This command is used to create (or update) the .so symlink to the library.

Configuring GPM

Boot Script

Install the /etc/rc.d/init.d/gpm init script included in the blfs-bootscripts-20240209 package.

make install-gpm

Config Files

/etc/gpm-root.conf and ~/.gpm-root: The default and individual user gpm-root configuration files.

/etc/sysconfig/mouse: This file contains the name of your mouse device and the protocol it uses. To create this file, run the following as the root user:

cat > /etc/sysconfig/mouse << "EOF"
# Begin /etc/sysconfig/mouse

MDEVICE="<yourdevice>"
PROTOCOL="<yourprotocol>"
GPMOPTS="<additional options>"

# End /etc/sysconfig/mouse
EOF

Configuration Information

Examples of values to set MDEVICE, PROTOCOL, and GPMOPTS to are:

MDEVICE="/dev/input/mice"
PROTOCOL="imps2"
GPMOPTS=""

A list of which protocol values are known can be found by running gpm -m [device] -t -help. The MDEVICE setting depends on which type of mouse you have. For example, /dev/ttyS0 for a serial mouse (on Windows this is COM1), /dev/input/mice is often used for USB mice and /dev/psaux for PS2 mice. GPMOPTS is the 'catch all' for any additional options that are needed for your hardware.

Installed Programs: disable-paste, display-buttons, display-coords, get-versions, gpm, gpm-root, hltest, mev, and mouse-test

Installed Library: libgpm.so

Installed Directory: /usr/share/doc/gpm-1.20.7

Short Descriptions

disable-paste	is a security mechanism used to disable the paste buffer
display-buttons	is a simple program that reports the mouse buttons being pressed and released
display-coords	is a simple program that reports the mouse coordinates
get-versions	is used to report the GPM library and server versions
gpm	is a cut and paste utility and mouse server for virtual consoles
gpm-root	is a default handler for gpm. It is used to draw menus on the root window
hltest	is a simple sample application using the high-level library, meant to be read by programmers trying to use the high-level library
mev	is a program to report mouse events
mouse-test	is a tool for determining the mouse type and device it's attached to
`libgpm.so`	contains the API functions to access the GPM daemon

Hdparm-9.65

Introduction to Hdparm

The Hdparm package contains a utility that is useful for obtaining information about, and controlling ATA/IDE controllers and hard drives. It allows to increase performance and sometimes to increase stability.

This package is known to build and work properly using an LFS 12.1 platform.

Warning

As well as being useful, incorrect usage of Hdparm can destroy your information and in rare cases, drives. Use with caution and make sure you know what you are doing. If in doubt, it is recommended that you leave the default kernel parameters alone.

Package Information

Download (HTTP): https://downloads.sourceforge.net/hdparm/hdparm-9.65.tar.gz
Download MD5 sum: 6d6d039d61ec995b1ec72ddce0b1853b
Download size: 140 KB
Estimated disk space required: 1.0 MB
Estimated build time: less than 0.1 SBU

Installation of Hdparm

Build Hdparm by running the following command:

make

This package does not come with a test suite.

Now, as the root user:

make binprefix=/usr install

Installed Program: hdparm

Installed Libraries: None

Installed Directories: None

Short Descriptions

hdparm

provides a command-line interface to various hard disk ioctls supported by the stock Linux ATA/IDE device driver subsystem

LSB-Tools-0.12

Introduction to LSB-Tools

The LSB-Tools package includes tools for Linux Standards Base (LSB) conformance.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/lfs-book/LSB-Tools/releases/download/v0.12/LSB-Tools-0.12.tar.gz
Download MD5 sum: 1e6ef8cdfddb55035a6c36757e6313f9
Download size: 20 KB
Estimated disk space required: 412 KB
Estimated build time: less than 0.1 SBU

Installation of LSB-Tools

Install LSB-Tools by running the following commands:

make

Now, as the root user:

make install

Remove a file that should not be installed as the root user:

rm /usr/sbin/lsbinstall

Configuration Information

The configuration for this package was done in LFS. The file /etc/lsb-release should already exist. Be sure that the DISTRIB_CODENAME entry has been set properly.

Installed Programs: lsb_release , install_initd, and remove_initd

Installed Library: None

Installed Directories: /usr/lib/python3.12/site-packages/lsbtools

Short Descriptions

lsb_release	is a script to give LSB data
install_initd	is a script to activate SysV startup scripts
remove_initd	is a script to deactivate SysV startup scripts

Lm-sensors-3-6-0

Introduction to Lm_sensors

The lm_sensors package provides userspace support for the hardware monitoring drivers in the Linux kernel. This is useful for monitoring the temperature of the CPU and adjusting the performance of some hardware (such as cooling fans).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/lm-sensors/lm-sensors/archive/V3-6-0/lm-sensors-3-6-0.tar.gz
Download MD5 sum: f60e47b5eb50bbeed48a9f43bb08dd5e
Download size: 268 KB
Estimated disk space required: 2.6 MB
Estimated build time: less than 0.1 SBU

lm_sensors Dependencies

Required

Which-2.21

Optional

RRDtool (required to build the sensord program) and dmidecode (runtime)

Kernel Configuration

The following configuration options attempt to cover the most common hardware monitoring devices in a typical desktop or laptop system. View the help of each (by pressing the H button with the option focused in the make menuconfig) to know if you need it. There are many platform-specific hardware monitoring devices so it's impossible to list the configuration for all of them here. You may investigate the content of /sys/class/hwmon within a “mainstream” distro running on the system to know which drivers you need.

Power management and ACPI options --->
  [*] ACPI (Advanced Configuration and Power Interface) Support --->      [ACPI]
    < /*/M> Battery                                               [ACPI_BATTERY]
    < /*/M> Thermal Zone                                          [ACPI_THERMAL]

Device Drivers --->
  NVME Support --->
    < /*> NVM Express block device                                [BLK_DEV_NVME]
    # Set [HWMON] to <*> (not <M>!) or it will not show up:
    [ /*] NVMe hardware monitoring                                  [NVME_HWMON]
  <*/M> Hardware Monitoring support --->                                 [HWMON]
    < /*/M> AMD Athlon64/FX or Opteron temperature sensor       [SENSORS_K8TEMP]
    < /*/M> AMD Family 10h+ temperature sensor                 [SENSORS_K10TEMP]
    < /*/M> AMD Family 15h processor power                [SENSORS_FAM15H_POWER]
    < /*/M> Intel Core/Core2/Atom temperature sensor          [SENSORS_CORETEMP]

Recompile your kernel and reboot into the new kernel.

Installation of Lm_sensors

Install Lm_sensors by running the following commands:

make PREFIX=/usr        \
     BUILD_STATIC_LIB=0 \
     MANDIR=/usr/share/man

This package does not come with a test suite.

Now, as the root user:

make PREFIX=/usr        \
     BUILD_STATIC_LIB=0 \
     MANDIR=/usr/share/man install &&

install -v -m755 -d /usr/share/doc/lm_sensors-3-6-0 &&
cp -rv              README INSTALL doc/* \
                    /usr/share/doc/lm_sensors-3-6-0

Command Explanations

BUILD_STATIC_LIB=0: This parameter disables compiling and installing the static version of libsensors.

PROG_EXTRA=sensord: This parameter enables compiling sensord, a daemon that can monitor your system at regular intervals. Compiling sensord requires RRDtool. Be sure to install RRDtool in /usr by running make prefix=/usr when building it. Otherwise, Lm_sensors will not find it easily.

Configuring Lm_sensors

Config File

/etc/sensors3.conf

Installed Programs: fancontrol, isadump, isaset, pwmconfig, sensors, sensors-conf-convert, sensors-detect, and optionally, sensord

Installed Library: libsensors.so

Installed Directories: /etc/sensors.d, /usr/include/sensors and /usr/share/doc/lm_sensors-3-6-0

Short Descriptions

fancontrol	is a shell script for use with lm_sensors. It reads its configuration from a file, then calculates fan speeds from temperatures and sets the corresponding PWM outputs to the computed values
isadump	is a small helper program to examine registers visible through the ISA bus. It is intended to probe any chip that lives on the ISA bus working with an address register and a data register (I2C-like access) or a flat range (of up to 256 bytes)
isaset	is a small helper program to set registers visible through the ISA bus
pwmconfig	tests the pulse width modulation (PWM) outputs of sensors and configures fancontrol
sensors	prints the current readings of all sensor chips
sensors-conf-convert	is a Perl script to convert lm-sensors version 2 configuration files to work with version 3
sensors-detect	is a Perl script that will walk you through the process of scanning your system for various hardware monitoring chips (sensors) supported by `libsensors`, or more generally by the lm_sensors tool suite
sensord	(optional) is a daemon that can be used to periodically log sensor readings
`libsensors.so`	contains the lm_sensors API functions

Logrotate-3.21.0

Introduction to Logrotate

The logrotate package allows automatic rotation, compression, removal, and mailing of log files.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/logrotate/logrotate/releases/download/3.21.0/logrotate-3.21.0.tar.xz
Download MD5 sum: 6c15f45efc3475a576c4f7e6cc481b2c
Download size: 164.5 KB
Estimated disk space required: 2.9 MB (add 38 MB for tests)
Estimated build time: less than 0.1 SBU (add 0.2 SBU for tests)

Logrotate Dependencies

Required

popt-1.19

Optional

An MTA (runtime)

Installation of Logrotate

Install logrotate by running the following command:

./configure --prefix=/usr &&
make

To test the results, issue: make test. One test fails because the very old compress is not present and two tests fail if an MTA is not installed.

Now, as the root user:

make install

Configuring Logrotate

Logrotate needs a configuration file, which must be passed as an argument to the command when executed. Create the file as the root user:

cat > /etc/logrotate.conf << EOF
# Begin /etc/logrotate.conf

# Rotate log files weekly
weekly

# Don't mail logs to anybody
nomail

# If the log file is empty, it will not be rotated
notifempty

# Number of backups that will be kept
# This will keep the 2 newest backups only
rotate 2

# Create new empty files after rotating old ones
# This will create empty log files, with owner
# set to root, group set to sys, and permissions 664
create 0664 root sys

# Compress the backups with gzip
compress

# No packages own lastlog or wtmp -- rotate them here
/var/log/wtmp {
    monthly
    create 0664 root utmp
    rotate 1
}

/var/log/lastlog {
    monthly
    rotate 1
}

# Some packages drop log rotation info in this directory
# so we include any file in it.
include /etc/logrotate.d

# End /etc/logrotate.conf
EOF

chmod -v 0644 /etc/logrotate.conf

Now create the /etc/logrotate.d directory as the root user:

mkdir -p /etc/logrotate.d

At this point additional log rotation commands can be entered, typically in the /etc/logrotate.d directory. For example:

cat > /etc/logrotate.d/sys.log << EOF
/var/log/sys.log {
   # If the log file is larger than 100kb, rotate it
   size   100k
   rotate 5
   weekly
   postrotate
      /bin/killall -HUP syslogd
   endscript
}
EOF

chmod -v 0644 /etc/logrotate.d/sys.log

You can designate multiple files in one entry:

cat > /etc/logrotate.d/example.log << EOF
file1
file2
file3 {
   ...
   postrotate
    ...
   endscript
}
EOF

chmod -v 0644 /etc/logrotate.d/example.log

You can use in the same line the list of files: file1 file2 file3. See the logrotate man page or https://www.techrepublic.com/article/manage-linux-log-files-with-logrotate/ for more examples.

The command logrotate /etc/logrotate.conf can be run manually, however, the command should be run daily. Other useful commands are logrotate -d /etc/logrotate.conf for debugging purposes and logrotate -f /etc/logrotate.conf forcing the logrotate commands to be run immediately. Combining the previous options -df, you can debug the effect of the force command. When debugging, the commands are only simulated and are not actually run. As a result, errors about files not existing will eventually appear because the files are not actually created.

To run the logrotate command daily, if you've installed Fcron-3.2.1 and completed the section on periodic jobs, execute the following commands, as the root user, to create a daily cron job:

cat > /etc/cron.daily/logrotate.sh << "EOF" &&
#!/bin/bash
/usr/sbin/logrotate /etc/logrotate.conf
EOF
chmod 754 /etc/cron.daily/logrotate.sh

Installed Programs: logrotate

Installed Library: None

Installed Directories: None

Short Descriptions

logrotate

performs the log maintenance functions defined in the configuration files

MC-4.8.31

Introduction to MC

MC (Midnight Commander) is a text-mode full-screen file manager and visual shell. It provides a clear, user-friendly, and somewhat protected interface to a Unix system while making many frequent file operations more efficient and preserving the full power of the command prompt.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://ftp.midnight-commander.org/mc-4.8.31.tar.xz
Download MD5 sum: 2c3dd9af66e4cfef5a7a460df1cdf868
Download size: 2.3 MB
Estimated disk space required: 71 MB (add 96 MB for tests)
Estimated build time: 0.3 SBU (using parallelism=4; add 0.2 SBU for tests)

MC Dependencies

Required

Optional

Doxygen-1.10.0, GPM-1.20.7, Graphviz-10.0.1, libssh2-1.11.0, PCRE-8.45, pcre2-10.42, Ruby-3.3.0, UnZip-6.0, a graphical environment, and Zip-3.0

Installation of MC

Install MC by running the following commands:

./configure --prefix=/usr \
            --sysconfdir=/etc \
            --enable-charset &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--sysconfdir=/etc: This switch places the global configuration directory in /etc.

--enable-charset: This switch adds support to mcedit for editing files in encodings different from the one implied by the current locale.

--with-search-engine=pcre2: Use this switch if you would prefer to use pcre2-10.42 instead of GLib for the built-in search engine. Alternatively, you can pass 'pcre' instead of 'pcre2' if you prefer to use PCRE-8.45.

Configuring MC

Config Files

~/.config/mc/*

Configuration Information

The ~/.config/mc directory and its contents are created when you start mc for the first time. Then you can edit the main ~/.config/mc/ini configuration file manually or through the MC shell. Consult the mc(1) man page for details.

Installed Programs: mc and the symlinks mcdiff, mcedit and mcview

Installed Libraries: None

Installed Directories: /etc/mc and /usr/{libexec,share}/mc

Short Descriptions

mc	is a visual shell
mcdiff	is an internal visual diff tool
mcedit	is an internal file editor
mcview	is an internal file viewer

ModemManager-1.18.12

Introduction to ModemManager

ModemManager provides a unified high level API for communicating with mobile broadband modems, regardless of the protocol used to communicate with the actual device.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.freedesktop.org/software/ModemManager/ModemManager-1.18.12.tar.xz
Download MD5 sum: 9f014dfc59f1bd8bc230bb2c2974d104
Download size: 2.5 MB
Estimated disk space required: 155 MB (with tests)
Estimated build time: 0.7 SBU (Using parallelism=4; with tests)

ModemManager Dependencies

Required

libgudev-238

Optional

Editor Notes: https://wiki.linuxfromscratch.org/blfs/wiki/ModemManager

Installation of ModemManager

Install ModemManager by running the following commands:

./configure --prefix=/usr                 \
            --sysconfdir=/etc             \
            --localstatedir=/var          \
            --disable-static              \
            --disable-maintainer-mode     \
            --with-systemd-journal=no     \
            --with-systemd-suspend-resume &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--with-systemd-suspend-resume: This switch forces ModemManager to use the elogind power management facilities.

--with-systemd-journal=no : This switch forces ModemManager not to use the systemd journal for logging.

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

Installed Programs: mmcli and ModemManager

Installed Libraries: libmm-glib.so

Installed Directories: /etc/ModemManager, /usr/include/libmm-glib, /usr/include/ModemManager, /usr/lib/ModemManager, /usr/share/ModemManager, /usr/share/gtk-doc/html/libmm-glib (optional), and /usr/share/gtk-doc/html/ModemManager (optional)

Short Descriptions

mmcli	is an utility used to control and monitor the ModemManager
ModemManager	is a D-Bus service used to communicate with modems
`libmm-glib.so`	contains API functions for communicating with mobile broadband modems, regardless of the protocol used to communicate with the actual device

notification-daemon-3.20.0

Introduction to Notification Daemon

The Notification Daemon package contains a daemon that displays passive pop-up notifications.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.gnome.org/sources/notification-daemon/3.20/notification-daemon-3.20.0.tar.xz
Download MD5 sum: 2de7f4075352831f1d98d8851b642124
Download size: 336 KB
Estimated disk space required: 4.1 MB
Estimated build time: less than 0.1 SBU

Notification Daemon Dependencies

Required

GTK+-3.24.41 and libcanberra-0.30 (Built with GTK+-3.24.41 support).

Installation of Notification Daemon

Install Notification Daemon by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --disable-static  &&
make

This package does not come with a test suite.

Now, as the root user:

make install

You can test the notification daemon with the command notify-send:

pgrep -l notification-da &&
notify-send -i info Information "Hi ${USER}, This is a Test"

The command pgrep -l notification-da is added to assure that it is the daemon of this package that is running, not another one, e.g. the daemon from xfce4-notifyd-0.9.4.

Installed Program: none

Installed Libraries: none

Installed Directory: none

p7zip-17.04

Introduction to p7zip

p7zip is the Unix command-line port of 7-Zip, a file archiver that archives with high compression ratios. It handles 7z, ZIP, GZIP, Brotli, BZIP2, XZ, TAR, APM, ARJ, CAB, CHM, CPIO, CramFS, DEB, DMG, FAT, HFS, ISO, Lizard, LZ5, LZFSE, LZH, LZMA, LZMA2, MBR, MSI, MSLZ, NSIS, NTFS, RAR, RPM, SquashFS, UDF, VHD, WIM, XAR, Z, and Zstd formats.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/p7zip-project/p7zip/archive/v17.04/p7zip-17.04.tar.gz
Download MD5 sum: 00acfd6be87848231722d2d53f89e4a5
Download size: 6.5 MB
Estimated disk space required: 55 MB
Estimated build time: 2.3 SBU (with tests)

p7zip Dependencies

Optional

wxWidgets

Installation of p7zip

First, prevent p7zip from installing compressed manual pages:

sed '/^gzip/d' -i install.sh

Next, fix a security vulnerability:

sed -i '160a if(_buffer == nullptr || _size == _pos) return E_FAIL;' CPP/7zip/Common/StreamObjects.cpp

Install p7zip by running the following commands:

make all3

To test the results, issue: make test.

Now, as the root user:

make DEST_HOME=/usr \
     DEST_MAN=/usr/share/man \
     DEST_SHARE_DOC=/usr/share/doc/p7zip-17.04 install

Note

If using DESTDIR techniques, use DEST_DIR instead.

Installed Programs: 7z, 7za, and 7zr

Installed Libraries: None

Installed Directory: /usr/lib/p7zip and /usr/share/doc/p7zip-17.04

Short Descriptions

7z	is a file archiver utility
7za	is a stand-alone executable handling less archive formats than 7z
7zr	is a minimal version of 7za that handles only 7z archives

Pax-20201030

Introduction to Pax

pax is an archiving utility created by POSIX and defined by the POSIX.1-2001 standard. Rather than sort out the incompatible options that have crept up between tar and cpio, along with their implementations across various versions of UNIX, the IEEE designed a new archive utility. The name “pax” is an acronym for portable archive exchange. Furthermore, “pax” means “peace” in Latin, so its name implies that it shall create peace between the tar and cpio format supporters. The command invocation and command structure is somewhat a unification of both tar and cpio.

pax has been required to be present in LSB conformant systems since LSB version 3.0.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): http://www.mirbsd.org/MirOS/dist/mir/cpio/paxmirabilis-20201030.tgz
Download MD5 sum: 87a0a3870ec437c41eb1b406334fe2c5
Download size: 172 KB
Estimated disk space required: 1.2 MB
Estimated build time: less than 0.1 SBU

Installation of Pax

Install pax by running the following commands:.

Note

This package expands to the directory pax.

bash Build.sh

This package does not come with a test suite.

Now, as the root user:

Note

This package also creates hard links from pax to the programs cpio and tar in the build directory. The LFS editors do not recommend that they be installed as they will overwrite the GNU versions of these programs.

install -v pax /usr/bin &&
install -v -m644 pax.1 /usr/share/man/man1

Installed Program: pax

Short Descriptions

pax

copies files to and from archives in several formats

pciutils-3.10.0

Introduction to PCI Utils

The PCI Utils package contains a set of programs for listing PCI devices, inspecting their status and setting their configuration registers.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://mj.ucw.cz/download/linux/pci/pciutils-3.10.0.tar.gz
Download MD5 sum: ca53b87d2a94cdbbba6e09aca90924bd
Download size: 912 KB
Estimated disk space required: 5.7 MB
Estimated build time: less than 0.1 SBU

pciutils Dependencies

Installation of PCI Utils

Install PCI Utils by running the following commands:

make PREFIX=/usr                \
     SHAREDIR=/usr/share/hwdata \
     SHARED=yes

This package does not come with a test suite.

Now, as the root user:

make PREFIX=/usr                \
     SHAREDIR=/usr/share/hwdata \
     SHARED=yes                 \
     install install-lib        &&

chmod -v 755 /usr/lib/libpci.so

Command Explanations

SHARED=yes: This parameter enables building of the shared library instead of the static one.

ZLIB=no: This option prevents compression of the pci.ids file.

Configuring PCI Utils

The pci.ids data file is constantly being updated. To get a current version of this file, run update-pciids as the root user. This program requires the Which-2.21 script or program to find cURL-8.6.0, Lynx-2.8.9rel.1, or Wget-1.21.4 which are used to download the most current file, and then replace the existing file in /usr/share/hwdata.

You should update the /usr/share/hwdata/pci.ids file periodically. If you've installed Fcron-3.2.1 and completed the section on periodic jobs, execute the following commands, as the root user, to create a weekly cron job:

cat > /etc/cron.weekly/update-pciids.sh << "EOF" &&
#!/bin/bash
/usr/sbin/update-pciids
EOF
chmod 754 /etc/cron.weekly/update-pciids.sh

Installed Programs: lspci, setpci, and update-pciids

Installed Library: libpci.so

Installed Directory: /usr/include/pci and /usr/share/hwdata

Short Descriptions

lspci	is a utility for displaying information about all PCI buses in the system and all devices connected to them
setpci	is a utility for querying and configuring PCI devices
update-pciids	fetches the current version of the PCI ID list.
`libpci.so`	is a library that allows applications to access the PCI subsystem

pm-utils-1.4.1

Introduction to Power Management Utilities

The Power Management Utilities provide simple shell command line tools to suspend and hibernate the computer. They can be used to run user supplied scripts on suspend and resume.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://pm-utils.freedesktop.org/releases/pm-utils-1.4.1.tar.gz
Download MD5 sum: 1742a556089c36c3a89eb1b957da5a60
Download size: 204 KB
Estimated disk space required: 1.6 MB
Estimated build time: 0.1 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/pm-utils-1.4.1-bugfixes-1.patch

Power Management Utilities Dependencies

Optional

xmlto-0.0.28 (to generate man pages)

Optional (runtime)

Hdparm-9.65, Wireless Tools-29, ethtool, and vbetool

Kernel Configuration

If needed, enable the following options in the kernel configuration and recompile the kernel:

Power management and ACPI options --->
  [*] Suspend to RAM and standby                                       [SUSPEND]
  [*] Hibernation (aka 'suspend to disk')                          [HIBERNATION]

Suspend to RAM allows the system to enter sleep states in which main memory is powered and thus its contents are preserved. The method cuts power to most parts of the machine aside from the RAM. Because of the large power savings, it is advisable for laptops to automatically enter this mode when the computer is running on batteries and the lid is closed (or the user is inactive for some time).

Suspend to disk (Hibernation) saves the machine's state into swap space and completely powers off the machine. When the machine is powered on, the state is restored. Until then, there is zero power consumption. Suspend to RAM and hibernation are normally appropriate for portable devices such as laptops, but can be used on workstations. The capability is not really appropriate for servers.

To use hibernation, the kernel parameter resume=/dev/<swap_partition> has to be used on the kernel command line (in grub.cfg). The swap partition should be at least the size of the physical RAM on the system.

Installation of Power Management Utilities

First, fix several bugs and a couple of incompatibilities with newer kernels:

patch -Np1 -i ../pm-utils-1.4.1-bugfixes-1.patch

Install Power Management Utilities by running the following commands:

./configure --prefix=/usr     \
            --sysconfdir=/etc \
            --docdir=/usr/share/doc/pm-utils-1.4.1 &&
make

This package does not come with a test suite.

Now, as the root user:

make install

If you don't have xmlto-0.0.28 installed, copy pregenerated man pages, as the root user:

install -v -m644 man/*.1 /usr/share/man/man1 &&
install -v -m644 man/*.8 /usr/share/man/man8 &&
ln -sv pm-action.8 /usr/share/man/man8/pm-suspend.8 &&
ln -sv pm-action.8 /usr/share/man/man8/pm-hibernate.8 &&
ln -sv pm-action.8 /usr/share/man/man8/pm-suspend-hybrid.8

Configuring Power Management Utilities

Suspend or resume functionality can be easily modified by installing files into the /etc/pm/sleep.d directory. These files, known as hooks, are run when the system is put into a sleep state or resumed. Default hooks are located in /usr/lib/pm-utils/sleep.d, and user hooks should be put in /etc/pm/sleep.d. See the pm-action(8) man page for more information.

In order to use hibernation with GRUB and a swap partition, you need to add kernel parameter resume=swap_partition (e.g. resume=/dev/sda1) to the kernel line in the /boot/grub/grub.cfg configuration file.

Installed Programs: on_ac_power, pm-hibernate, pm-is-supported, pm-powersave, pm-suspend and pm-suspend-hybrid

Installed Libraries: None

Installed Directories: /etc/pm, /usr/lib/pm-utils and /usr/share/doc/pm-utils-1.4.1

Short Descriptions

on_ac_power	is a script that determines whether the system is running on AC power (rather than a battery)
pm-hibernate	is a symlink to pm-action script that puts the computer into hibernate mode (the system is fully powered off and system state is saved to disk)
pm-is-supported	is a script that checks whether power management features such as suspend and hibernate are supported
pm-powersave	is a script that puts the computer into powersaving (low power) mode
pm-suspend	is a symlink to pm-action script that puts the computer into suspend mode (most devices are shut down and system state is saved in RAM)
pm-suspend-hybrid	is a symlink to pm-action script that puts the computer into hybrid-suspend mode (the system does everything it needs to hibernate, but suspends instead of shutting down)

Power-profiles-daemon-0.20

Introduction to Power-profiles-daemon

The Power-profiles-daemon package provides a program that allows modification of the system power/behavior state. This is used on many laptops and can be used by a Desktop Environment to activate power saving or performance CPU governors through dbus.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/archive/0.20/power-profiles-daemon-0.20.tar.gz
Download MD5 sum: 92df21de1148ef6e7c30e4a0829e02b1
Download size: 68 KB
Estimated disk space required: 1.4 MB
Estimated build time: less than 0.1 SBU (with tests)

Power-profiles-daemon Dependencies

Required

gobject-introspection-1.78.1, libgudev-238, Polkit-124, and PyGObject-3.46.0

Optional

GTK-Doc-1.33.2, The rest are for the tests, dbusmock-0.30.2, umockdev-0.17.18, isort, and mccabe

Kernel Configuration

Enable the following options in the kernel configuration and recompile the kernel if necessary:

Power management and ACPI options --->
  CPU Frequency scaling --->
    -*-   CPU Frequency scaling                                       [CPU_FREQ]
    -*-     'performance' governor                    [CPU_FREQ_GOV_PERFORMANCE]
    <*/M>   'powersave' governor                        [CPU_FREQ_GOV_POWERSAVE]
    # Select if CPU is Intel:
    [ /*]   Intel P state control                             [X86_INTEL_PSTATE]
    # Select if CPU is AMD:
    [ /*]   AMD Processor P-State driver                        [X86_AMD_PSTATE]

Device Drivers --->
  # Some drivers under this submenu provide "platform profile" support
  # and power-profiles-daemon can take advantage from platform profiles;
  # select a driver if suitable for your platform:
  [ /*] X86 Platform Specific Device Drivers --->         [X86_PLATFORM_DEVICES]

Select the appropriate sub-options that appear when the above options are selected. As much as possible, the layout should be the same as in kernel configuration menus.

Installation of Power-profiles-daemon

Install Power-profiles-daemon by running the following commands:

mkdir build &&
cd build &&

meson setup                       \
      --prefix=/usr               \
      --buildtype=release         \
      -Dgtk_doc=false             \
      -Dtests=false               \
      -Dsystemdsystemunitdir=/tmp \
      .. &&
ninja

If you have installed the external dependencies, to test the results issue: ninja test.

Now, as the root user:

ninja install

Now, clean up an unneeded systemd unit installed into /tmp:

rm -fv /tmp/power-profiles-daemon.service

Command Explanations

-Dgtk_doc=false: Prevents building the documentation. Remove this if you have GTK-Doc installed and wish to build the documentation.

-Dtests=false: Prevents building the tests because they cannot be run within the boundaries of BLFS. Remove this if you have installed the external dependencies and wish to run the tests.

-Dsystemdsystemunitdir=/tmp: Removes the dependency on systemd.

Configuring Power-profiles-daemon

Boot Script

To automatically start the power-profiles-daemon when the system is rebooted, install the /etc/rc.d/init.d/power-profiles-daemon bootscript from the blfs-bootscripts-20240209 as the root user:

make install-power-profiles-daemon

Installed Program: powerprofilesctl

Installed Libraries: None

Installed Directories: None

Short Descriptions

powerprofilesctl

This allows the user to set the power governor of the CPU.

Raptor-2.0.16

Introduction to Raptor

Raptor is a C library that provides a set of parsers and serializers that generate Resource Description Framework (RDF) triples.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.librdf.org/source/raptor2-2.0.16.tar.gz
Download MD5 sum: 0a71f13b6eaa0a04bf411083d89d7bc2
Download size: 1.7 MB
Estimated disk space required: 25 MB (additional 2 MB for the tests)
Estimated build time: 0.1 SBU (additional 0.3 SBU for the tests)

Raptor Dependencies

Required

cURL-8.6.0 and libxslt-1.1.39

Optional

GTK-Doc-1.33.2, ICU-74.2 and libyajl

Installation of Raptor

First, fix an incompatibility with libxml2-2.11.x:

sed -i 's/20627/20627 \&\& LIBXML_VERSION < 21100/' src/raptor_libxml.c

Install Raptor by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check. Several of the XML tests may fail.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--with-icu-config=/usr/bin/icu-config: Use this switch if you have installed ICU-74.2 and wish to build Raptor with its support.

Installed Programs: rapper

Installed Libraries: libraptor2.so

Installed Directories: /usr/include/raptor2 and /usr/share/gtk-doc/html/raptor2

Short Descriptions

rapper	is a RDF parsing and serializing utility
`libraptor2.so`	contains the Raptor API functions

Rasqal-0.9.33

Introduction to Rasqal

Rasqal is a C library that handles Resource Description Framework (RDF) query language syntaxes, query construction, and execution of queries returning results as bindings, boolean, RDF graphs/triples or syntaxes.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.librdf.org/source/rasqal-0.9.33.tar.gz
Download MD5 sum: 1f5def51ca0026cd192958ef07228b52
Download size: 1.6 MB
Estimated disk space required: 22 MB (additional 4 MB for the tests)
Estimated build time: 0.3 SBU (additional 0.7 SBU for the tests)

Rasqal Dependencies

Required

Raptor-2.0.16

Optional

PCRE-8.45 and libgcrypt-1.10.3

Installation of Rasqal

Install Rasqal by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: rasqal-config and roqet

Installed Library: librasqal.so

Installed Directories: /usr/include/rasqal and /usr/share/gtk-doc/html/rasqal

Short Descriptions

rasqal-config	is an utility for retrieving the installation options of Rasqal
roqet	is an RDF query utility

Redland-1.0.17

Introduction to Redland

Redland is a set of free software C libraries that provide support for the Resource Description Framework (RDF).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://download.librdf.org/source/redland-1.0.17.tar.gz
Download MD5 sum: e5be03eda13ef68aabab6e42aa67715e
Download size: 1.6 MB
Estimated disk space required: 18 MB
Estimated build time: 0.2 SBU

Redland Dependencies

Required

Rasqal-0.9.33

Optional

libiodbc-3.52.15, SQLite-3.45.1, MariaDB-10.11.7 or MySQL, PostgreSQL-16.2, Berkeley DB (deprecated) virtuoso, and 3store

Installation of Redland

Install Redland by running the following commands:

./configure --prefix=/usr --disable-static &&
make

To test the results, issue make check.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: rdfproc, redland-config and redland-db-upgrade

Installed Libraries: librdf.so and /usr/lib/redland/librdf_storage_*.so

Installed Directories: /usr/lib/redland, /usr/share/gtk-doc/html/redland and /usr/share/redland

Short Descriptions

rdfproc	is the Redland RDF processor utility
redland-config	is a script to get information about the installed version of Redland
redland-db-upgrade	upgrades older Redland databases to 0.9.12 format

sg3_utils-1.48

Introduction to sg3_utils

The sg3_utils package contains low level utilities for devices that use a SCSI command set. Apart from SCSI parallel interface (SPI) devices, the SCSI command set is used by ATAPI devices (CD/DVDs and tapes), USB mass storage devices, Fibre Channel disks, IEEE 1394 storage devices (that use the "SBP" protocol), SAS, iSCSI and FCoE devices (amongst others).

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://sg.danny.cz/sg/p/sg3_utils-1.48.tar.xz
Download MD5 sum: 0024393d2d2942cc081ce613d98db68a
Download size: 1.2 MB
Estimated disk space required: 27 MB
Estimated build time: 0.2 SBU

Installation of sg3_utils

Install sg3_utils by running the following commands:

./configure --prefix=/usr --disable-static &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: rescan-scsi-bus.sh, scsi_logging_level, scsi_mandat, scsi_readcap, scsi_ready, scsi_satl, scsi_start, scsi_stop, scsi_temperature, sg_bg_ctl, sg_compare_and_write, sg_copy_results, sg_dd, sg_decode_sense, sg_emc_trespass, sg_format, sg_get_config, sg_get_lba_status, sg_ident, sg_inq, sg_logs, sg_luns, sg_map, sg_map26, sg_modes, sg_opcodes, sg_persist, sg_prevent, sg_raw, sg_rbuf, sg_rdac, sg_read, sg_read_attr, sg_read_block_limits, sg_read_buffer, sg_read_long, sg_readcap, sg_reassign, sg_referrals, sg_rep_pip, sg_rep_zones, sg_requests, sg_reset, sg_reset_wp, sg_rmsn, sg_rtpg, sg_safte, sg_sanitize, sg_sat_identify, sg_sat_phy_event, sg_sat_read_gplog, sg_sat_set_features, sg_scan, sg_seek, sg_senddiag, sg_ses, sg_ses_microcode, sg_start, sg_stpg, sg_stream_ctl, sg_sync, sg_test_rwbuf, sg_timestamp, sg_turs, sg_unmap, sg_verify, sg_vpd, sg_wr_mode, sg_write_buffer, sg_write_long, sg_write_same, sg_write_verify, sg_write_x, sg_xcopy, sg_zone, sginfo, sgm_dd, and sgp_dd

Installed Library: libsgutils2.so

Installed Directories: None

Short Descriptions

rescan-scsi-bus.sh	adds or removes SCSI devices without having to reboot
scsi_logging_level	accesses Linux SCSI logging level information
scsi_mandat	checks SCSI device support for mandatory commands
scsi_readcap	does the SCSI READ CAPACITY command on disks
scsi_ready	does the SCSI TEST UNIT READY on devices
scsi_satl	checks for SCSI to ATA Translation (SAT) device support
scsi_start	starts one or more SCSI disks
scsi_stop	stops one or more SCSI disks
scsi_temperature	fetches the temperature of a SCSI device
sg_bg_ctl	performs a SCSI BACKGROUND CONTROL command on a device to perform "advanced background operations"
sg_compare_and_write	sends the SCSI COMPARE AND WRITE command to device
sg_copy_results	sends the SCSI RECEIVE COPY RESULTS command (XCOPY related)
sg_dd	copies data to and from files and devices. Specialised for devices that understand the SCSI command set
sg_decode_sense	takes SCSI sense data in binary or as a sequence of ASCII hexadecimal bytes and decodes it
sg_emc_trespass	changes ownership of a LUN from another Service-Processor to this one
sg_format	formats or resizes a SCSI disk (perhaps changes its block size)
sg_get_config	sends a SCSI GET CONFIGURATION command (MMC-4 +)
sg_get_elem_status	sends a SCSI GET PHYSICAL ELEMENT STATUS command to a device
sg_get_lba_status	sends the SCSI GET LBA STATUS command
sg_ident	sends a SCSI REPORT or SET IDENTIFYING INFORMATION command
sginfo	access mode page information for a SCSI (or ATAPI) device
sg_inq	sends a SCSI INQUIRY or ATA IDENTIFY (PACKET) DEVICE command and outputs the response
sg_logs	access log pages with SCSI LOG SENSE command
sg_luns	sends the SCSI REPORT LUNS command
sg_map	displays mapping between linux sg and other SCSI devices
sg_map26	maps a special file to a SCSI generic (sg) device (or vice versa)
sgm_dd	copies data to and from files and devices. Specialized for devices that understand the SCSI command set and does memory mapped transfers from sg devices
sg_modes	reads mode pages with the SCSI MODE SENSE command
sg_opcodes	reports information on supported SCSI commands or task management functions
sgp_dd	copies data to and from files and devices. Specialized for devices that understand the SCSI command set
sg_persist	sends a SCSI PERSISTENT RESERVE (IN or OUT) command to manipulate registrations and reservations
sg_prevent	sends a SCSI PREVENT ALLOW MEDIUM REMOVAL command
sg_raw	sends an arbitrary SCSI command to a device
sg_rbuf	reads data using the SCSI READ BUFFER command
sg_rdac	displays or modifies the RDAC Redundant Controller Page
sg_read	reads blocks of data continually from the same offset
sg_read_attr	performs a SCSI READ ATTRIBUTE command on a device
sg_read_block_limits	sends a SCSI READ BLOCK LIMITS command
sg_read_buffer	sends a SCSI READ BUFFER command
sg_readcap	sends a SCSI READ CAPACITY command
sg_read_long	sends a SCSI READ LONG command
sg_reassign	sends a SCSI REASSIGN BLOCKS command
sg_referrals	sends a SCSI REPORT REFERRALS command
sg_rep_pip	sends a SCSI REPORT PROVISIONING INITIALIZATION PATTERN command
sg_rep_zones	sends a SCSI REPORT ZONES command
sg_requests	sends one or more SCSI REQUEST SENSE commands
sg_reset	sends a SCSI device, target, bus or host reset; or checks reset state
sg_reset_wp	sends a SCSI RESET WRITE POINTER command
sg_rmsn	sends a SCSI READ MEDIA SERIAL NUMBER command
sg_rtpg	sends a SCSI REPORT TARGET PORT GROUPS command
sg_safte	fetches status information from a SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) device
sg_sanitize	sends a SCSI SANITIZE command
sg_sat_identify	sends an ATA IDENTIFY (PACKET) DEVICE command via a SCSI to ATA Translation (SAT) layer
sg_sat_phy_event	sends an ATA READ LOG EXT command via a SAT pass through to fetch log page 11h which contains SATA phy event counters
sg_sat_read_gplog	sends an ATA READ LOG EXT command via a SCSI to ATA Translation (SAT) layer
sg_sat_set_features	sends an ATA SET FEATURES command via a SCSI to ATA Translation (SAT) layer
sg_scan	does a scan of sg devices (or given SCSI/ATAPI/ATA devices) and prints the results
sg_seek	performs a SCSI SEEK or PRE-FETCH command on a device and it's cache
sg_senddiag	performs a SCSI SEND DIAGNOSTIC command
sg_ses	sends controls and fetches the current status from a SCSI Enclosure Services (SES) device
sg_ses_microcode	sends microcode to a SCSI enclosure
sg_start	sends a SCSI START STOP UNIT command to start, stop, load or eject medium
sg_stpg	sends a SCSI SET TARGET PORT GROUPS command
sg_stream_ctl	performs a SCSI STREAM CONTROL or GET STREAM STATUS command on a device to open or close an I/O stream
sg_sync	sends a SCSI command to synchronize the cache
sg_test_rwbuf	tests the SCSI host adapter by issuing write and read operations on a device's buffer and calculating checksums
sg_timestamp	reports or sets the timestamp on a SCSI device
sg_turs	sends one or more SCSI TEST UNIT READY commands
sg_unmap	sends a SCSI UNMAP command
sg_verify	invokes SCSI VERIFY command(s) on a block device
sg_vpd	fetches Vital Product Data (VPD) pages using a SCSI INQUIRY command
sg_write_buffer	sends a SCSI WRITE BUFFER command
sg_write_long	sends a SCSI WRITE LONG command
sg_write_same	sends a SCSI WRITE SAME command
sg_write_verify	sends a SCSI WRITE AND VERIFY command
sg_write_x	performs SCSI WRITE commands on a device
sg_wr_mode	writes mode pages
sg_xcopy	copies data to and from files and devices using SCSI EXTENDED COPY (XCOPY)
sg_zone	performs SCSI ZONE commands on a device, such as OPEN, CLOSE, FINISH or SEQUENTIALIZE
`libsgutils2.so`	contains the sg3_utils API functions

sysmon-qt-2.0

Introduction to sysmon-qt

The sysmon-qt package provides a program to monitor system values including CPU usage, memory usage, and system temperatures in a compact screen window.

This package is known to build and work properly using an LFS 12.1 platform.

Note

There is also a version of this package, sysmon-qt-1.1, at the same location as below that is based on (Qt-5.15.12 or qt-alternate-5.15.12). The build instructions are identical to these. The functionality is the same and it does not make sense to build both versions.

Package Information

Download (HTTP): https://github.com/lfs-book/sysmon-qt/releases/download/v2.0/sysmon-qt-2.0.tar.xz
Download MD5 sum: 9477952e6918c383cbfee36f710d0a34
Download size: 76 KB
Estimated disk space required: 1.1 MB
Estimated build time: 0.3 SBU

sysmon-qt Dependencies

Required

Qt-6.6.2

Installation of sysmon-qt

Install sysmon-qt by running the following commands:

cd src               &&
qmake6 sysmon-qt.pro &&
make

This package does not come with a test suite.

Now, as the root user:

cp sysmon-qt                 /usr/bin                 &&
cp ../data/sysmon-qt.desktop /usr/share/applications/ &&
cp ../data/sysmon-qt.png     /usr/share/pixmaps/

Installed Programs: sysmon-qt

Installed Library: None

Installed Directories: None

Sysstat-12.7.5

Introduction to Sysstat

The Sysstat package contains utilities to monitor system performance and usage activity. Sysstat contains the sar utility, common to many commercial Unixes, and tools you can schedule via cron to collect and historize performance and activity data.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://sysstat.github.io/sysstat-packages/sysstat-12.7.5.tar.xz
Download MD5 sum: c5cac550f88327f0a93b12f6da93a0cb
Download size: 896 KB
Estimated disk space required: 29 MB
Estimated build time: 0.1 SBU

Sysstat Dependencies

There are no build-time requirements for this package; however, it is designed to be controlled by a cron daemon such as Fcron-3.2.1.

Installation of Sysstat

Install Sysstat by running the following commands:

sa_lib_dir=/usr/lib/sa    \
sa_dir=/var/log/sa        \
conf_dir=/etc/sysstat     \
./configure --prefix=/usr \
            --disable-file-attr &&
make

This package does not come with a working test suite.

Now, as the root user:

make install

Command Explanations

sa_lib_dir: This environment variable specifies the location of the package-specific library directory.

sa_dir: This environment variable specifies the location of the directory containing the data files.

conf_dir: This environment variable specifies the location of the system configuration directory.

--disable-file-attr: Do not set attributes on files being installed. This parameter causes the installation to ignore the man group variable resulting in the man files having root: root ownership.

Note

Run ./configure --help to see other influential environment variables you can pass to configure. You may want to use the history and compressafter variables to customize the amount of data files kept on the system.

Configuring Sysstat

Config Files

/etc/sysconfig/sysstat and /etc/sysconfig/sysstat.ioconf

Cron Information

To begin gathering Sysstat history information, you must add to, or create a privileged user's crontab. The history data location is /var/log/sa. The user running Sysstat utilities via cron must have write access to this location.

Below is an example of what to install in the crontab. Adjust the parameters to suit your needs. Use man sa1 and man sa2 for information about the commands.

# 8am-7pm activity reports every 10 minutes during weekdays
0 8-18 * * 1-5 /usr/lib/sa/sa1 600 6 &

# 7pm-8am activity reports every hour during weekdays
0 19-7 * * 1-5 /usr/lib/sa/sa1 &

# Activity reports every hour on Saturday and Sunday
0 * * * 0,6 /usr/lib/sa/sa1 &

# Daily summary prepared at 19:05
5 19 * * * /usr/lib/sa/sa2 -A &

Ensure you submit the revised crontab to the cron daemon.

System Startup Information

At system startup, a LINUX RESTART message must be inserted in the daily data file to reinitialize the kernel counters. This can be automated by installing the /etc/rc.d/init.d/sysstat init script included in the blfs-bootscripts-20240209 package using the following command as the root user:

make install-sysstat

Installed Programs: cifsiostat, iostat, mpstat, pidstat, sadf, sar, and tapestat

Installed Libraries: None

Installed Directories: /usr/lib/sa, /usr/share/doc/sysstat-12.7.5 and /var/log/sa

Short Descriptions

cifsiostat	displays statistics about read and write operations on CIFS filesystems
iostat	reports CPU statistics and input/output statistics for devices and partitions
mpstat	writes activities for each available processor
pidstat	is used for monitoring individual tasks currently being managed by the Linux kernel
sadf	is used for displaying the contents of data files created by the sar command. But unlike sar, sadf can write its data in many different formats
sar	is used for displaying the contents of elected cumulative activity counters in the operating system
tapestat	is used for monitoring the activity of tape drives connected to a system

UDisks-2.10.1

Introduction to UDisks

The UDisks package provides a daemon, tools and libraries to access and manipulate disks and storage devices.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/storaged-project/udisks/releases/download/udisks-2.10.1/udisks-2.10.1.tar.bz2
Download MD5 sum: 613af9bfea52cde74d2ac34d96de544d
Download size: 1.8 MB
Estimated disk space required: 44 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

UDisks Dependencies

Required

libatasmart-0.19, libblockdev-3.1.0, libgudev-238, libxslt-1.1.39, and Polkit-124

Optional (Required if building GNOME)

Optional

D-Bus Python-1.3.2 (for the integration tests), GTK-Doc-1.33.2, LVM2-2.03.23, PyGObject-3.46.0 (for the integration tests), exFAT, and libiscsi

Optional Runtime Dependencies

btrfs-progs-6.7.1, dbus-1.14.10, dosfstools-4.2, gptfdisk-1.0.10, mdadm-4.2, and xfsprogs-6.6.0

Installation of UDisks

Install UDisks by running the following commands:

./configure --prefix=/usr        \
            --sysconfdir=/etc    \
            --localstatedir=/var \
            --disable-static     \
            --enable-available-modules &&
make

To test the results, issue: make check. A more thorough test can be run with make ci. You must first create the directories /var/run/udisks2 and /var/lib/udisks2, and the optional python modules should be present.

Now, as the root user:

make install

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

--enable-gtk-doc: Use this parameter if GTK-Doc is installed and you wish to rebuild and install the API documentation.

--enable-available-modules: This switch enables additional UDisks2 functionalities if libblockdev-3.1.0 has been built with optional dependencies.

Installed Programs: udisksctl and umount.udisks2

Installed Library: libudisks2.so

Installed Directories: /etc/udisks2, /usr/include/udisks2, /usr/libexec/udisks2, /usr/share/gtk-doc/html/udisks2, and /var/lib/udisks2

Short Descriptions

udisksctl	is a command-line program used to interact with the udisksd daemon
umount.udisks2	is a command-line program used to unmount file systems that have been mounted by the UDisks daemon
`libudisks2.so`	contains the UDisks API functions

UnRar-6.2.12

Introduction to UnRar

The UnRar package contains a RAR extraction utility used for extracting files from RAR archives. RAR archives are usually created with WinRAR, primarily in a Windows environment.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.rarlab.com/rar/unrarsrc-6.2.12.tar.gz
Download MD5 sum: 1f526429e8e50a9b3b94f325b2848c24
Download size: 244 KB
Estimated disk space required: 2.3 MB
Estimated build time: 0.1 SBU

Installation of UnRar

Note

This package extracts the tarball to the unversioned directory unrar and not the expected directory unrar-6.2.12.

Install UnRar by running the following commands:

make -f makefile

This package does not come with a test suite.

Now, as the root user:

install -v -m755 unrar /usr/bin

Installed Program: unrar

Installed Libraries: None

Installed Directories: None

Short Descriptions

unrar

uncompresses a RAR archive

UnZip-6.0

Introduction to UnZip

The UnZip package contains ZIP extraction utilities. These are useful for extracting files from ZIP archives. ZIP archives are created with PKZIP or Info-ZIP utilities, primarily in a DOS environment.

This package is known to build and work properly using an LFS 12.1 platform.

Caution

The previous version of the UnZip package had some locale related issues. Currently there are no BLFS editors capable of testing these locale issues. Therefore, the locale related information is left on this page, but has not been tested. A more general discussion of these problems can be found in the Program Assumes Encoding section of the Locale Related Issues page.

Package Information

Download (HTTP): https://downloads.sourceforge.net/infozip/unzip60.tar.gz
Download MD5 sum: 62b490407489521db863b523a7f86375
Download size: 1.3 MB
Estimated disk space required: 9 MB
Estimated build time: less than 0.1 SBU

Additional Downloads

Required patch: https://www.linuxfromscratch.org/patches/blfs/12.1/unzip-6.0-consolidated_fixes-1.patch

UnZip Locale Issues

Note

Use of UnZip in the JDK, Mozilla, DocBook or any other BLFS package installation is not a problem, as BLFS instructions never use UnZip to extract a file with non-ASCII characters in the file's name.

These issues are thought to be fixed in the patch. But since none of the editors have data to test this, the following workarounds are retained in case they might still be needed.

The UnZip package assumes that filenames stored in the ZIP archives created on non-Unix systems are encoded in CP850, and that they should be converted to ISO-8859-1 when writing files onto the filesystem. Such assumptions are not always valid. In fact, inside the ZIP archive, filenames are encoded in the DOS codepage that is in use in the relevant country, and the filenames on disk should be in the locale encoding. In MS Windows, the OemToChar() C function (from User32.DLL) does the correct conversion (which is indeed the conversion from CP850 to a superset of ISO-8859-1 if MS Windows is set up to use the US English language), but there is no equivalent in Linux.

When using unzip to unpack a ZIP archive containing non-ASCII filenames, the filenames are damaged because unzip uses improper conversion when any of its encoding assumptions are incorrect. For example, in the ru_RU.KOI8-R locale, conversion of filenames from CP866 to KOI8-R is required, but conversion from CP850 to ISO-8859-1 is done, which produces filenames consisting of undecipherable characters instead of words (the closest equivalent understandable example for English-only users is rot13). There are several ways around this limitation:

1) For unpacking ZIP archives with filenames containing non-ASCII characters, use WinZip while running the Wine Windows emulator.

2) Use bsdtar -xf from libarchive-3.7.2 to unpack the ZIP archive. Then fix the damage made to the filenames using the convmv tool (https://j3e.de/linux/convmv/). The following is an example for the zh_CN.UTF-8 locale:

convmv -f cp936 -t utf-8 -r --nosmart --notest \
    </path/to/unzipped/files>

Installation of UnZip

First apply the patch:

patch -Np1 -i ../unzip-6.0-consolidated_fixes-1.patch

Now compile the package:

make -f unix/Makefile generic

The test suite does not work for target “generic”.

Now, as the root user:

make prefix=/usr MANDIR=/usr/share/man/man1 \
 -f unix/Makefile install

Command Explanations

make -f unix/Makefile generic: This target begins by running a configure script (unlike the older targets such as linux and linux_noasm) which creates a flags file that is then used in the build. This ensures that the 32-bit x86 build receives the right flags to unzip files which are larger than 2GB when extracted.

Installed Programs: funzip, unzip, unzipfsx, zipgrep, and zipinfo

Installed Libraries: None

Installed Directories: None

Short Descriptions

funzip	allows the output of unzip commands to be redirected
unzip	lists, tests or extracts files from a `ZIP` archive
unzipfsx	is a self-extracting stub that can be prepended to a `ZIP` archive. Files in this format allow the recipient to decompress the archive without installing UnZip
zipgrep	searches files in a `ZIP` archive for lines matching a pattern
zipinfo	produces technical information about the files in a `ZIP` archive, including file access permissions, encryption status, type of compression, etc

UPower-1.90.2

Introduction to UPower

The UPower package provides an interface for enumerating power devices, listening to device events and querying history and statistics. Any application or service on the system can access the org.freedesktop.UPower service via the system message bus.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://gitlab.freedesktop.org/upower/upower/-/archive/v1.90.2/upower-v1.90.2.tar.bz2
Download MD5 sum: bfd6e3275e61d7e097b53eb2b216fffa
Download size: 136 KB
Estimated disk space required: 6.5 MB (add 1.1 MB for tests)
Estimated build time: less than 0.1 SBU (using parallelism=4, add 0.6 SBU for tests)

UPower Dependencies

Required

libgudev-238 and libusb-1.0.27

Optional (Required if building GNOME)

Optional

GTK-Doc-1.33.2, libxslt-1.1.39, docbook-xsl-nons-1.79.2, PyGObject-3.46.0, dbusmock-0.30.2, umockdev-0.17.18 (for part of the test suite), and libimobiledevice

Installation of UPower

First, remove an unneeded dependency from a test:

sed '/parse_version/d' -i src/linux/integration-test.py

Install UPower by running the following commands:

mkdir build &&
cd    build &&

meson setup ..                  \
      --prefix=/usr             \
      --buildtype=release       \
      -Dgtk-doc=false           \
      -Dman=false               \
      -Dsystemdsystemunitdir=no \
      -Dudevrulesdir=/usr/lib/udev/rules.d &&
ninja

To test the results, issue: LC_ALL=C ninja test. Some checks may not pass due to missing files. The test suite should be run from a local GUI session started with dbus-launch. On 32-bit machines, one test will fail due to rounding errors: Tests.test_battery_energy_charge_mixed. On some systems, two tests relating to the headphone hotplug feature are known to fail. Those can be safely ignored since the functionality still works. The test named Tests.test_bluetooth_le_device is known to fail with dbusmock-0.30.1 or later.

Now, as the root user:

ninja install

Command Explanations

-Dgtk-doc=false: Prevents building the documentation. Remove this if you have GTK-Doc installed and wish to build the documentation.

-Dman=false: Prevents building the manual pages. Remove this if you have libxslt-1.1.39 and docbook-xsl-nons-1.79.2 installed and wish to build the manual pages.

-Dsystemdsystemunitdir=no: Removes the dependency on systemd.

-Dudevrulesdir=/usr/lib/udev/rules.d: Tells the build system where to install udev rules because the information is missing in /usr/lib/pkgconfig/libudev.pc

Installed Program: upower

Installed Libraries: libupower-glib.so

Installed Directories: /etc/UPower, /usr/include/libupower-glib, and /var/lib/upower

Short Descriptions

upower	is the UPower command line tool
`libupower-glib.so`	contains the UPower API functions

usbutils-017

Introduction to USB Utils

The USB Utils package contains utilities used to display information about USB buses in the system and the devices connected to them.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://kernel.org/pub/linux/utils/usb/usbutils/usbutils-017.tar.xz
Download MD5 sum: 8ff21441faf2e8128e4810b3d6e49059
Download size: 168 KB
Estimated disk space required: 4.4 MB
Estimated build time: 0.1 SBU

USB Utils Dependencies

Required

libusb-1.0.27

Installation of USB Utils

Install USB Utils by running the following commands:

./configure --prefix=/usr --datadir=/usr/share/hwdata &&
make

This package does not come with a test suite.

Now, as the root user:

make install

To install the usb.ids data file, using Wget-1.21.4, run, as the root user:

install -dm755 /usr/share/hwdata/ &&
wget http://www.linux-usb.org/usb.ids -O /usr/share/hwdata/usb.ids

The script lsusb.py displays information in a more easily readable form than lsusb. To find the options, use lsusb.py -h. One form of use recommended by the developer is lsusb.py -ciu.

Configuring USB Utils

The usb.ids data file is constantly being updated. To get a current version of this file, using Wget-1.21.4, periodically run again, as the root user:

wget http://www.linux-usb.org/usb.ids -O /usr/share/hwdata/usb.ids

You should update the /usr/share/hwdata/usb.ids file periodically. If you've installed Fcron-3.2.1 and completed the section on periodic jobs, execute the following commands, as the root user, to create a weekly cron job:

cat > /etc/cron.weekly/update-usbids.sh << "EOF" &&
#!/bin/bash
/usr/bin/wget http://www.linux-usb.org/usb.ids -O /usr/share/hwdata/usb.ids
EOF
chmod 754 /etc/cron.weekly/update-usbids.sh

Installed Programs: lsusb, lsusb.py, usb-devices, and usbhid-dump

Installed Libraries: None

Installed Directories: None

Short Descriptions

lsusb	is a utility for displaying information about all USB buses in the system and all devices connected to them, but not in human friendly form
lsusb.py	displays information about all USB buses in the system and all devices connected to them in reasonable human friendly form
usb-devices	is a shell script that displays details of USB buses and devices connected to them. It is designed to be used if /proc/bus/usb/devices is not available on your system
usbhid-dump	is used to dump report descriptors and streams from HID (human interface device) interfaces of USB devices

Which-2.21 and Alternatives

The presence or absence of the which program in the main LFS book is probably one of the most contentious issues on the mailing lists. It has resulted in at least one flame war in the past. To hopefully put an end to this once and for all, presented here are two options for equipping your system with which. The question of which “which” is for you to decide.

Introduction to GNU Which

The first option is to install the actual GNU which package.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/which/which-2.21.tar.gz
Download MD5 sum: 097ff1a324ae02e0a3b0369f07a7544a
Download size: 148 KB
Estimated disk space required: 1 MB
Estimated build time: less than 0.1 SBU

Installation of Which

Install which by running the following commands:

./configure --prefix=/usr &&
make

This package does not come with a test suite.

Now, as the root user:

make install

Installed Program: which

Installed Libraries: None

Installed Directories: None

Short Descriptions

which

shows the full path of (shell) commands installed in your PATH

The 'which' Script

The second option (for those who don't want to install the package) is to create a simple script (execute as the root user):

cat > /usr/bin/which << "EOF"
#!/bin/bash
type -pa "$@" | head -n 1 ; exit ${PIPESTATUS[0]}
EOF
chmod -v 755 /usr/bin/which
chown -v root:root /usr/bin/which

This should work OK and is probably the easiest solution for most cases, but is not the most comprehensive implementation.

Zip-3.0

Introduction to Zip

The Zip package contains Zip utilities. These are useful for compressing files into ZIP archives.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://downloads.sourceforge.net/infozip/zip30.tar.gz
Download MD5 sum: 7b74551e63f8ee6aab6fbc86676c0d37
Download size: 1.1 MB
Estimated disk space required: 6.4 MB
Estimated build time: 0.1 SBU

Installation of Zip

Install Zip by running the following commands:

make -f unix/Makefile generic_gcc

This package does not come with a test suite.

Now, as the root user:

make prefix=/usr MANDIR=/usr/share/man/man1 -f unix/Makefile install

Command Explanations

make prefix=/usr -f unix/Makefile install: This command overrides the prefix variable that is set to /usr/local in the unix/Makefile. Alternatives to generic_gcc can be seen with a make -f unix/Makefile list command.

Installed Programs: zip, zipcloak, zipnote, and zipsplit

Installed Libraries: None

Installed Directories: None

Short Descriptions

zip	compresses files into a `ZIP` archive
zipcloak	is a utility to encrypt and decrypt a `ZIP` archive
zipnote	reads or writes comments stored in a `ZIP` file
zipsplit	is a utility to split `ZIP` files into smaller files

Chapter 13. Programming

A base LFS system can be used as a development platform, however the base system only includes language support for C, C++, Perl, and Python. This chapter provides instructions to build many popular programming environments to greatly expand your system's development capabilities.

Cbindgen-0.26.0

Introduction to Cbindgen

Cbindgen can be used to generate C bindings for Rust code.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/mozilla/cbindgen/archive/v0.26.0/cbindgen-0.26.0.tar.gz
Download MD5 sum: f3ef70691bc4743b8f76ca6d27847ba4
Download size: 216 KB
Estimated disk space required: 121 MB (add 600 MB for tests)
Estimated build time: 0.5 SBU (add 0.4 SBU for tests), both on a 4-core machine

cbindgen Dependencies

Required

rustc-1.76.0

Note

An Internet connection is needed for building this package.

Installation of cbindgen

Install cbindgen by running the following commands:

cargo build --release

To test the results, issue: cargo test. Three tests in profile.rs are known to fail.

Now, as the root user:

install -Dm755 target/release/cbindgen /usr/bin/

Installed Program: cbindgen

Installed Library: none

Installed Directory: none

Short Descriptions

cbindgen

generates C bindings for Rust code

Clisp-2.49

Introduction to Clisp

GNU Clisp is a Common Lisp implementation which includes an interpreter, compiler, debugger, and many extensions.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/clisp/latest/clisp-2.49.tar.bz2
Download MD5 sum: 1962b99d5e530390ec3829236d168649
Download size: 7.8 MB
Estimated disk space required: 163 MB (add 8 MB for tests)
Estimated build time: 0.9 SBU (1.2 SBU with tests)

Additional Downloads

Optional patch: https://www.linuxfromscratch.org/patches/blfs/12.1/clisp-2.49-readline7_fixes-1.patch (required if building against libffcall)

Clisp Dependencies

Optional

libnsl-2.0.1 and libffcall

Installation of Clisp

Note

This package does not support parallel build.

If you are building on a 32-bit system, work around a bug in GCC caused by the latest version of binutils:

case $(uname -m) in
    i?86) export CFLAGS="${CFLAGS:--O2 -g} -falign-functions=4" ;;
esac

Remove two tests, which fail for unknown reasons:

sed -i -e '/socket/d' -e '/"streams"/d' tests/tests.lisp

Install Clisp by running the following commands:

If you are building clisp against libffcall, apply the patch to fix a build failure with current readline:

patch -Np1 -i ../clisp-2.49-readline7_fixes-1.patch

Install Clisp by running the following commands:

mkdir build &&
cd    build &&

../configure --srcdir=../                       \
             --prefix=/usr                      \
             --docdir=/usr/share/doc/clisp-2.49 \
             --with-libsigsegv-prefix=/usr &&

ulimit -s 16384 &&
make -j1

To test the results, issue: make check.

Now, as the root user:

make install

Command Explanations

ulimit -s 16384: this increases the maximum stack size, as recommended by the configure.

--docdir=/usr/share/doc/clisp-2.49: this ensures the html documentation will go into a versioned directory instead of straight into /usr/share/html/.

--with-libsigsegv-prefix=/usr: use this to tell configure that you have installed libsigsegv in /usr, otherwise it will not be found.

--with-libffcall-prefix=/usr: use this to tell configure that you have installed the optional libffcall in /usr, otherwise like libsigsegv it will not be found.

Installed Programs: clisp, clisp-link

Installed Libraries: various static libraries in /usr/lib/clisp-2.49/base/

Installed Directories: /usr/lib/clisp-2.49 /usr/share/doc/clisp-2.49 /usr/share/emacs/site-lisp;

Short Descriptions

clisp	is an ANSI Common Lisp compiler, interpreter, and debugger
clisp-link	is used to link an external module to clisp

CMake-3.28.3

Introduction to CMake

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 since version 4.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://cmake.org/files/v3.28/cmake-3.28.3.tar.gz
Download MD5 sum: 6b16c82b81e1fd80b63bee9696846b21
Download size: 11 MB
Estimated disk space required: 435 MB (add 1.2 GB for tests)
Estimated build time: 2.2 SBU (add 3.9 SBU for tests, both using parallelism=4)

CMake Dependencies

Optional

GCC-13.2.0 (for gfortran), git-2.44.0 (for use during tests), Mercurial-6.6.3 (for use during tests), OpenJDK-21.0.2 (for use during tests), (Qt-5.15.12 or qt-alternate-5.15.12) or Qt-6.6.2 (for the Qt-based GUI), sphinx-7.2.6 (for building documents), Subversion-1.14.3 (for testing), cppdap, jsoncpp, and rhash

Installation of CMake

Install CMake by running the following commands:

sed -i '/"lib64"/s/64//' Modules/GNUInstallDirs.cmake &&

./bootstrap --prefix=/usr        \
            --system-libs        \
            --mandir=/share/man  \
            --no-system-jsoncpp  \
            --no-system-cppdap   \
            --no-system-librhash \
            --docdir=/share/doc/cmake-3.28.3 &&
make

To test the results, issue: LC_ALL=en_US.UTF-8 bin/ctest -j<N> -O cmake-3.28.3-test.log, where <N> is an integer between 1 and the number of system cores. Setting LC_ALL is needed to prevent some test failures when some of the locale variables are set to non English locales.

If you want to investigate a problem with a given "problem1-test", use bin/ctest -R "problem1-test" and, to omit it, use bin/ctest -E "problem1-test". These options can be used together: bin/ctest -R "problem1-test" -E "problem2-test". Option -N can be used to display all available tests, and you can run bin/ctest for a sub-set of tests by using separated by spaces names or numbers as options. Option --help can be used to show all options.

Now, as the root user:

make install

Command Explanations

sed ... Modules/GNUInstallDirs.cmake: This command disables applications using cmake from attempting to install files in /usr/lib64/.

--system-libs: This switch forces the build system to link against the system installed version for all needed libraries but those explicitly specified via a --no-system-* option.

--no-system-jsoncpp and --no-system-cppdap: These switches remove the 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 libraries used. A bundled version of that library is used instead.

--no-system-{curl,libarchive,libuv,nghttp2}: Use the corresponding option in the list for the bootstrap if one of the recommended dependencies is not installed. A bundled version of the dependency will be used instead.

--qt-gui: This switch enables building the Qt-based GUI for CMake.

--parallel=: This switch enables performing the CMake bootstrap with multiple jobs at one time.

Installed Programs: ccmake, cmake, cmake-gui (optional), cpack, and ctest

Installed Libraries: None

Installed Directories: /usr/share/cmake-3.28 and /usr/share/doc/cmake-3.28.3

Short Descriptions

ccmake	is a curses based interactive frontend to cmake
cmake	is the makefile generator
cmake-gui	(optional) is the Qt-based frontend to cmake
cpack	is the CMake packaging program
ctest	is a testing utility for cmake-generated build trees

Doxygen-1.10.0

Introduction to Doxygen

The Doxygen package contains a documentation system for C++, C, Java, Objective-C, Corba IDL and to some extent PHP, C# and D. It is useful for generating HTML documentation and/or an off-line reference manual from a set of documented source files. There is also support for generating output in RTF, PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation is extracted directly from the sources, which makes it much easier to keep the documentation consistent with the source code.

You can also configure Doxygen to extract the code structure from undocumented source files. This is very useful to quickly find your way in large source distributions. Used along with Graphviz, you can also visualize the relations between the various elements by means of include dependency graphs, inheritance diagrams, and collaboration diagrams, which are all generated automatically.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://doxygen.nl/files/doxygen-1.10.0.src.tar.gz
Download MD5 sum: c7455e9961c3491479929935c5087bf6
Download size: 8.0 MB
Estimated disk space required: 253 MB (with tests)
Estimated build time: 2.1 SBU (using parallelism=4; with tests)

Doxygen Dependencies

Required

CMake-3.28.3 and git-2.44.0

Optional

Graphviz-10.0.1, ghostscript-10.02.1, libxml2-2.12.5 (required for the tests), LLVM-17.0.6 (with clang), (Qt-5.15.12 or qt-alternate-5.15.12) (for doxywizard), texlive-20230313 (or install-tl-unx), xapian-1.4.24 (for doxyindexer), and javacc

Installation of Doxygen

Note

When untarring this package, you may see messages such as “Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.TextEncoding'”. These messages are harmless, and can be safely ignored.

First, fix up some python scripts:

grep -rl '^#!.*python$' | xargs sed -i '1s/python/&3/'

Install Doxygen by running the following commands:

mkdir -v build &&
cd       build &&

cmake -G "Unix Makefiles"         \
      -DCMAKE_BUILD_TYPE=Release  \
      -DCMAKE_INSTALL_PREFIX=/usr \
      -Wno-dev .. &&

make

To test the results, issue: make tests.

If you wish to generate the package documentation, you must have Python, TeX Live (for HTML docs) and Ghostscript (for PDF docs) installed, then issue the following command:

cmake -DDOC_INSTALL_DIR=share/doc/doxygen-1.10.0 -Dbuild_doc=ON .. &&

make docs

Now, as the root user:

make install &&
install -vm644 ../doc/*.1 /usr/share/man/man1

If you have generated the package documentation, then the man pages are automatically installed, and you do not need to run the last install ... command.

Command Explanations

-Dbuild_wizard=ON: Use this switch if Qt5 is installed and you wish to build the GUI front-end.

-Dbuild_search=ON: Use this switch if xapian is installed and you wish to build external search tools (doxysearch.cgi and doxyindexer).

-Duse_libclang=ON: Use this switch if llvm with clang are installed, to add support for libclang parsing.

Configuring Doxygen

There is no real configuration necessary for the Doxygen package although three additional packages are required if you wish to use extended capabilities. If you require formulas to create PDF documentation, then you must have texlive-20230313 installed. If you require formulas to convert PostScript files to bitmaps, then you must have ghostscript-10.02.1 installed.

Installed Programs: doxygen and optionally, doxywizard, doxyindexer and doxysearch.cgi

Installed Libraries: None

Installed Directory: /usr/share/doc/doxygen-1.10.0

Short Descriptions

doxygen	is a command-line based utility used to generate template configuration files and then generate documentation from these templates. Use doxygen --help for an explanation of the command-line parameters
doxywizard	is a GUI front-end for configuring and running doxygen
doxyindexer	generates a search index called `doxysearch.db` from one or more search data files produced by doxygen. See, e.g. https://javacc.github.io/javacc/
doxysearch.cgi	is a CGI program to search the data indexed by doxyindexer

GCC-13.2.0

Introduction to GCC

The GCC package contains the GNU Compiler Collection. This page describes the installation of compilers for the following languages: C, C++, Fortran, Objective C, Objective C++, Go, and Modula2. Since C and C++ are installed in LFS, this page is either for upgrading C and C++, or for installing additional compilers.

Note

Additional languages, among which D and Ada, are available in the collection. D and Ada have a binary bootstrap requirement for the first installation, so their installation is not described here. To install them, you can proceed along the same lines as below after installing the corresponding compiler from a binary package, adding ada or d to the --enable-languages line.

This package is known to build and work properly using an LFS 12.1 platform.

Caution

If you are upgrading GCC from any other version prior to 13.2.0, then you must be careful compiling 3rd party kernel modules. You should ensure that the kernel and all its native modules are also compiled using the same version of GCC that you use to build the 3rd party module. This issue does not affect native kernel (and kernel modules) updates, as the instructions below are a complete reinstallation of GCC. If you have existing 3rd party modules installed, ensure they are recompiled using the updated version of GCC. As always, never update the kernel headers from the ones used when Glibc was compiled during LFS.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/gcc/gcc-13.2.0/gcc-13.2.0.tar.xz
Download MD5 sum: e0e48554cc6e4f261d55ddee9ab69075
Download size: 84 MB
Estimated disk space required: 13 GB (2.9 GB installed with all listed languages; add 1.5 GB for tests)
Estimated build time: 13 SBU (add 29 SBU for tests; both with parallelism=8)

GCC Dependencies

Optional

GDB-14.1, Valgrind-3.22.0 (for tests), and ISL (to enable graphite optimization)

Installation of GCC

Important

Even if you specify only languages other than C and C++ to the ./configure command below, the installation process will overwrite your existing GCC C and C++ compilers and libraries. Running the full suite of tests is recommended.

Do not continue with the make install command until you are confident the build was successful. You can compare your test results with those found at https://gcc.gnu.org/ml/gcc-testresults/. You may also want to refer to the information found in the GCC section of Chapter 8 in the LFS book (../../../../lfs/view/12.1/chapter08/gcc.html).

The instructions below are intentionally performing a “bootstrap” process. Bootstrapping is needed for robustness and is highly recommended when upgrading the compilers version. To disable bootstrap anyway, add --disable-bootstrap to the ./configure options below.

Install GCC by running the following commands:

case $(uname -m) in
  x86_64)
    sed -i.orig '/m64=/s/lib64/lib/' gcc/config/i386/t-linux64
  ;;
esac

mkdir build               &&
cd    build               &&

../configure              \
    --prefix=/usr         \
    --disable-multilib    \
    --with-system-zlib    \
    --enable-default-pie  \
    --enable-default-ssp  \
    --disable-fixincludes \
    --enable-languages=c,c++,fortran,go,objc,obj-c++,m2 &&
make

If you have installed additional packages such as 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-13.2.0, about 65 FAIL occur in the “guality” suite, as well as miscellaneous failures throughout the rest of the test suite. If all the compilers above are built, there will be a little over 80 unexpected failures out of over 546,000 tests. To run the tests, issue:

ulimit -s 32768 &&
make -k check

The tests are very long, and the results may be hard to find in the logs, specially if you use parallel jobs with make. You can get a summary of the tests with:

../contrib/test_summary

Now, as the root user:

make install &&

mkdir -pv /usr/share/gdb/auto-load/usr/lib              &&
mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib &&

chown -v -R root:root \
    /usr/lib/gcc/*linux-gnu/13.2.0/include{,-fixed}

Command Explanations

mkdir build; cd build: The GCC documentation recommends building the package in a dedicated build directory.

--disable-multilib: This parameter ensures that files are created for the specific architecture of your computer.

--with-system-zlib: Uses the system zlib instead of the bundled one. zlib is used for compressing and decompressing GCC's intermediate language in LTO (Link Time Optimization) object files.

--enable-default-pie: Makes the -fpie option the default when compiling programs. Together with the ASLR feature enabled in the kernel, this defeats some kind of attacks based on known memory layouts.

--enable-default-ssp: Makes the -fstack-protector-strong option the default when compiling programs. SSP is a technique preventing alteration of the program flow by corrupting the parameter stack.

--enable-languages=c,c++,fortran,go,objc,obj-c++,m2: This command identifies which languages to build. You may modify this command to remove undesired languages. GCC also supports Ada and D, but building GCC with Ada (or D) support needs an existing Ada (or D) compiler. So they are not enabled here.

ulimit -s 32768: This command prevents several tests from running out of stack space.

make -k check: This command runs the test suite without stopping if any errors are encountered.

../contrib/test_summary: This command will produce a summary of the test suite results. You can append | grep -A7 Summ to the command to produce an even more condensed version of the summary. You may also wish to redirect the output to a file for review and comparison later on.

mv -v /usr/lib/*gdb.py ...: The installation 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.

chown -v -R root:root /usr/lib/gcc/*linux-gnu/...: If the package is built by a user other than root, the ownership of the installed include directory (and its content) will be incorrect. This command changes the ownership to the root user and group.

--enable-host-shared --enable-languages=jit: Build libgccjit, a library for embedding GCC inside programs and libraries for generating machine code. Despite “JIT” (just-in-time) in the name, the library can be used for AOT (ahead-of-time) compilation as well. --enable-host-shared is needed for building libgccjit, but it significantly slows down GCC. So libgccjit should be built and installed separately, not as a part of the “main” GCC installation. If you need this library, configure GCC with these two options and install the library by running make -C gcc jit.install-common jit.install-info as the root user. This library is not used by any BLFS package, nor tested by the BLFS developers.

Some program and library names and descriptions are not listed here, but can be found at LFS section for GCC as they were initially installed during the building of LFS.

Installed Programs: gccgo, gfortran, gm2, go, and gofmt, hard-linked to architecture specific names

Installed Libraries: libgfortran.{so,a}, libgm2.{so,a} libgo.{so,a}, libgobegin.a, libgolibbegin.a, libobjc.{so,a}, and numerous other run-time libraries and executables

Installed Directories: /usr/lib/go

Short Descriptions

gccgo	is a GCC-based compiler for the Go language
gm2	is a GCC-based compiler for the Modula-2 language
go	is a tool for managing Go source code
gofmt	is a tool for formatting Go source code
gfortran	is a GCC-based compiler for the Fortran language

GC-8.2.6

Introduction to GC

The GC package contains the Boehm-Demers-Weiser conservative garbage collector, which can be used as a garbage collecting replacement for the C malloc function or C++ new operator. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory that is no longer useful. The collector automatically recycles memory when it determines that it can no longer be otherwise accessed. The collector is also used by a number of programming language implementations that either use C as intermediate code, want to facilitate easier interoperation with C libraries, or just prefer the simple collector interface. Alternatively, the garbage collector may be used as a leak detector for C or C++ programs, though that is not its primary goal.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/ivmai/bdwgc/releases/download/v8.2.6/gc-8.2.6.tar.gz
Download MD5 sum: fc5351214bc2e854070ee3319181a467
Download size: 1.2 MB
Estimated disk space required: 11 MB (with tests)
Estimated build time: 0.2 SBU (with tests)

Optional

libatomic_ops-7.8.2

Installation of GC

Install GC by running the following commands:

./configure --prefix=/usr      \
            --enable-cplusplus \
            --disable-static   \
            --docdir=/usr/share/doc/gc-8.2.6 &&
make

To test the results, issue: make check.

Now, as the root user:

make install &&
install -v -m644 doc/gc.man /usr/share/man/man3/gc_malloc.3

Command Explanations

--docdir=/usr/share/doc/gc-8.2.6: This option is used so the package will install the documentation in a versioned directory.

--enable-cplusplus: This parameter enables the building and installing of the C++ library along with the standard C library.

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: None

Installed Libraries: libcord.so, libgc.so, libgccpp.so, and libgctba.so

Installed Directories: /usr/include/gc and /usr/share/doc/gc-8.2.6

Short Descriptions

`libcord.so`	contains a tree-based string library
`libgc.so`	contains a C interface to the conservative garbage collector, primarily designed to replace the C malloc function
`libgccpp.so`	contains a C++ interface to the conservative garbage collector
`libgctba.so`	contains a C++ interface to throw bad allocations

GDB-14.1

Introduction to GDB

GDB, the GNU Project debugger, allows you to see what is going on “inside” another program while it executes -- or what another program was doing at the moment it crashed. Note that GDB is most effective when tracing programs and libraries that were built with debugging symbols and not stripped.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/gdb/gdb-14.1.tar.xz
Download MD5 sum: 4a084d03915b271f67e9b8ea2ab24972
Download size: 23 MB
Estimated disk space required: 966 MB (add 805 MB for docs; add 710 MB for tests)
Estimated build time: 2.1 SBU (add 0.4 SBU for docs; add 18 SBU for tests; all using parallelism=4)

GDB Dependencies

Recommended Runtime Dependency

six-1.16.0 (Python 3 module, required at run-time to use GDB scripts from various LFS/BLFS packages with Python 3 installed in LFS)

Optional

Doxygen-1.10.0, GCC-13.2.0 (ada, gfortran, and go are used for tests), Guile-3.0.9, rustc-1.76.0 (used for some tests), Valgrind-3.22.0, and SystemTap (run-time, used for tests)

Installation of GDB

Install GDB by running the following commands:

mkdir build &&
cd    build &&

../configure --prefix=/usr          \
             --with-system-readline \
             --with-python=/usr/bin/python3 &&
make

Optionally, to build the API documentation using Doxygen-1.10.0, run:

make -C gdb/doc doxy

To test the results, issue:

pushd gdb/testsuite &&
make  site.exp      &&
echo  "set gdb_test_timeout 120" >> site.exp &&
runtest
popd

See gdb/testsuite/README and TestingGDB. There are many problems with the test suite:

Clean directories are needed if re-running the tests. For that reason, make a copy of the compiled source code directory before the tests in case you need to run the tests again.
Results depend on installed compilers.
A test run of the test suite had 51 unexpected failures out of the over 106000 tests.
On some systems, the gdb.tui test suite will fail if running over SSH.
On some AMD-based systems, over 200 additional tests may fail due to a difference in the threading implementation on those CPUs.

Now, as the root user:

make -C gdb install &&
make -C gdbserver install

If you have built the API documentation, it is now in gdb/doc/doxy. You can install it (as the root user):

install -d /usr/share/doc/gdb-14.1 &&
rm -rf gdb/doc/doxy/xml &&
cp -Rv gdb/doc/doxy /usr/share/doc/gdb-14.1

Command Explanations

--with-system-readline: This switch forces GDB to use the copy of Readline installed in LFS.

--with-python=/usr/bin/python3: This switch forces GDB to use Python 3.

Installed Programs: gcore, gdb, gdbserver, and gdb-add-index

Installed Library: libinproctrace.so

Installed Directories: /usr/{include,share}/gdb and /usr/share/doc/gdb-14.1

Short Descriptions

gcore	generates a core dump of a running program
gdb	is the GNU Debugger
gdbserver	is a remote server for the GNU debugger (it allows programs to be debugged from a different machine)
gdb-add-index	Allows adding index files to ELF binaries. This speeds up gdb start on large programs.
`libinproctrace.so`	contains functions for the in-process tracing agent. The agent allows for installing fast tracepoints, listing static tracepoint markers, probing static tracepoints markers, and starting trace monitoring.

Git-2.44.0

Introduction to Git

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 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-6.6.3, Bazaar, Subversion-1.14.3, CVS, Perforce, and Team Foundation Server.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://www.kernel.org/pub/software/scm/git/git-2.44.0.tar.xz
Download MD5 sum: 7e4eb7c45e9ba7c90fa51deeea49732f
Download size: 7.1 MB
Estimated disk space required: 307 MB (with downloaded documentation; add 18 MB for building docs)
Estimated build time: 0.3 SBU (with parallelism=4; add 0.4 SBU for building doc, and up to 5 SBU (disk speed dependent) for tests)

Additional Downloads

https://www.kernel.org/pub/software/scm/git/git-manpages-2.44.0.tar.xz (not needed if you've installed asciidoc-10.2.0, xmlto-0.0.28, and prefer to rebuild them)
https://www.kernel.org/pub/software/scm/git/git-htmldocs-2.44.0.tar.xz and other docs (not needed if you've installed asciidoc-10.2.0 and want to rebuild the documentation).

Git Dependencies

Optional

Apache-2.4.58 (for some tests), Fcron-3.2.1 (runtime, for scheduling git maintenance jobs), GnuPG-2.4.4 (runtime, may be used to sign Git commits or tags, or verify the signatures of them), OpenSSH-9.6p1 (runtime, needed to use Git over ssh), pcre2-10.42 (or the deprecated PCRE-8.45), in either case configured with --enable-jit, Subversion-1.14.3 with Perl bindings (runtime, for git svn), Tk-8.6.13 (gitk, a simple Git repository viewer, uses Tk at runtime), Valgrind-3.22.0, Authen::SASL and MIME::Base64 (both runtime, for git send-email), and IO-Socket-SSL-2.085 (runtime, for git send-email to connect to a SMTP server with SSL encryption)

Optional (to create the man pages, html docs and other docs)

xmlto-0.0.28 and asciidoc-10.2.0 , and also dblatex (for the PDF version of the user manual), and docbook2x to create info pages

Installation of Git

Install Git by running the following commands:

./configure --prefix=/usr \
            --with-gitconfig=/etc/gitconfig \
            --with-python=python3 &&
make

You can build the man pages and/or html docs, or use downloaded ones. If you choose to build them, use the next two instructions.

If you have installed asciidoc-10.2.0 you can create the html version of the man pages and other docs:

make html

If you have installed asciidoc-10.2.0 and xmlto-0.0.28 you can create the man pages:

make man

The test suite can be run in parallel mode. To run the test suite, issue: make test -k |& tee test.log. If some test fails, the list of failed tests can be shown via grep '^not ok' test.log | grep -v TODO.

Now, as the root user:

make perllibdir=/usr/lib/perl5/5.38/site_perl install

If you created the man pages and/or html docs

Install the man pages as the root user:

make install-man

Install the html docs as the root user:

make htmldir=/usr/share/doc/git-2.44.0 install-html

If you downloaded the man pages and/or html docs

If you downloaded the man pages untar them as the root user:

tar -xf ../git-manpages-2.44.0.tar.xz \
    -C /usr/share/man --no-same-owner --no-overwrite-dir

If you downloaded the html docs untar them as the root user:

mkdir -vp   /usr/share/doc/git-2.44.0 &&
tar   -xf   ../git-htmldocs-2.44.0.tar.xz \
      -C    /usr/share/doc/git-2.44.0 --no-same-owner --no-overwrite-dir &&

find        /usr/share/doc/git-2.44.0 -type d -exec chmod 755 {} \; &&
find        /usr/share/doc/git-2.44.0 -type f -exec chmod 644 {} \;

Reorganize text and html in the html-docs (both methods)

For both methods, the html-docs include a lot of plain text files. Reorganize the files as the root user:

mkdir -vp /usr/share/doc/git-2.44.0/man-pages/{html,text}         &&
mv        /usr/share/doc/git-2.44.0/{git*.txt,man-pages/text}     &&
mv        /usr/share/doc/git-2.44.0/{git*.,index.,man-pages/}html &&

mkdir -vp /usr/share/doc/git-2.44.0/technical/{html,text}         &&
mv        /usr/share/doc/git-2.44.0/technical/{*.txt,text}        &&
mv        /usr/share/doc/git-2.44.0/technical/{*.,}html           &&

mkdir -vp /usr/share/doc/git-2.44.0/howto/{html,text}             &&
mv        /usr/share/doc/git-2.44.0/howto/{*.txt,text}            &&
mv        /usr/share/doc/git-2.44.0/howto/{*.,}html               &&

sed -i '/^<a href=/s|howto/|&html/|' /usr/share/doc/git-2.44.0/howto-index.html &&
sed -i '/^\* link:/s|howto/|&html/|' /usr/share/doc/git-2.44.0/howto-index.txt

Command Explanations

--with-gitconfig=/etc/gitconfig: This sets /etc/gitconfig as the file that stores 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 git p4 interface to Perforce repositories, and also used in some tests.

--with-libpcre2: Use this switch if PCRE2 is installed and has been built with the non-default JIT enabled.

--with-libpcre1: As an alternative to PCRE2, use this switch if the deprecated PCRE is installed and has been built with the non-default JIT enabled.

tar -xf ../git-manpages-2.44.0.tar.gz -C /usr/share/man --no-same-owner: This untars git-manpages-2.44.0.tar.gz. The -C option makes tar change directory to /usr/share/man before it starts to decompress the docs. The --no-same-owner option stops tar from preserving the user and group details of the files. This is useful as that user or group may not exist on your system; this could (potentially) be a security risk.

mv /usr/share/doc/git-2.44.0 ...: These commands move some of the files into subfolders to make it easier to sort through the docs and find what you're looking for.

find ... chmod ...: These commands correct the permissions in the shipped documentation tar file.

Configuring Git

Config Files

~/.gitconfig and /etc/gitconfig

Installed Programs: git, git-receive-pack, git-upload-archive, and git-upload-pack (hardlinked to each other), git-cvsserver, git-shell, gitk, and scalar

Installed Libraries: None

Installed Directories: /usr/libexec/git-core, /usr/lib/perl5/5.38/site_perl/Git, and /usr/share/{doc/git-2.44.0,git-core,git-gui,gitk,gitweb}

Short Descriptions

git	is the stupid content tracker
git-cvsserver	is a CVS server emulator for Git
gitk	is a graphical Git repository browser (needs Tk-8.6.13)
git-receive-pack	is invoked by git send-pack and updates the repository with the information fed from the remote end
git-shell	is a login shell for SSH accounts to provide restricted Git access
git-upload-archive	is invoked by git archive --remote and sends a generated archive to the other end over the git protocol
git-upload-pack	is invoked by git fetch-pack, it discovers what objects the other side is missing, and sends them after packing
scalar	is a repository management tool that optimizes Git for use in large repositories

Running a Git Server

Introduction

This section will describe how to set up, administer and secure a git server. Git has many options available. For more detailed documentation see https://git-scm.com/book/en/v2.

Server Dependencies

Required

git-2.44.0 and OpenSSH-9.6p1

Setting up a Git Server

The following instructions will install a git server. It will be set up to use OpenSSH as the secure remote access method.

Configuration of the server consists of the following steps:

1. Set Up Users, Groups, and Permissions

You will need to be user root for the initial portion of configuration. Create the git user and group and set and unusable password hash with the following commands:

groupadd -g 58 git &&
useradd -c "git Owner" -d /home/git -m -g git -s /usr/bin/git-shell -u 58 git &&
sed -i '/^git:/s/^git:[^:]:/git:NP:/' /etc/shadow

Putting in an unusable password hash (replacing the ! by NP) unlocks the account but it cannot be used to login via password authentication. That is required by sshd to work properly. Next, create some files and directories in the home directory of the git user allowing access to the git repository using ssh keys.

install -o git -g git -dm0700 /home/git/.ssh &&
install -o git -g git -m0600 /dev/null /home/git/.ssh/authorized_keys

For any developer who should have access to the repository add his/her public ssh key to /home/git/.ssh/authorized_keys. First, prepend some options to prevent users from using the connection to git for port forwarding to other machines the git server might reach.

echo -n "no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty " >> /home/git/.ssh/authorized_keys &&
cat <user-ssh-key> >> /home/git/.ssh/authorized_keys

It is also useful to set the default name of the initial branch of new repositories by modifying the git configuration. As the root user, run:

git config --system init.defaultBranch trunk

Finally add the /usr/bin/git-shell entry to the /etc/shells configuration file. This shell has been set in the git user profile and is to make sure that only git related actions can be executed:

echo "/usr/bin/git-shell" >> /etc/shells

2. Create a git repository

The repository can be anywhere on the filesystem. It is important that the git user has read/write access to that location. We use /srv/git as base directory. Create a new git repository with the following commands (as the root user):

Note

In all the instructions below, we use project1 as an example repository name. You should name your repository as a short descriptive name for your specific project.

install -o git -g git -m755 -d /srv/git/project1.git &&
cd /srv/git/project1.git                             &&
git init --bare                                      &&
chown -R git:git .

3. Populate the repository from a client system

Note

All the instructions in this section and the next should be done on a user system, not the server system.

Now that the repository is created, it can be used by the developers to put some files into it. Once the ssh key of the user is imported to git's authorized_keys file, the user can interact with the repository.

A minimal configuration should be available on the developer's system specifying its user name and the email address. Create this minimal config file on client side:

cat > ~/.gitconfig <<EOF
[user]
        name = <users-name>
        email = <users-email-address>
EOF

On the developer's machine, set up some files to be pushed to the repository as the initial content:

Note

The gitserver term used below should be the host name (or ip address) of the git server.

mkdir myproject
cd myproject
git init --initial-branch=trunk
git remote add origin git@gitserver:/srv/git/project1.git
cat >README <<EOF
This is the README file
EOF
git add README
git commit -m 'Initial creation of README'
git push --set-upstream origin trunk

The initial content is now pushed to the server and is available for other users. On the current machine, the argument --set-upstream origin trunk is now no longer required as the local repository is now connected to the remote repository. Subsequent pushes can be performed as

git push

Other developers can now clone the repository and do modifications to the content (as long as their ssh keys has been installed):

git clone git@gitserver:/srv/git/project1.git
cd project1
vi README
git commit -am 'Fix for README file'
git push

Note

This is a very basic server setup based on OpenSSH access. All developers are using the git user to perform actions on the repository and the changes users are committing can be distinguished as the local user name (see ~/.gitconfig) is recorded in the changesets.

Access is restricted by the public keys added to git's authorized_keys file and there is no option for the public to export/clone the repository. To enable this, continue with step 4 to set up the git server for public read-only access.

In the URL used to clone the project, the absolute path (here /srv/git/project1.git) has to be specified as the repository is not in git's home directory but in /srv/git. To get rid of the need to expose the structure of the server installation, a symlink can be added in git's home directory for each project like this:

ln -svf /srv/git/project1.git /home/git/

Now, the repository can be cloned using

git clone git@gitserver:project1.git

4. Configure the Server

The setup described above makes a repository available for authenticated users (via providing the ssh public key file). There is also a simple way to publish the repository to unauthenticated users — of course without write access.

The combination of access via ssh (for authenticated users) and the export of repositories to unauthenticated users via the daemon is in most cases enough for a development site.

Note

The daemon will be reachable at port 9418 by default. Make sure that your firewall setup allows access to that port.

To start the server at boot time, install the git-daemon bootscript included in the blfs-bootscripts-20240209 package:

make install-git-daemon

In order to allow git to export a repository, a file named git-daemon-export-ok is required in each repository directory on the server. The file needs no content, just its existence enables, its absence disables the export of that repository.

touch /srv/git/project1.git/git-daemon-export-ok

The script to start the git daemon uses some default values internally. Most important is the path to the repository directory which is set to /srv/git. In case you have for whatever reason created the repository in a different location, you'll need to tell the boot script where the repository is to be found. This can be achieved by creating a configuration file named /etc/sysconfig/git-daemon. This configuration file will be imported if it exists, meaning it is optional. The file can look like:

# Begin /etc/sysconfig/git-daemon

# Specify the location of the git repository
GIT_BASE_DIR="/srv/git/"

# Directories added to whitelist
DFT_REPO_DIR="$GIT_BASE_DIR"

# Add extra options which will appended to the 'git daemon'
# command executed in the boot script
GIT_DAEMON_OPTS=""

# End /etc/sysconfig/git-daemon

There are only three options to set in the configuration file:

GIT_BASE_DIR=<dirname>

Specify the location of the git repositories. Relative paths used when accessing the daemon will translated relative to this directory.
DFT_REPO_DIR=<dirname>

This directory is added to the white list of allowed directories. This variable can hold multiple directory names but is usually set equal to GIT_BASE_DIR.
GIT_DAEMON_OPTS=<options>

In case special options to the git daemon command are needed, they have to be specified in this setting. One example might be to adjust the port number where daemon is listening. In this case, add --port=<port number> to this variable. For more information about which options can be set, take a look at the output of git daemon --help.

After starting the daemon, unauthenticated users can clone exported repositories by using

git clone git://gitserver/project1.git

As the base directory is /srv/git by default (or set to a custom value in the configuration), git interprets the incoming path (/project1.git) relative to that base directory so that the repository in /srv/git/project1.git is served.

Guile-3.0.9

Introduction to Guile

The Guile package contains the GNU Project's extension language library. Guile also contains a stand alone Scheme interpreter.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://ftp.gnu.org/gnu/guile/guile-3.0.9.tar.xz
Download MD5 sum: 258983e0156c2bc66539dcbcb96f2bd2
Download size: 5.5 MB
Estimated disk space required: 221 MB (add 4 MB for tests)
Estimated build time: 5.9 SBU (Using parallelism=4; add 0.3 SBU for tests)

Guile Dependencies

Required

GC-8.2.6 and libunistring-1.1

Optional

Emacs-29.2 and GDB-14.1 (run-time only dependencies).

Installation of Guile

Install Guile by running the following commands:

./configure --prefix=/usr    \
            --disable-static \
            --docdir=/usr/share/doc/guile-3.0.9 &&
make      &&
make html &&

makeinfo --plaintext -o doc/r5rs/r5rs.txt doc/r5rs/r5rs.texi &&
makeinfo --plaintext -o doc/ref/guile.txt doc/ref/guile.texi

To test the results, issue: ./check-guile. On an i686 system, as many as 10 tests will fail in the numbers.test test suite due to minor floating-point rounding errors.

Now, as the root user:

make install      &&
make install-html &&

mkdir -p                       /usr/share/gdb/auto-load/usr/lib &&
mv /usr/lib/libguile-*-gdb.scm /usr/share/gdb/auto-load/usr/lib &&
mv /usr/share/doc/guile-3.0.9/{guile.html,ref} &&
mv /usr/share/doc/guile-3.0.9/r5rs{.html,}     &&

find examples -name "Makefile*" -delete         &&
cp -vR examples   /usr/share/doc/guile-3.0.9   &&

for DIRNAME in r5rs ref; do
  install -v -m644  doc/${DIRNAME}/*.txt \
                    /usr/share/doc/guile-3.0.9/${DIRNAME}
done &&
unset DIRNAME

Command Explanations

--disable-static: This switch prevents installation of static versions of the libraries.

Installed Programs: guild, guile, guile-config, guile-snarf and guile-tools

Installed Libraries: libguile-3.0.so and guile-readline.so

Installed Directories: /usr/include/guile, /usr/lib/guile, /usr/share/doc/guile-3.0.9 and /usr/share/guile

Short Descriptions

guile	is a stand-alone Scheme interpreter for Guile
guile-config	is a Guile script which provides the information necessary to link your programs against the Guile library, in much the same way PkgConfig does
guile-snarf	is a script to parse declarations in your C code for Scheme visible C functions
guild	is a wrapper program installed along with guile, which knows where a particular module is installed and calls it, passing its arguments to the program
guile-tools	is a symlink to guild

LLVM-17.0.6

Introduction to LLVM

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 popular CPUs (as well as some less common ones!). These libraries are built around a well specified code representation known as the LLVM intermediate representation ("LLVM IR").

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 rust if that is built using the system LLVM.

The Compiler RT package provides runtime sanitizer and profiling libraries for developers who use Clang and LLVM.

This package is known to build and work properly using an LFS 12.1 platform.

Package Information

Download (HTTP): https://github.com/llvm/llvm-project/releases/download/llvmorg-17.0.6/llvm-17.0.6.src.tar.xz
Download MD5 sum: fd7fc891907e14f8e0ff7e3f87cc89a4
Download size: 57 MB
Estimated disk space required: 4.2 GB (964 MB installed; add 20 GB for tests and 308 MB for documentation)
Estimated build time: 13 SBU (Add 8 SBU for tests; both using parallelism=8)

Additional Downloads

Cmake modules for LLVM

Download: https://anduin.linuxfromscratch.org/BLFS/llvm/llvm-cmake-17.src.tar.xz
Download MD5 sum: 2b75b6446bfd5d0dcc288cd412b6a52a
Download size: 12 KB

Third-party dependencies for LLVM build system

Download: https://anduin.linuxfromscratch.org/BLFS/llvm/llvm-third-party-17.src.tar.xz
Download MD5 sum: 09c9f2259766dd65b75cd728df11b395
Download size: 376 KB

Recommended Download

Clang

Download: https://github.com/llvm/llvm-project/releases/download/llvmorg-17.0.6/clang-17.0.6.src.tar.xz
Download MD5 sum: 52ff9f49e064860445474aa21e4a7e40
Download size: 21 MB

Patch enabling SSP by default in clang: https://www.linuxfromscratch.org/patches/blfs/12.1/clang-17-enable_default_ssp-1.patch

Optional Download

Compiler RT

Download: https://github.com/llvm/llvm-project/releases/download/llvmorg-17.0.6/compiler-rt-17.0.6.src.tar.xz
Download MD5 sum: 85d25f04cbc4c1a20e3a1ab2a2c522cd
Download size: 2.4 MB

LLVM Dependencies

Required