Details on this package are located in Section 10.36.2, “Contents of Bc.”
Copyright © 2005–2013 Joe Ciccone, Jim Gifford & Ryan Oliver
Copyright © 2005-2013, Joe Ciccone, Jim Gifford, & Ryan Oliver
All rights reserved.
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Linux® is a registered trademark of Linus Torvalds.
This book is based on the "Linux From Scratch" book, that was released under the following license:
Copyright © 1999–2013, Gerard Beekmans
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions in any form must retain the above copyright notice, this list of conditions and the following disclaimer
Neither the name of “Linux From Scratch” nor the names of its contributors may be used to endorse or promote products derived from this material without specific prior written permission
Any material derived from Linux From Scratch must contain a reference to the “Linux From Scratch” project
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Linux From Scratch Project has seen many changes in the few years of its existence. I personally became involved with the project in 1999, around the time of the 2.x releases. At that time, the build process was to create static binaries with the host system, then chroot and build the final binaries on top of the static ones.
Later came the use of the /static directory to hold the initial static builds, keeping them separated from the final system, then the PureLFS process developed by Ryan Oliver and Greg Schafer, introducing a new toolchain build process that divorces even our initial builds from the host. Finally, LFS 6 brought Linux Kernel 2.6, the udev dynamic device structure, sanitized kernel headers, and other improvements to the Linux From Scratch system.
The one "flaw" in LFS is that it has always been based on an x86 class processor. With the advent of the Athlon 64 and Intel EM64T processors, the x86-only LFS is no longer ideal. Throughout this time, Ryan Oliver developed and documented a process by which you could build Linux for any system and from any system, by use of cross-compilation techniques. Thus, the Cross-Compiled LFS (CLFS) was born.
CLFS follows the same guiding principles the LFS project has always followed, e.g., knowing your system inside and out by virtue of having built the system yourself. Additionally, during a CLFS build, you will learn advanced techniques such as cross-build toolchains, multilib support (32 & 64-bit libraries side-by-side), alternative architectures such as Sparc, MIPS, and Alpha, and much more.
We hope you enjoy building your own CLFS system, and the benefits that come from a system tailored to your needs.
--
Jeremy Utley, CLFS 1.x Release Manager (Page Author)
Jonathan Norman, Release Manager
Jim Gifford, CLFS Project Co-leader
Ryan Oliver, CLFS Project Co-leader
Joe Ciccone, CLFS Project Co-leader
Jonathan Norman, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat,
Manuel Canales Esparcia, Nathan Coulson and William Harrington - CLFS Developers
There are many reasons why somebody would want to read this book. The principal reason is to install a Linux system from the source code. A question many people raise is, “why go through all the hassle of manually building a Linux system from scratch when you can just download and install an existing one?” That is a good question and is the impetus for this section of the book.
One important reason for the existence of CLFS is to help people understand how a Linux system works. Building an CLFS system helps demonstrate what makes Linux tick, and how things work together and depend on each other. One of the best things this learning experience provides is the ability to customize Linux to your own tastes and needs.
A key benefit of CLFS is that it allows users to have more control over their system without any reliance on a Linux implementation designed by someone else. With CLFS, you are in the driver's seat and dictate every aspect of the system, such as the directory layout and bootscript setup. You also dictate where, why, and how programs are installed.
Another benefit of CLFS is the ability to create a very compact Linux system. When installing a regular distribution, one is often forced to include several programs which are probably never used. These programs waste disk space or CPU cycles. It is not difficult to build an CLFS system of less than 100 megabytes (MB), which is substantially smaller than the majority of existing installations. Does this still sound like a lot of space? A few of us have been working on creating a very small embedded CLFS system. We successfully built a system that was specialized to run the Apache web server with approximately 8MB of disk space used. Further stripping could bring this down to 5 MB or less. Try that with a regular distribution! This is only one of the many benefits of designing your own Linux implementation.
We could compare Linux distributions to a hamburger purchased at a fast-food restaurant—you have no idea what might be in what you are eating. CLFS, on the other hand, does not give you a hamburger. Rather, CLFS provides the recipe to make the exact hamburger desired. This allows users to review the recipe, omit unwanted ingredients, and add your own ingredients to enhance the flavor of the burger. When you are satisfied with the recipe, move on to preparing it. It can be made to exact specifications—broil it, bake it, deep-fry it, or barbecue it.
Another analogy that we can use is that of comparing CLFS with a finished house. CLFS provides the skeletal plan of a house, but it is up to you to build it. CLFS maintains the freedom to adjust plans throughout the process, customizing it to the needs and preferences of the user.
Security is an additional advantage of a custom built Linux system. By compiling the entire system from source code, you are empowered to audit everything and apply all the security patches desired. It is no longer necessary to wait for somebody else to compile binary packages that fix a security hole. Unless you examine the patch and implement it yourself, you have no guarantee that the new binary package was built correctly and adequately fixes the problem.
The goal of Cross Linux From Scratch is to build a complete and usable foundation-level system. Readers who do not wish to build their own Linux system from scratch may not benefit from the information in this book. If you only want to know what happens while the computer boots, we recommend the “From Power Up To Bash Prompt” HOWTO located at http://axiom.anu.edu.au/~okeefe/p2b/ or on The Linux Documentation Project's (TLDP) website at http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html. The HOWTO builds a system which is similar to that of this book, but it focuses strictly on creating a system capable of booting to a BASH prompt. Consider your objective. If you wish to build a Linux system and learn along the way, this book is your best choice.
There are too many good reasons to build your own CLFS system to list them all here. This section is only the tip of the iceberg. As you continue in your CLFS experience, you will find the power that information and knowledge truly bring.
Building a CLFS system is not a simple task. It requires a certain level of existing knowledge of Unix system administration in order to resolve problems, and correctly execute the commands listed. In particular, as an absolute minimum, the reader should already have the ability to use the command line (shell) to copy or move files and directories, list directory and file contents, and change the current directory. It is also expected that the reader has a reasonable knowledge of using and installing Linux software. A basic knowledge of the architectures being used in the Cross LFS process and the host operating systems in use is also required.
Because the CLFS book assumes at least this basic level of skill, the various CLFS support forums are unlikely to be able to provide you with much assistance. Your questions regarding such basic knowledge will likely go unanswered, or you will be referred to the CLFS essential pre-reading list.
Before building a CLFS system, we recommend reading the following HOWTOs:
Software-Building-HOWTO http://www.tldp.org/HOWTO/Software-Building-HOWTO.html
This is a comprehensive guide to building and installing “generic” Unix software distributions under Linux.
The Linux Users' Guide http://www.linuxhq.com/guides/LUG/guide.html
This guide covers the usage of assorted Linux software.
The Essential Pre-Reading Hint http://hints.cross-lfs.org/index.php/Essential_Prereading
This is a hint written specifically for users new to Linux. It includes a list of links to excellent sources of information on a wide range of topics. Anyone attempting to install CLFS should have an understanding of many of the topics in this hint.
You should be able to build a CLFS system from just about any Unix-type operating system. Your host system should have the following software with the minimum versions indicated. Also note that many distributions will place software headers into separate packages, often in the form of “[package-name]-devel” or “[package-name]-dev”. Be sure to install those if your distribution provides them.
Bash-2.05a
Binutils-2.12 (Versions greater than 2.23.2 are not recommended as they have not been tested)
Bison-1.875
Bzip2-1.0.2
Coreutils-5.0
Diffutils-2.8
Findutils-4.1.20
Gawk-3.1.5
GCC-4.1.2 and the C++ compiler, g++ (Versions greater than 4.8.1 are not recommended as they have not been tested)
Glibc-2.2.5 (Versions greater than 2.18 are not recommended as they have not been tested)
Grep-2.5
Gzip-1.2.4
Linux 2.6.32 (Built with GCC 4.1.2 or later)
Make-3.80
Ncurses-5.3
Patch-2.5.4
Sed-3.0.2
Tar-1.22
Texinfo-4.7
XZ-Utils-4.999.8beta
To see whether your host system has all the appropriate versions, create and run the following script. Read the output carefully for any errors, and make sure to install any packages that are reported as not found.
cat > version-check.sh << "EOF"
#!/bin/bash
# Simple script to list version numbers of critical development tools
bash --version | head -n1 | cut -d" " -f2-4
echo -n "Binutils: "; ld --version | head -n1 | cut -d" " -f3-
bison --version | head -n1
bzip2 --version 2>&1 < /dev/null | head -n1 | cut -d" " -f1,6-
echo -n "Coreutils: "; chown --version | head -n1 | cut -d")" -f2
diff --version | head -n1
find --version | head -n1
gawk --version | head -n1
gcc --version | head -n1
g++ --version | head -n1
ldd $(which ${SHELL}) | grep libc.so | cut -d ' ' -f 3 | ${SHELL} | head -n 1 | cut -d ' ' -f 1-7
grep --version | head -n1
gzip --version | head -n1
uname -s -r
make --version | head -n1
tic -V
patch --version | head -n1
sed --version | head -n1
tar --version | head -n1
makeinfo --version | head -n1
xz --version | head -n1
echo 'main(){}' | gcc -v -o /dev/null -x c - > dummy.log 2>&1
if ! grep -q ' error' dummy.log; then
echo "Compilation successful" && rm dummy.log
else
echo 1>&2 "Compilation FAILED - more development packages may need to be \
installed. If you like, you can also view dummy.log for more details."
fi
EOF
bash version-check.sh 2>errors.log &&
[ -s errors.log ] && echo -e "\nThe following packages could not be found:\n$(cat errors.log)"
To make things easier to follow, there are a few typographical conventions used throughout this book. This section contains some examples of the typographical format found throughout Cross-Compiled Linux From Scratch.
./configure --prefix=/usr
This form of text is designed to be typed exactly as seen unless otherwise noted in the surrounding text. It is also used in the explanation sections to identify which of the commands is being referenced.
install-info: unknown option '--dir-file=/mnt/clfs/usr/info/dir'
This form of text (fixed-width text) shows screen output,
probably as the result of commands issued. This format is also
used to show filenames, such as /etc/ld.so.conf
.
Emphasis
This form of text is used for several purposes in the book. Its main purpose is to emphasize important points or items.
This format is used for hyperlinks, both within the CLFS community and to external pages. It includes HOWTOs, download locations, and websites.
cat > ${CLFS}/etc/group << "EOF"
root:x:0:
bin:x:1:
......
EOF
This format is used when creating configuration files. The first
command tells the system to create the file ${CLFS}/etc/group
from whatever is typed on the
following lines until the sequence end of file (EOF) is
encountered. Therefore, this entire section is generally typed as
seen.
[REPLACED TEXT]
This format is used to encapsulate text that is not to be typed as seen or copied-and-pasted.
passwd(5)
This format is used to refer to a specific manual page
(hereinafter referred to simply as a “man” page). The number inside parentheses
indicates a specific section inside of man. For example, passwd has two man pages. Per
CLFS installation instructions, those two man pages will be
located at /usr/share/man/man1/passwd.1
and /usr/share/man/man5/passwd.5
. Both man pages
have different information in them. When the book uses
passwd(5)
it is specifically
referring to /usr/share/man/man5/passwd.5
. man passwd will print the first
man page it finds that matches “passwd”, which will be /usr/share/man/man1/passwd.1
. For this example,
you will need to run man 5
passwd in order to read the specific page being
referred to. It should be noted that most man pages do not have
duplicate page names in different sections. Therefore,
man [program name]
is
generally sufficient.
This book is divided into the following parts.
Part I explains a few important notes on how to proceed with the Cross-LFS installation. This section also provides meta-information about the book.
Part II describes how to prepare for the building process—making a partition and downloading the packages.
Part III shows you how to make a set of Cross-Compiler tools. These tools can run on your host system but allow you to build packages that will run on your target system.
Part IV explains how to build a tool chain designed to operate on your target system. These are the tools that will allow you to build a working system on your target computer.
Part V guides the reader through the building of the CLFS system—compiling and installing all the packages one by one, setting up the boot scripts, and installing the kernel. The resulting Linux system is the foundation on which other software can be built to expand the system as desired. At the end of this book, there is an easy to use reference listing all of the programs, libraries, and important files that have been installed.
The appendices contain information that doesn't really fit anywhere else in the book. Appendix A contains definitions of acronyms and terms used in the book; Appendices B and C have information about package dependencies and the build order. Some architectures may have additional appendices for arch-specific issues.
The software used to create a CLFS system is constantly being updated and enhanced. Security warnings and bug fixes may become available after the CLFS book has been released. Some host systems may also have problems building CLFS. To check whether the package versions or instructions in this release of CLFS need any modifications to accommodate security vulnerabilities, other bug fixes, or host-specific issues, please visit http://trac.cross-lfs.org/wiki/errata before proceeding with your build. You should note any changes shown and apply them to the relevant section of the book as you progress with building the CLFS system.
The CLFS team would like to acknowledge people who have assisted in making the book what it is today.
Our Leaders:
Ryan Oliver - Build Process Developer.
Jim Gifford - Lead Developer.
Joe Ciccone - Lead Developer.
Jeremy Utley - Release Manager 1.x Series.
Our CLFS Team:
Nathan Coulson - Bootscripts.
Matt Darcy - x86, X86_64, and Sparc builds.
Manuel Canales Esparcia - Book XML.
Karen McGuiness - Proofreader.
Jonathan Norman - x86, x86_64, PowerPC & UltraSPARC.
Jeremy Huntwork - PowerPC, x86, Sparc builds.
Justin Knierim - Website Architect.
Ken Moffat - PowerPC and X86_64 builds. Developer of Pure 64 Hint.
Alexander E. Patrakov - Udev/Hotplug Integration
Chris Staub - x86 builds. Leader of Quality Control.
Zack Winkles - Unstable book work.
William Harrington - x86, x86_64, PowerPC, Sparc, Mips builds.
Outside the Development Team
Jürg Billeter - Testing and assisting in the development of the Linux Headers Package
Richard Downing - Testing, typo, and content fixes.
Peter Ennis - Typo and content fixes.
Tony Morgan - Typo and content fixes.
The CLFS team would also like to acknowledge contributions of people from clfs-dev@lists.cross-lfs.org and associated mailing lists who have provided valuable technical and editorial corrections while testing the Cross-LFS book.
G. Moko - Text updates and Typos
Maxim Osipov - MIPS Testing.
Doug Ronne - Various x86_64 fixes.
William Zhou - Text updates and Typos
Theo Schneider - Testing of the Linux Headers Package
The Linux From Scratch Project
Gerard Beekmans <gerard AT linuxfromscratch D0T org> – Creator of Linux From Scratch, on which Cross-LFS is based
Thank you all for your support.
The CLFS system will be built by using a previously installed Unix system or Linux distribution (such as Debian, Fedora, Mandriva, SUSE, or Ubuntu). This existing system (the host) will be used as a starting point to provide necessary programs, including a compiler, linker, and shell, to build the new system. Select the “development” option during the distribution installation to be able to access these tools.
As an alternative to installing an entire separate distribution onto your machine, you may wish to use a livecd. Most distributions provide a livecd, which provides an environment to which you can add the required tools onto, allowing you to successfully follow the instructions in this book. Remember that if you reboot the livecd you will need to reconfigure the host environment before continuing with your build.
Preparing a New Partition of this book describes how to create a new Linux native partition and file system, the place where the new CLFS system will be compiled and installed. Packages and Patches explains which packages and patches need to be downloaded to build a CLFS system and how to store them on the new file system. Final Preparations discusses the setup for an appropriate working environment. Please read Final Preparations carefully as it explains several important issues the developer should be aware of before beginning to work through Constructing Cross-Compile Tools and beyond.
Constructing Cross-Compile Tools explains the installation of cross-compile tools which will be built on the host but be able to compile programs that run on the target machine. These cross-compile tools will be used to create a temporary, minimal system that will be the basis for building the final CLFS system. Some of these packages are needed to resolve circular dependencies—for example, to compile a compiler, you need a compiler.
The process of building cross-compile tools first involves building and installing all the necessary tools to create a build system for the target machine. With these cross-compiled tools, we eliminate any dependencies on the toolchain from our host distro.
After we build our “Cross-Tools”, we start building a very minimal working system in /tools. This minimal system will be built using the cross-toolchain in /cross-tools.
In Installing Basic System Software, the full CLFS system is built. Depending on the system you are cross-compiling for, you will either boot the minimal temp-system on the target machine, or chroot into it.
The chroot (change root) program is used to enter a virtual environment and start a new shell whose root directory will be set to the CLFS partition. This is very similar to rebooting and instructing the kernel to mount the CLFS partition as the root partition. The major advantage is that “chrooting” allows the builder to continue using the host while CLFS is being built. While waiting for package compilation to complete, a user can switch to a different virtual console (VC) or X desktop and continue using the computer as normal.
Some systems cannot be built by chrooting so they must be booted instead. Generally, if you building for a different arch than the host system, you must reboot because the kernel will likely not support the target machine. Booting involves installing a few additional packages that are needed for bootup, installing bootscripts, and building a miminal kernel. We also describe some alternative booting methods in Section 7.18, “What to do next”
To finish the installation, the CLFS-Bootscripts are set up in Setting Up System Bootscripts, and the kernel and boot loader are set up in Making the CLFS System Bootable. The End contains information on furthering the CLFS experience beyond this book. After the steps in this book have been implemented, the computer will be ready to reboot into the new CLFS system.
This is the process in a nutshell. Detailed information on each step is discussed in the following chapters and package descriptions. Items that may seem complicated will be clarified, and everything will fall into place as the reader embarks on the CLFS adventure.
This is version 2.1.0 of the Cross-Compiled Linux From Scratch book, dated October 06, 2013. If this book is more than six months old, a newer and better version is probably already available. To find out, please check one of the mirrors via http://trac.cross-lfs.org/.
Below is a list of detailed changes made since the previous release of the book.
Changelog Entries:
06 October 2013
[William Harrington] - Fix shm umount during end section reboot.
24 September 2013
[William Harrington] - Update File to 5.15.
23 September 2013
[William Harrington] - Update M4 to 1.4.17.
[William Harrington] - Update EUDEV to 1.3.
[William Harrington] - Update DHCPCD to 6.1.0.
[William Harrington] - Update TCL to 8.6.1.
[William Harrington] - Update Man-pages to 3.54.
19 September 2013
[William Harrington] - Remove pt_chown entries from book.
09 September 2013
[William Harrington] - Increase the stack size during the GCC testsuite.
08 September 2013
[William Harrington] - Change GID of tty to 5 and tape to 4.
03 September 2013
[William Harrington] - Fix final system EUDEV installation.
30 August 2013
[William Harrington] - Move GDB python files auto-load directory.
28 August 2013
[William Harrington] - Add GCC 4.8.1 branch update patch.
23 August 2013
[William Harrington] - Update KMOD to 15.
[William Harrington] - Update KBD to 2.0.0.
[William Harrington] - Add Check to test-suite tools.
22 August 2013
[William Harrington] - Install firmware option during boot method.
[William Harrington] - Add rule to Eudev installs for proper ethernet device naming.
21 August 2013
[William Harrington] - Update EGLIBC to 2.18-r23806.
[William Harrington] - Update Linux to 3.10.9.
19 August 2013
[William Harrington] - Add missing make mrproper to final-system linux headers install.
[William Harrington] - Add M4=m4 to temp system configure commands of Bison and Flex as M4 is hardcoded to /cross-tools.
16 August 2013
[William Harrington] - Update Gettext to 0.18.3.1.
[William Harrington] - Update Bison to 3.0.
15 August 2013
[William Harrington] - Fix shm mount during chroot virtual kernel filesystems.
14 August 2013
[William Harrington] - Add --noclear to
inittab
.
[William Harrington] - Disable fixincludes for GCC in temp and final systems.
[William Harrington] - Update Perl to 5.18.1.
12 August 2013
[William Harrington] - Add ac_cv_prog_lex_is_flex=yes to temp-system and final-system Bison.
[William Harrington] - Update Vim to Vim 7.4.
[William Harrington] - Fix temp system GCC for HOST gmp isl and cloog libraries and headers.
08 August 2013
[William Harrington] - Migrate to Eudev.
[William Harrington] - Update Bootscripts for Eudev.
07 August 2013
[William Harrington] - Update Dhcpcd to 6.0.5.
06 August 2013
[William Harrington] - Update LESS to 460.
[William Harrington] - Update IPutils to s20121221.
[William Harrington] - Disable Vlock in KBD as it requires PAM.
[William Harrington] - Update Libestr to 0.1.5.
[William Harrington] - Update Rsyslog to 6.4.2.
05 August 2013
[William Harrington] - Remove --enable-arch from final-system Util-Linux as it is no longer used.
[William Harrington] - Update Bash patch to upstream version 4.2-045.
04 August 2013
[William Harrington] - Update Vim updates to last 1314 patch level.
[William Harrington] - Update boot method KMOD to support xz and zlib.
[William Harrington] - Remove unneeded config cache entry for c_cv_func_setpgrp_void during boot method shadow cross compilation.
[William Harrington] - Update EGLIBC 2.17 to Revision 23679.
[William Harrington] - Remove mpbsd configure option from final-system GMP.
02 August 2013
[William Harrington] - Add GMP, MPFR, MPC, ISL, CLooG configure options to temp system GCC configure.
01 August 2013
[William Harrington] - Update Util-Linux to 2.23.2.
[William Harrington] - Update Man-Pages to 3.53.
[William Harrington] - Update ISL to 0.12.1.
[William Harrington] - Add Make-3.82 fixes patch.
30 July 2013
[William Harrington] - Remove unneeded --disable-cloog-version-check from all gcc configure commands.
30 July 2013
[William Harrington] - Remove unneeded commands from linux header installation commands and adjust INSTALL_HDR_PATH variable.
29 July 2013
[William Harrington] - Enable graphite for cross-tools toolchain.
[William Harrington] - Remove unnecessary sed for headers and libraries for graphite.
27 July 2013
[William Harrington] - Add MD5SUMS and SHA1SUMS to packages introduction.
[William Harrington] - Add wget example to packages introduction.
25 July 2013
[William Harrington] - Add sed to cross-tools and temp-system binutils for hosts using Texinfo 5.x.
23 July 2013
[William Harrington] - Add Bc to cross-tools and final-system.
[William Harrington] - Update Linux kernel version to 3.10.2.
[William Harrington] - Update IPRoute2 to 3.10.0.
22 July 2013
[William Harrington] - Update KBD to 1.15.5.
[William Harrington] - Remove unneeded KBD es_po patch.
09 July 2013
[William Harrington] - Update Gettext to 0.18.3.
[William Harrington] - Remove unneeded config.cache command for Temp System Patch.
08 July 2013
[William Harrington] - Remove unneeded entries to cross-tools EGLIBC config.cache and change description.
[William Harrington] - Remove unneeded inst_vardbdir install option for current EGLIBC.
07 July 2013
[William Harrington] - Update TZData to 2013d.
06 July 2013
[William Harrington] - Update Man-Pages to 3.52.
03 July 2013
[William Harrington] - Update KMOD to 14.
25 June 2013
[William Harrington] - Add ISL 0.12 to the book.
24 June 2013
[William Harrington] - Updated Gzip to 1.6.
[William Harrington] - Update E2fsprogs to 1.42.8.
07 June 2013
[William Harrington] - Add a sed to Tar-1.26 installs as gets() is no longer declared with Glibc-2.17.
[William Harrington] - Update Vim branch update patch to level 1140.
05 June 2013
[William Harrington] - Update Eglibc to 2.17.
[William Harrington] - Remove Eglibc fixes patch.
[William Harrington] - Add TZ Data to final systme Eglibc install.
03 June 2013
[William Harrington] - Update Iproute2 to 3.8.0.
[William Harrington] - Update GCC to 4.8.1.
[William Harrington] - Update CLooG to 0.18.0.
[William Harrington] - Remove PPL.
[William Harrington] - Remove -fexceptions from GMP builds.
[William Harrington] - Update CLooG build instructions.
02 June 2013
[William Harrington] - Add a sed for temp-system Gawk extension error.
31 May 2013
[William Harrington] - Update Coreutils to 8.21.
[William Harrington] - Update Bison to 2.7.1.
[William Harrington] - Update Util-linux to 2.23.1.
[William Harrington] - Expand tcl space for regular expressions required by some tests.
28 May 2013
[William Harrington] - Update File to 5.14.
27 May 2013
[William Harrington] - Update Zlib to 1.2.8.
[William Harrington] - Add g++ to host reqs test script.
[William Harrington] - Update MPFR to 3.1.2.
[William Harrington] - Update GMP to 5.1.2.
[William Harrington] - Update Binutils to 2.23.2.
[William Harrington] - Update DejaGNU to 1.5.1.
[William Harrington] - Update Diffutils to 3.3.
[William Harrington] - Update E2fsprogs to 1.42.7.
[William Harrington] - Update Gawk to 4.1.0.
[William Harrington] - Update GMP to 5.1.2.
[William Harrington] - Update Gettext to 0.18.2.1.
[William Harrington] - Update Groff to 1.22.2.
[William Harrington] - Update KMOD to 13.
[William Harrington] - Update Less to 459.
[William Harrington] - Update Linux to 3.8.13.
[William Harrington] - Man-Pages to 3.51.
[William Harrington] - Update Perl to 5.18.0.
[William Harrington] - Update Pkg-Config-Lite to 0.28-1.
[William Harrington] - Update Sed to 4.2.2.
[William Harrington] - Update TCL to 8.6.0.
24 April 2013
[William Harrington] - Changelog restarted, see the 2.0.0 book for the old changelog.
Below is a list of changes specifics for this architecture made since the previous release of the book. For general changes see Master Changelog,
Changelog Entries:
28 July 2013
[William Harrington] - Add -O2 to default optimizations.
12 July 2013
[William Harrington] - Adjust EGLIBC CFLAGS to use default optimizations.
24 April 2013
[William Harrington] - Changelog restarted, see the 2.0.0 book for the old changelog.
If during the building of the CLFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the Frequently Asked Questions (FAQ) that is located at http://trac.cross-lfs.org/wiki/faq.
The cross-lfs.org
server hosts a
number of mailing lists used for the development of the CLFS
project. These lists include the main development and support
lists, among others. If the FAQ does not contain your answer,
you can search the CLFS lists via The Mail Archive http://www.mail-archive.com.
You can find the mail lists with the following link:
http://www.mail-archive.com/index.php?hunt=clfs
For information on the different lists, how to subscribe, archive locations, and additional information, visit http://trac.cross-lfs.org/wiki/lists.
Cross-LFS does not maintain its own News Server, but we do
provide access via gmane.org
http://gmane.org. If you want to
subscribe to the Cross-LFS lists via a newsreader you can
utilize gmane.org
. You can find the
gmane search for CLFS with the following link:
Several members of the CLFS community offer assistance on our
community Internet Relay Chat (IRC) network. Before using
this support, please make sure that your question is not
already answered in the CLFS FAQ or the mailing list
archives. You can find the IRC network at chat.freenode.net
. The support channel for
cross-lfs is named #cross-lfs. If you need to show people the
output of your problems, please use
http://pastebin.cross-lfs.org and reference the pastebin URL
when asking your questions.
The CLFS project has a number of world-wide mirrors to make accessing the website and downloading the required packages more convenient. Please visit the CLFS website at http://trac.cross-lfs.org/wiki/mirrors for mirrors of CLFS.
If an issue or a question is encountered while working through this book, check the FAQ page at http://trac.cross-lfs.org/wiki/faq#generalfaq. Questions are often already answered there. If your question is not answered on this page, try to find the source of the problem. The following hint will give you some guidance for troubleshooting: http://hints.cross-lfs.org/index.php/Errors.
We also have a wonderful CLFS community that is willing to offer assistance through the mailing lists and IRC (see the Section 1.5, “Resources” section of this book). However, we get several support questions everyday and many of them can be easily answered by going to the FAQ and by searching the mailing lists first. So for us to offer the best assistance possible, you need to do some research on your own first. This allows us to focus on the more unusual support needs. If your searches do not produce a solution, please include all relevant information (mentioned below) in your request for help.
Apart from a brief explanation of the problem being experienced, the essential things to include in any request for help are:
The version of the book being used (in this case 2.1.0)
The host distribution and version being used to create CLFS.
The architecture of the host and target.
The value of the $CLFS_HOST, $CLFS_TARGET, $BUILD32, and $BUILD64 environment variables.
The package or section in which the problem was encountered.
The exact error message or symptom received. See Section 1.6.3, “Compilation Problems” below for an example.
Note whether you have deviated from the book at all. A package version change or even a minor change to any command is considered deviation.
Deviating from this book does not mean that we will not help you. After all, the CLFS project is about personal preference. Be upfront about any changes to the established procedure—this helps us evaluate and determine possible causes of your problem.
If something goes wrong while running the configure script, review
the config.log
file. This file
may contain the errors you encountered during configure. It often logs
errors that may have not been printed to the screen. Include
only the relevant
lines if you need to ask for help.
Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output from the configure script and the make run can be helpful. It is not necessary to include the entire output, but do include enough of the relevant information. Below is an example of the type of information to include from the screen output from make:
gcc -DALIASPATH=\"/mnt/clfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/clfs/usr/share/locale\"
-DLIBDIR=\"/mnt/clfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/clfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
expand.o file.o function.o getopt.o implicit.o job.o main.o
misc.o read.o remake.o rule.o signame.o variable.o vpath.o
default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/clfs/tmp/make-3.79.1/job.c:1565: undefined reference
to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/clfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/clfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2
In this case, many people would just include the bottom section:
make [2]: *** [make] Error 1
This is not enough information to properly diagnose the problem because it only notes that something went wrong, not what went wrong. The entire section, as in the example above, is what should be saved because it includes the command that was executed and the associated error message(s).
An excellent article about asking for help on the Internet is available online at http://catb.org/~esr/faqs/smart-questions.html. Read and follow the hints in this document to increase the likelihood of getting the help you need.
In this chapter, the partition which will host the CLFS system is prepared. We will create the partition itself, create a file system on it, and mount it.
Like most other operating systems, CLFS is usually installed on a dedicated partition. The recommended approach to building a CLFS system is to use an available empty partition or, if you have enough unpartitioned space, to create one. However, if you're building for a different architecture you can simply build everything in “/mnt/clfs” and transfer it to your target machine.
A minimal system requires around 6 gigabytes (GB). This is enough to store all the source tarballs and compile the packages. The CLFS system itself will not take up this much room. A large portion of this requirement is to provide sufficient free temporary storage. Compiling packages can require a lot of disk space which will be reclaimed after the package is installed. If the CLFS system is intended to be the primary Linux system, additional software will probably be installed which will require additional space (2-10 GB).
Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as swap space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The swap partition for an CLFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.
Start a disk partitioning program such as cfdisk or fdisk with a command line
option naming the hard disk on which the new partition will be
created—for example /dev/hda
for the primary Integrated Drive
Electronics (IDE) disk. Create a Linux native partition and a
swap partition, if needed. Please refer to cfdisk(8)
or fdisk(8)
if you do not yet know how to use
the programs.
Remember the designation of the new partition (e.g.,
hda5
). This book will refer to
this as the CLFS partition. Also remember the designation of
the swap partition. These names will be needed later for the
/etc/fstab
file.
Now that a blank partition has been set up, the file system can
be created. The most widely-used system in the Linux world is
the second extended file system (ext2), but with newer
high-capacity hard disks, journaling file systems are becoming
increasingly popular. We will create an ext2
file system. Instructions for other
file systems can be found at http://cblfs.cross-lfs.org/index.php?section=6#File_System.
To create an ext2
file system
on the CLFS partition, run the following:
mke2fs /dev/[xxx]
Replace [xxx]
with
the name of the CLFS partition (hda5
in our previous example).
Some host distributions use custom features in their
filesystem creation tools (E2fsprogs). This can cause
problems when booting into your new CLFS system, as those
features will not be supported by the CLFS-installed
E2fsprogs; you will get an error similar to unsupported filesystem features, upgrade
your e2fsprogs
. To check if your host system uses
custom enhancements, run the following command:
debugfs -R feature /dev/[xxx]
If the output contains features other than: dir_index; filetype; large_file; resize_inode or sparse_super then your host system may have custom enhancements. In that case, to avoid later problems, you should compile the stock E2fsprogs package and use the resulting binaries to re-create the filesystem on your CLFS partition:
cd /tmp
tar xjf /path/to/sources/e2fsprogs-1.42.8.tar.bz2
cd e2fsprogs-1.42.8
mkdir build
cd build
../configure
make #note that we intentionally don't 'make install' here!
./misc/mke2fs /dev/[xxx]
cd /tmp
rm -rf e2fsprogs-1.42.8
If a swap partition was created, it will need to be initialized for use by issuing the command below. If you are using an existing swap partition, there is no need to format it.
mkswap /dev/[yyy]
Replace [yyy]
with
the name of the swap partition.
Now that a file system has been created, the partition needs to
be made accessible. In order to do this, the partition needs to
be mounted at a chosen mount point. For the purposes of this
book, it is assumed that the file system is mounted under
/mnt/clfs
, but the directory
choice is up to you.
Choose a mount point and assign it to the CLFS
environment variable by running:
export CLFS=/mnt/clfs
Next, create the mount point and mount the CLFS file system by running:
mkdir -pv ${CLFS}
mount -v /dev/[xxx]
${CLFS}
Replace [xxx]
with
the designation of the CLFS partition.
If using multiple partitions for CLFS (e.g., one for
/
and another for /usr
), mount them using:
mkdir -pv ${CLFS} mount -v /dev/[xxx]
${CLFS} mkdir -v ${CLFS}/usr mount -v /dev/[yyy]
${CLFS}/usr
Replace [xxx]
and
[yyy]
with the
appropriate partition names.
Ensure that this new partition is not mounted with permissions
that are too restrictive (such as the nosuid, nodev, or noatime
options). Run the mount command without any
parameters to see what options are set for the mounted CLFS
partition. If nosuid
, nodev
, and/or noatime
are set, the partition will need to be
remounted.
Now that there is an established place to work, it is time to download the packages.
This chapter includes a list of packages that need to be downloaded for building a basic Linux system. The listed version numbers correspond to versions of the software that are known to work, and this book is based on their use. We highly recommend not using newer versions because the build commands for one version may not work with a newer version. The newest package versions may also have problems that require work-arounds. These work-arounds will be developed and stabilized in the development version of the book.
Download locations may not always be accessible. If a download location has changed since this book was published, Google (http://www.google.com/) provides a useful search engine for most packages. If this search is unsuccessful, try one of the alternative means of downloading discussed at http://cross-lfs.org/files/packages/git/.
Create a directory called ${CLFS}/sources
and use it to store your
sources and patches. All packages should be compiled there as
well. Using any other location for compiling may have
unexpected results.
To create this directory, execute, as user root
, the following command before starting
the download session:
mkdir -v ${CLFS}/sources
Make this directory writable and sticky. When a directory is marked “sticky”, that means that even if multiple users have write permission on that directory, any file within that directory can only be deleted or modified by its owner. The following command will enable the write and sticky modes:
chmod -v a+wt ${CLFS}/sources
You can download all needed packages and patches into this directory either by using the links on the following pages in this section, or by passing the download list to wget:
wget -i dl.list -P ${CLFS}/sources
Verification of downloaded packages can be done by downloading the following MD5 or SHA1 checksum lists:
pushd ${CLFS}/sources md5sum -c MD5SUMS popd
pushd ${CLFS}/sources md5sum -c SHA1SUMS popd
Download or otherwise obtain the following packages:
Home page: http://www.gnu.org/software/autoconf
Download: http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.xz
MD5 sum: 50f97f4159805e374639a73e2636f22e
Home page: http://www.gnu.org/software/automake
Download: http://ftp.gnu.org/gnu/automake/automake-1.12.4.tar.xz
MD5 sum: 7395a0420ecb5c9bc43e5fcf4824df36
Home page: http://www.gnu.org/software/bash
Download: http://ftp.gnu.org/gnu/bash/bash-4.2.tar.gz
MD5 sum: 3fb927c7c33022f1c327f14a81c0d4b0
Home page: http://www.gnu.org/software/bc/
Download: http://alpha.gnu.org/gnu/bc/bc-1.06.95.tar.bz2
MD5 sum: 5126a721b73f97d715bb72c13c889035
Home page: http://sources.redhat.com/binutils
Download: http://ftp.gnu.org/gnu/binutils/binutils-2.23.2.tar.bz2
MD5 sum: 4f8fa651e35ef262edc01d60fb45702e
Home page: http://www.gnu.org/software/bison
Download: http://ftp.gnu.org/gnu/bison/bison-3.0.tar.xz
MD5 sum: a2624994561aa69f056c904c1ccb2880
Download: http://cross-lfs.org/files/packages/git/bootscripts-cross-lfs-2.1-pre1.tar.xz
MD5 sum: f474bf2efff744548a69d9049bad973f
Home page: http://www.bzip.org/
Download: http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz
MD5 sum: 00b516f4704d4a7cb50a1d97e6e8e15b
Home page: http://check.sourceforge.net/
Download: http://sourceforge.net/projects/check/files/check/0.9.10/check-0.9.10.tar.gz
MD5 sum: 6d10a8efb9a683467b92b3bce97aeb30
Home page: http://cloog.org
Download: http://www.bastoul.net/cloog/pages/download/cloog-0.18.0.tar.gz
MD5 sum: be78a47bd82523250eb3e91646db5b3d
Home page: http://www.gnu.org/software/coreutils
Download: http://ftp.gnu.org/gnu/coreutils/coreutils-8.21.tar.xz
MD5 sum: 065ba41828644eca5dd8163446de5d64
Home page: http://www.gnu.org/software/dejagnu
Download: http://ftp.gnu.org/gnu/dejagnu/dejagnu-1.5.1.tar.gz
MD5 sum: 8386e04e362345f50ad169f052f4c4ab
Home page: http://roy.marples.name/projects/dhcpcd
Download: http://roy.marples.name/downloads/dhcpcd/dhcpcd-6.1.0.tar.bz2
MD5 sum: 6070040c57492925af9ac6aed980de2a
Home page: http://www.gnu.org/software/diffutils
Download: http://ftp.gnu.org/gnu/diffutils/diffutils-3.3.tar.xz
MD5 sum: 99180208ec2a82ce71f55b0d7389f1b3
Home page: http://www.eglibc.org/home
Download: http://cross-lfs.org/files/eglibc-2.18-r24148.tar.xz
MD5 sum: 8b3dc01f6ee5f1654b98213e8d4721a4
Home page: http://e2fsprogs.sourceforge.net
Download: http://www.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.42.8/e2fsprogs-1.42.8.tar.xz
MD5 sum: 57f20ba5e4cac8ce082065a61aa3f3bc
Home page: http://www.gentoo.org/proj/en/eudev/
Download: ftp://mirror.ovh.net/gentoo-distfiles/distfiles/eudev-1.3.tar.gz
MD5 sum: 164df78f6f0093578a20bdd00335845f
Home page: http://expect.sourceforge.net
Download: http://downloads.sourceforge.net/project/expect/Expect/5.45/expect5.45.tar.gz
MD5 sum: 44e1a4f4c877e9ddc5a542dfa7ecc92b
Home page: http://www.darwinsys.com/file
Download: ftp://ftp.astron.com/pub/file/file-5.15.tar.gz
MD5 sum: 3f99565532f548d7540912c4642d1ede
File (5.15) may no longer be available at the listed location. The site administrators of the master download location occasionally remove older versions when new ones are released. An alternative download location that may have the correct version available is http://cross-lfs.org/files/packages/git/.
Home page: http://www.gnu.org/software/findutils
Download: http://ftp.gnu.org/gnu/findutils/findutils-4.4.2.tar.gz
MD5 sum: 351cc4adb07d54877fa15f75fb77d39f
Home page: http://flex.sourceforge.net
Download: http://downloads.sourceforge.net/flex/flex-2.5.37.tar.bz2
MD5 sum: c75940e1fc25108f2a7b3ef42abdae06
Home page: http://www.gnu.org/software/gawk
Download: http://ftp.gnu.org/gnu/gawk/gawk-4.1.0.tar.xz
MD5 sum: b18992ff8faf3217dab55d2d0aa7d707
Home page: http://gcc.gnu.org
Download: ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.8.1/gcc-4.8.1.tar.bz2
MD5 sum: 3b2386c114cd74185aa3754b58a79304
Home page: http://www.gnu.org/software/gettext
Download: http://ftp.gnu.org/gnu/gettext/gettext-0.18.3.1.tar.gz
MD5 sum: 3fc808f7d25487fc72b5759df7419e02
Home page: http://gmplib.org/
Download: http://ftp.gnu.org/gnu/gmp/gmp-5.1.3.tar.xz
MD5 sum: e5fe367801ff067b923d1e6a126448aa
Home page: http://www.gnu.org/software/grep
Download: http://ftp.gnu.org/gnu/grep/grep-2.14.tar.xz
MD5 sum: d4a3f03849d1e17ce56ab76aa5a24cab
Home page: http://www.gnu.org/software/groff
Download: http://ftp.gnu.org/gnu/groff/groff-1.22.2.tar.gz
MD5 sum: 9f4cd592a5efc7e36481d8d8d8af6d16
Home page: http://www.gzip.org
Download: http://ftp.gnu.org/gnu/gzip/gzip-1.6.tar.xz
MD5 sum: da981f86677d58a106496e68de6f8995
Home page: http://www.archlinux.org/packages/core/any/iana-etc/
Download: http://ftp.cross-lfs.org/pub/clfs/conglomeration/iana-etc/iana-etc-2.30.tar.bz2
MD5 sum: 3ba3afb1d1b261383d247f46cb135ee8
Home page: http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
Download: http://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-3.10.0.tar.xz
MD5 sum: 45fb5427fc723a0001c72b92c931ba02
Home page: http://www.linuxfoundation.org/en/Net:Iputils
Download: http://www.skbuff.net/iputils/iputils-s20121221.tar.bz2
MD5 sum: 6072aef64205720dd1893b375e184171
Home page: http://garage.kotnet.org/~skimo/isl/
Download: http://isl.gforge.inria.fr/isl-0.12.1.tar.lzma
MD5 sum: d7a723a508056b9dc5a25c5ca7d1d74f
Download: ftp://devel.altlinux.org/legion/kbd/kbd-2.0.0.tar.gz
MD5 sum: 5ba259a0b2464196f6488a72070a3d60
Home page: http://git.kernel.org/?p=utils/kernel/kmod/kmod.git;a=summary
Download: http://www.kernel.org/pub/linux/utils/kernel/kmod/kmod-15.tar.xz
MD5 sum: d03372179ed2cfa0c52b6672cf438901
Home page: http://www.greenwoodsoftware.com/less
Download: http://www.greenwoodsoftware.com/less/less-460.tar.gz
MD5 sum: c3b603140aed2beb6091fdbc27f80ff0
Home page: http://www.libee.org/
Download: http://www.libee.org/download/files/download/libee-0.4.1.tar.gz
MD5 sum: 7bbf4160876c12db6193c06e2badedb2
Home page: http://libestr.adiscon.com/
Download: http://libestr.adiscon.com/files/download/libestr-0.1.5.tar.gz
MD5 sum: f180c0cdc82883d161eba3f2e8a34eb4
Home page: http://www.gnu.org/software/libtool
Download: http://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.xz
MD5 sum: 2ec8997e0c07249eb4cbd072417d70fe
Home page: http://www.kernel.org
Download: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.10.14.tar.xz
MD5 sum: 3cd1e4b50fb9decd63754ae80f3b2414
Home page: http://www.gnu.org/software/m4
Download: http://ftp.gnu.org/gnu/m4/m4-1.4.17.tar.xz
MD5 sum: 12a3c829301a4fd6586a57d3fcf196dc
Home page: http://www.gnu.org/software/make
Download: http://ftp.gnu.org/gnu/make/make-3.82.tar.bz2
MD5 sum: 1a11100f3c63fcf5753818e59d63088f
Home page: http://primates.ximian.com/~flucifredi/man
Download: http://primates.ximian.com/~flucifredi/man/man-1.6g.tar.gz
MD5 sum: ba154d5796928b841c9c69f0ae376660
Home page: http://www.win.tue.nl/~aeb/linux/man
Download: http://www.kernel.org/pub/linux/docs/man-pages/man-pages-3.54.tar.xz
MD5 sum: 382f83e670ecbe1d97fc58e03da0b026
Home page: http://www.multiprecision.org/
Download: http://www.multiprecision.org/mpc/download/mpc-1.0.1.tar.gz
MD5 sum: b32a2e1a3daa392372fbd586d1ed3679
Home page: http://www.mpfr.org/
Download: http://www.mpfr.org/mpfr-3.1.2/mpfr-3.1.2.tar.xz
MD5 sum: e3d203d188b8fe60bb6578dd3152e05c
Home page: http://www.gnu.org/software/ncurses
Download: ftp://ftp.gnu.org/pub/gnu/ncurses/ncurses-5.9.tar.gz
MD5 sum: 8cb9c412e5f2d96bc6f459aa8c6282a1
Home page: http://savannah.gnu.org/projects/patch
Download: http://ftp.gnu.org/gnu/patch/patch-2.7.1.tar.xz
MD5 sum: e9ae5393426d3ad783a300a338c09b72
Home page: http://www.perl.org
Download: http://www.cpan.org/src/5.0/perl-5.18.1.tar.bz2
MD5 sum: 4ec1a3f3824674552e749ae420c5e68c
Home page: http://sourceforge.net/projects/pkgconfiglite
Download: http://sourceforge.net/projects/pkgconfiglite/files/0.28-1/pkg-config-lite-0.28-1.tar.gz
MD5 sum: 61f05feb6bab0a6bbfab4b6e3b2f44b6
Home page: http://procps.sourceforge.net
Download: http://procps.sourceforge.net/procps-3.2.8.tar.gz
MD5 sum: 9532714b6846013ca9898984ba4cd7e0
Home page: http://psmisc.sourceforge.net
Download: http://downloads.sourceforge.net/psmisc/psmisc-22.20.tar.gz
MD5 sum: a25fc99a6dc7fa7ae6e4549be80b401f
Home page: http://cnswww.cns.cwru.edu/php/chet/readline/rltop.html
Download: http://ftp.gnu.org/gnu/readline/readline-6.2.tar.gz
MD5 sum: 67948acb2ca081f23359d0256e9a271c
Home page: http://www.rsyslog.com/
Download: http://www.rsyslog.com/files/download/rsyslog/rsyslog-6.4.2.tar.gz
MD5 sum: 7de0124ec7d67ce2bfda0009ab1263ee
Home page: http://www.gnu.org/software/sed
Download: http://ftp.gnu.org/gnu/sed/sed-4.2.2.tar.bz2
MD5 sum: 7ffe1c7cdc3233e1e0c4b502df253974
Home page: http://pkg-shadow.alioth.debian.org
Download: http://pkg-shadow.alioth.debian.org/releases/shadow-4.1.5.1.tar.bz2
MD5 sum: a00449aa439c69287b6d472191dc2247
Home page: http://savannah.nongnu.org/projects/sysvinit
Download: http://download.savannah.gnu.org/releases/sysvinit/sysvinit-2.88dsf.tar.bz2
MD5 sum: 6eda8a97b86e0a6f59dabbf25202aa6f
Home page: http://www.gnu.org/software/tar
Download: http://ftp.gnu.org/gnu/tar/tar-1.26.tar.bz2
MD5 sum: 2cee42a2ff4f1cd4f9298eeeb2264519
Home page: http://www.tcl.tk
Download: http://downloads.sourceforge.net/tcl/tcl8.6.1-src.tar.gz
MD5 sum: aae4b701ee527c6e4e1a6f9c7399882e
Home page: http://www.gnu.org/software/texinfo
Download: http://ftp.gnu.org/gnu/texinfo/texinfo-4.13a.tar.gz
MD5 sum: 71ba711519209b5fb583fed2b3d86fcb
Home page: http://www.iana.org/time-zones
Download: http://www.iana.org/time-zones/repository/releases/tzdata2013g.tar.gz
MD5 sum: 76dbc3b5a81913fc0d824376c44a5d15
Home page: http://userweb.kernel.org/~kzak/util-linux/
Download: http://www.kernel.org/pub/linux/utils/util-linux/v2.23/util-linux-2.23.2.tar.xz
MD5 sum: b39fde897334a4858bb2098edcce5b3f
Home page: http://www.vim.org
Download: ftp://ftp.vim.org/pub/vim/unix/vim-7.4.tar.bz2
MD5 sum: 607e135c559be642f210094ad023dc65
Home page: http://tukaani.org/xz/
Download: http://tukaani.org/xz/xz-5.0.5.tar.xz
MD5 sum: aa17280f4521dbeebed0fbd11cd7fa30
Home page: http://www.zlib.net
Download: http://zlib.net/zlib-1.2.8.tar.xz
MD5 sum: 28f1205d8dd2001f26fec1e8c2cebe37
Zlib (1.2.8) may no longer be available at the listed location. The site administrators of the master download location occasionally remove older versions when new ones are released. An alternative download location that may have the correct version available is http://cross-lfs.org/files/packages/git/.
Total size of these packages: about 312 MB
Home page: http://www.gnu.org/software/grub
Download: http://ftp.gnu.org/gnu/grub/grub-2.00.tar.xz
MD5 sum: a1043102fbc7bcedbf53e7ee3d17ab91
Total size of these packages: about 5 MB
In addition to the packages, several patches are also required. These patches correct any mistakes in the packages that should be fixed by the maintainer. The patches also make small modifications to make the packages easier to work with. The following patches will be needed to build a CLFS system:
Download: http://patches.cross-lfs.org/2.1.0/bash-4.2-branch_update-7.patch
MD5 sum: 4dfb1ce9b5d0040eae06e66157ab213a
Download: http://patches.cross-lfs.org/2.1.0/coreutils-8.21-uname-1.patch
MD5 sum: 5d3a1f7196c9c07033bbd2853885fda2
Download: http://patches.cross-lfs.org/2.1.0/gcc-4.8.1-branch_update-3.patch
MD5 sum: 743b954ce42dd6193376e43ea84d7c10
Download: http://patches.cross-lfs.org/2.1.0/iana-etc-2.30-get_fix-1.patch
MD5 sum: 73aee2dc34cf4d990cc22fe323d89f27
Download: http://patches.cross-lfs.org/2.1.0/iana-etc-2.30-numbers_update-20120610-2.patch
MD5 sum: 826fb780d13caafb7cb99b9c346f2102
Download: http://patches.cross-lfs.org/2.1.0/iputils-s20121221-fixes-1.patch
MD5 sum: a2e77de7fd1fc4417bce0af3e6ffdfcb
Download: http://patches.cross-lfs.org/2.1.0/make-3.82-fixes-1.patch
MD5 sum: bca6c0167780f427f527e976d597b505
Download: http://patches.cross-lfs.org/2.1.0/man-1.6g-i18n-1.patch
MD5 sum: a5aba0cb5a95a7945db8c882334b7dab
Download: http://patches.cross-lfs.org/2.1.0/ncurses-5.9-bash_fix-1.patch
MD5 sum: c6f7f2ab0ebaf7721ebeb266641352db
Download: http://patches.cross-lfs.org/2.1.0/ncurses-5.9-branch_update-4.patch
MD5 sum: c2b2dc2d31b02c218359e6218f12a72c
Download: http://patches.cross-lfs.org/2.1.0/perl-5.18.1-libc-1.patch
MD5 sum: 63eda1cc319206788ea93c58f395417c
Download: http://patches.cross-lfs.org/2.1.0/procps-3.2.8-fix_HZ_errors-1.patch
MD5 sum: 2ea4c8e9a2c2a5a291ec63c92d7c6e3b
Download: http://patches.cross-lfs.org/2.1.0/procps-3.2.8-ps_cgroup-1.patch
MD5 sum: 3c478ef88fad23353e332b1b850ec630
Download: http://patches.cross-lfs.org/2.1.0/readline-6.2-branch_update-3.patch
MD5 sum: af788f5b1cfc5db9efc9e0fa0268a574
Download: http://patches.cross-lfs.org/2.1.0/tar-1.26-man-1.patch
MD5 sum: 074783d41f18c5c62a7cfc77e2678693
Download: http://patches.cross-lfs.org/2.1.0/texinfo-4.13a-new_compressors-1.patch
MD5 sum: 4ae2d3c132e21cb83b825bc691056d07
Download: http://patches.cross-lfs.org/2.1.0/vim-7.4-branch_update-1.patch
MD5 sum: b5fdb7f4e4cc27932a9183c8e289029d
Total size of these patches: about 23 MB
In addition to the above required patches, there exist a number of optional patches created by the CLFS community. These optional patches solve minor problems or enable functionality that is not enabled by default. Feel free to peruse the patches database located at http://patches.cross-lfs.org/2.1.0/ and acquire any additional patches to suit the system needs.
Download: http://patches.cross-lfs.org/2.1.0/gcc-4.8.1-specs-1.patch
MD5 sum: 14aa064a113f2cae0f877039bb4a6357
Total size of these patches: about 20 KB
Throughout this book, the environment variable CLFS
will be used several times. It is paramount
that this variable is always defined. It should be set to the
mount point chosen for the CLFS partition. Check that the
CLFS
variable is set up properly
with:
echo ${CLFS}
Make sure the output shows the path to the CLFS partition's
mount point, which is /mnt/clfs
if the provided example was followed. If the output is
incorrect, the variable can be set with:
export CLFS=/mnt/clfs
Having this variable set is beneficial in that commands such as install -dv ${CLFS}/tools can be typed literally. The shell will automatically replace “${CLFS}” with “/mnt/clfs” (or whatever the variable was set to) when it processes the command line.
If you haven't created the ${CLFS}
directory, do so at this time by
issuing the following commands:
install -dv ${CLFS}
Do not forget to check that ${CLFS}
is set whenever you leave and reenter the current working
environment (as when doing a “su” to root
or another user).
All programs compiled in Constructing
a Temporary System will be installed under ${CLFS}/tools
to keep them separate from the
programs compiled in Installing
Basic System Software. The programs compiled here are
temporary tools and will not be a part of the final CLFS
system. By keeping these programs in a separate directory, they
can easily be discarded later after their use. This also
prevents these programs from ending up in the host production
directories (easy to do by accident in Constructing
a Temporary System).
Create the required directory by running the following as
root
:
install -dv ${CLFS}/tools
The next step is to create a /tools
symlink on the host system. This will
point to the newly-created directory on the CLFS partition. Run
this command as root
as well:
ln -sv ${CLFS}/tools /
The above command is correct. The ln command has a few
syntactic variations, so be sure to check info coreutils ln and
ln(1)
before reporting what you
may think is an error.
The created symlink enables the toolchain to be compiled so
that it always refers to /tools
,
meaning that the compiler, assembler, and linker will work.
This will provide a common place for our temporary tools
system.
The cross-binutils and cross-compiler built in Constructing
Cross-Compile Tools will be installed under ${CLFS}/cross-tools
to keep them separate
from the host programs. The programs compiled here are
cross-tools and will not be a part of the final CLFS system or
the temp-system. By keeping these programs in a separate
directory, they can easily be discarded later after their use.
Create the required directory by running the following as
root
:
install -dv ${CLFS}/cross-tools
The next step is to create a /cross-tools
symlink on the host system. This
will point to the newly-created directory on the CLFS
partition. Run this command as root
as well:
ln -sv ${CLFS}/cross-tools /
The symlink isn't technically necessary (though the book's instructions do assume its existence), but is there mainly for consistency (because /tools is also symlinked to ${CLFS}/tools) and to simplify the installation of the cross-compile tools.
When logged in as user root
,
making a single mistake can damage or destroy a system.
Therefore, we recommend building the packages as an
unprivileged user. You could use your own user name, but to
make it easier to set up a clean work environment, create a new
user called clfs
as a member of
a new group (also named clfs
)
and use this user during the installation process. As
root
, issue the following
commands to add the new user:
groupadd clfs useradd -s /bin/bash -g clfs -d /home/clfs clfs mkdir -pv /home/clfs chown -v clfs:clfs /home/clfs
The meaning of the command line options:
-s
/bin/bash
This makes bash the default shell
for user clfs
.
The build instructions assume that the bash shell is in use.
-g
clfs
This option adds user clfs
to group clfs
.
clfs
This is the actual name for the created group and user.
To log in as clfs
(as opposed
to switching to user clfs
when
logged in as root
, which does
not require the clfs
user to
have a password), give clfs
a
password:
passwd clfs
Grant clfs
full access to
${CLFS}/cross-tools
and
${CLFS}/tools
by making
clfs
the directorys' owner:
chown -v clfs ${CLFS}/tools chown -v clfs ${CLFS}/cross-tools
If a separate working directory was created as suggested, give
user clfs
ownership of this
directory:
chown -v clfs ${CLFS}/sources
Next, login as user clfs
. This
can be done via a virtual console, through a display manager,
or with the following substitute user command:
su - clfs
The “-
” instructs
su to start a
login shell as opposed to a non-login shell. The difference
between these two types of shells can be found in detail in
bash(1)
and info bash.
Until specified otherwise, all commands from this point on
should be done as the clfs
user.
Set up a good working environment by creating two new startup
files for the bash shell. While logged in
as user clfs
, issue the
following command to create a new .bash_profile
:
cat > ~/.bash_profile << "EOF"
exec env -i HOME=${HOME} TERM=${TERM} PS1='\u:\w\$ ' /bin/bash
EOF
When logged on as user clfs
,
the initial shell is usually a login shell which reads the
/etc/profile
of the host
(probably containing some settings and environment variables)
and then .bash_profile
. The
exec env
-i.../bin/bash command in the .bash_profile
file replaces the running shell
with a new one with a completely empty environment, except for
the HOME
, TERM
, and PS1
variables. This ensures that no unwanted and potentially
hazardous environment variables from the host system leak into
the build environment. The technique used here achieves the
goal of ensuring a clean environment.
The new instance of the shell is a non-login shell, which does not read
the /etc/profile
or .bash_profile
files, but rather reads the
.bashrc
file instead. Create the
.bashrc
file now:
cat > ~/.bashrc << "EOF"
set +h
umask 022
CLFS=/mnt/clfs
LC_ALL=POSIX
PATH=/cross-tools/bin:/bin:/usr/bin
export CLFS LC_ALL PATH
EOF
The set +h
command turns off bash's hash function. Hashing
is ordinarily a useful feature—bash uses a hash table to
remember the full path of executable files to avoid searching
the PATH
time and again to find the
same executable. However, the new tools should be used as soon
as they are installed. By switching off the hash function, the
shell will always search the PATH
when a program is to be run. As such, the shell will find the
newly compiled tools in /cross-tools
as soon as they are available
without remembering a previous version of the same program in a
different location.
Setting the user file-creation mask (umask) to 022 ensures that newly created files and directories are only writable by their owner, but are readable and executable by anyone (assuming default modes are used by the open(2) system call, new files will end up with permission mode 644 and directories with mode 755).
The CLFS
variable should be set to
the chosen mount point.
The LC_ALL
variable controls the
localization of certain programs, making their messages follow
the conventions of a specified country. If the host system uses
a version of Glibc older than 2.2.4, having LC_ALL
set to something other than
“POSIX” or
“C” (during this
chapter) may cause issues if you exit the chroot environment
and wish to return later. Setting LC_ALL
to “POSIX” or “C” (the two are equivalent) ensures that
everything will work as expected in the chroot environment.
By putting /cross-tools/bin
at
the beginning of the PATH
, the
cross-compiler built in Constructing
Cross-Compile Tools will be picked up by the build process
for the temp-system packages before anything that may be
installed on the host. This, combined with turning off hashing,
helps to ensure that you will be using the cross-compile tools
to build the temp-system in /tools.
Finally, to have the environment fully prepared for building the temporary tools, source the just-created user profile:
source ~/.bash_profile
Most packages provide a test suite. Running the test suite for a newly built package is a good idea because it can provide a “sanity check” indicating that everything compiled correctly. A test suite that passes its set of checks usually proves that the package is functioning as the developer intended. It does not, however, guarantee that the package is totally bug free.
It is not possible to run testsuites when cross-compiling, so package installation instructions do not explain how to run testsuites until Installing Basic System Software.
This chapter shows you how to create cross platform tools.
If for some reason you have to stop and come back later, remember to use the su - clfs command, and it will setup the build environment that you left.
Before issuing the build instructions for a package, the package should be unpacked, and a cd into the created directory should be performed.
Several of the packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both this and the next chapters, but sometimes in only one or the other. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about offset or fuzz may also be encountered when applying a patch. Do not worry about these warnings, as the patch was still successfully applied.
During the compilation of most packages, there will be several warnings that scroll by on the screen. These are normal and can safely be ignored. These warnings are as they appear—warnings about deprecated, but not invalid, use of the C or C++ syntax. C standards change fairly often, and some packages still use the older standard. This is not a problem, but does prompt the warning.
After installing each package, both in this and the next chapters, delete its source and build directories, unless specifically instructed otherwise. Deleting the sources prevents mis-configuration when the same package is reinstalled later.
CFLAGS
and CXXFLAGS
must not be set during the building of
cross-tools.
To disable CFLAGS
and CXXFLAGS
use the following commands:
unset CFLAGS unset CXXFLAGS
Now add these to ~/.bashrc
, just
in case you have to exit and restart building later:
echo unset CFLAGS >> ~/.bashrc echo unset CXXFLAGS >> ~/.bashrc
During the building of the cross-compile tools you will need to
set a few variables that will be dependent on your particular
needs. The first variable will be the triplet of the host
machine, which will be put into the CLFS_HOST
variable. To account for the
possibility that the host and target are the same arch, as
cross-compiling won't work when host and target are the same,
part of the triplet needs to be changed slightly to add
"cross". Set CLFS_HOST
using the
following command:
export CLFS_HOST=$(echo ${MACHTYPE} | sed -e 's/-[^-]*/-cross/')
Now you will need to set the triplet for the target architecture. Set the target variable using the following command:
export CLFS_TARGET="[target triplet]"
Replace [target triplet] with the appropriate machine triplet using the table at the bottom of the page.
Now add these to ~/.bashrc
, just
in case you have to exit and restart building later:
cat >> ~/.bashrc << EOF export CLFS_HOST="${CLFS_HOST}" export CLFS_TARGET="${CLFS_TARGET}" EOF
Table 5.1. Processor Type and Target Triplets
Processor | Target Triplet |
---|---|
386 Compatibles | Not Supported By Glibc |
486 Compatibles | i486-pc-linux-gnu |
Pentium, K6, 586 Compatibles | i586-pc-linux-gnu |
Pentium II, Pentium III, Pentium 4 | i686-pc-linux-gnu |
Athlon, Duron | i686-pc-linux-gnu |
The Bc pacakge contains an arbitrary precision numeric processing language.
Prepare Bc for compilation:
./configure --prefix=/cross-tools
The meaning of the configure options:
--prefix=/cross-tools
This tells the configure script to prepare to install
the package in the /cross-tools
directory.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.36.2, “Contents of Bc.”
The Linux Kernel contains a make target that installs “sanitized” kernel headers.
For this step you will need the kernel tarball.
Install the kernel header files:
make mrproper make ARCH=i386 headers_check make ARCH=i386 INSTALL_HDR_PATH=/tools headers_install
The meaning of the make commands:
make
mrproper
Ensures that the kernel source dir is clean.
make
ARCH=i386 headers_check
Sanitizes the raw kernel headers so that they can be used by userspace programs.
make
ARCH=i386 INSTALL_HDR_PATH=/tools
headers_install
This will install the kernel headers into /tools/include
.
Details on this package are located in Section 10.5.2, “Contents of Linux-Headers.”
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
./configure --prefix=/cross-tools --disable-static
The meaning of the configure options:
--prefix=/cross-tools
This tells the configure script to prepare to install
the package in the /cross-tools
directory.
--disable-static
This tells the File package not to compile or install static libraries, which are not needed for the Cross-Tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.39.2, “Contents of File.”
The M4 package contains a macro processor.
Prepare M4 for compilation:
./configure --prefix=/cross-tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.26.2, “Contents of M4.”
The Ncurses package contains libraries for terminal-independent handling of character screens.
The following patch fixes an issue with some Bash versions:
patch -Np1 -i ../ncurses-5.9-bash_fix-1.patch
Prepare Ncurses for compilation:
./configure --prefix=/cross-tools \ --without-debug --without-shared
The meaning of the new configure options:
--without-debug
Tells Ncurses to build without debugging information.
--without-shared
This prevents Ncurses from building its shared libraries, which are not needed at this time.
Only one binary is needed for the Cross-Tools. Build the headers and then build tic:
make -C include make -C progs tic
Install tic with the following command:
install -v -m755 progs/tic /cross-tools/bin
Details on this package are located in Section 10.18.2, “Contents of Ncurses.”
GMP is a library for arithmetic on arbitrary precision integers, rational numbers, and floating-point numbers.
If you are building with a host which has 32-bit user-space with a 64-bit capable CPU, cross-tools GMP will attempt to link with 64-bit libraries. Add the following variable during configure to force GMP's ABI: ./configure ABI=32
Prepare GMP for compilation:
./configure --prefix=/cross-tools --enable-cxx \ --disable-static
The meaning of the new configure options:
--enable-cxx
This tells GMP to enable C++ support.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.9.2, “Contents of GMP.”
The MPFR library is a C library for multiple-precision floating-point computations with correct rounding.
Prepare MPFR for compilation:
LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ./configure --prefix=/cross-tools \ --disable-static --with-gmp=/cross-tools
The meaning of the new configure options:
LDFLAGS="-Wl,-rpath,/cross-tools/lib"
This tells configure to search
in /cross-tools
for
libraries.
--enable-shared
This tells configure to build MPFR's shared libraries.
--with-gmp=/cross-tools
This tells configure where to find GMP.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.10.2, “Contents of MPFR.”
MPC is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result.
Prepare MPC for compilation:
LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ./configure --prefix=/cross-tools --disable-static \ --with-gmp=/cross-tools --with-mpfr=/cross-tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.11.2, “Contents of MPC.”
ISL is a library for manipulating sets and relations of integer points bounded by linear constraints.
Prepare ISL for compilation:
LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ./configure --prefix=/cross-tools --disable-static \ --with-gmp-prefix=/cross-tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.12.2, “Contents of ISL.”
CLooG is a library to generate code for scanning Z-polyhedra. In other words, it finds code that reaches each integral point of one or more parameterized polyhedra. GCC links with this library in order to enable the new loop generation code known as Graphite.
Prepare CLooG for compilation:
LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ./configure --prefix=/cross-tools --disable-static \ --with-gmp-prefix=/cross-tools --with-isl-prefix=/cross-tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.13.2, “Contents of CLooG.”
The Binutils package contains a linker, an assembler, and other tools for handling object files.
It is important that Binutils be compiled before Glibc and GCC because both Glibc and GCC perform various tests on the available linker and assembler to determine which of their own features to enable.
Apply the following sed for hosts using Texinfo-5.x:
sed -i -e 's/@colophon/@@colophon/' \ -e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
AR=ar AS=as ../binutils-2.23.2/configure \ --prefix=/cross-tools --host=${CLFS_HOST} --target=${CLFS_TARGET} \ --with-sysroot=${CLFS} --with-lib-path=/tools/lib --disable-nls \ --disable-static --disable-multilib
The meaning of the new configure options:
AR=ar
AS=as
This prevents Binutils from compiling with ${CLFS_HOST}-ar and ${CLFS_HOST}-as as they are provided by this package and therefore not installed yet.
--host=${CLFS_HOST}
When used with --target, this creates a cross-architecture executable that creates files for ${CLFS_TARGET} but runs on ${CLFS_HOST}.
--target=${CLFS_TARGET}
When used with --host, this creates a cross-architecture executable that creates files for ${CLFS_TARGET} but runs on ${CLFS_HOST}.
--with-lib-path=/tools/lib
This tells the configure script to specify the library
search path during the compilation of Binutils,
resulting in /tools/lib
being passed to the linker. This prevents the linker
from searching through library directories on the host.
--disable-nls
This disables internationalization as i18n is not needed for the cross-compile tools.
--disable-multilib
This option disables the building of a multilib capable Binutils.
Compile the package:
make configure-host make
The meaning of the make options:
configure-host
This checks the host environment and makes sure all the necessary tools are available to compile Binutils.
Install the package:
make install
Copy libiberty.h
to
/tools/include
directory:
cp -v ../binutils-2.23.2/include/libiberty.h /tools/include
Details on this package are located in Section 10.15.2, “Contents of Binutils.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch contains a number of updates to the 4.8.1 branch by the GCC developers:
patch -Np1 -i ../gcc-4.8.1-branch_update-3.patch
Make a couple of essential adjustments to the specs
file to ensure GCC uses our build
environment:
patch -Np1 -i ../gcc-4.8.1-specs-1.patch
Change the StartFile Spec so that GCC looks in /tools
:
echo -en '\n#undef STANDARD_STARTFILE_PREFIX_1\n#define STANDARD_STARTFILE_PREFIX_1 "/tools/lib/"\n' >> gcc/config/linux.h echo -en '\n#undef STANDARD_STARTFILE_PREFIX_2\n#define STANDARD_STARTFILE_PREFIX_2 ""\n' >> gcc/config/linux.h
We will create a dummy limits.h
so the build will not use the one provided by the host
distro:
touch /tools/include/limits.h
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
AR=ar LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ../gcc-4.8.1/configure --prefix=/cross-tools \ --build=${CLFS_HOST} --host=${CLFS_HOST} --target=${CLFS_TARGET} \ --with-sysroot=${CLFS} --with-local-prefix=/tools \ --with-native-system-header-dir=/tools/include --disable-nls \ --disable-shared --with-mpfr=/cross-tools --with-gmp=/cross-tools \ --with-isl=/cross-tools --with-cloog=/cross-tools --with-mpc=/cross-tools \ --without-headers --with-newlib --disable-decimal-float --disable-libgomp \ --disable-libmudflap --disable-libssp --disable-threads --disable-multilib \ --disable-libatomic --disable-libitm --disable-libsanitizer \ --disable-libquadmath --disable-target-libiberty --disable-target-zlib \ --with-system-zlib --enable-cloog-backend=isl --disable-isl-version-check \ --enable-languages=c --enable-checking=release
The meaning of the new configure options:
--with-sysroot=${CLFS}
Tells GCC to consider ${CLFS} as the root file system.
--with-local-prefix=/tools
The purpose of this switch is to remove /usr/local/include
from gcc's include search
path. This is not absolutely essential, however, it
helps to minimize the influence of the host system.
--with-native-system-headers-dir=/tools/include
This switch ensures that GCC will search for the system
headers in /tools/include
and that host system headers will not be searched.
--disable-nls
This disables internationalization as i18n is not needed for the cross-compile tools.
--without-headers
Disables GCC from using the target's Libc when cross compiling.
--with-newlib
Tells GCC that the target libc will use 'newlib'.
--disable-decimal-float
Disables support for the C decimal floating point extension.
--disable-libgomp
Disables the creation of runtime libraries used by GOMP.
--disable-libmudflap
Disables the creation of runtime libaries used by libmudflap.
--disable-libssp
Disables the use of Stack Smashing Protection for runtime libraries.
--disable-threads
This will prevent GCC from looking for the multi-thread include files, since they haven't been created for this architecture yet. GCC will be able to find the multi-thread information after the Glibc headers are created.
--disable-libatomic
The atomic library isn't needed at this time.
--disable-libitm
The itm library isn't neeeded at this tiem.
--disable-libsanitizer
The sanitizer library isn't needed at this time.
--disable-libquadmath
The quadmath library isn't needed at this time.
--enable-languages=c
This option ensures that only the C compiler is built.
--enable-checking=release
This option selects the complexity of the internal consistency checks and adds error checking within the compiler.
Continue with compiling the package:
make all-gcc all-target-libgcc
The meaning of the new make options:
all-gcc
all-target-libgcc
Compiles only the parts of GCC that are needed at this time, rather than the full package.
Install the package:
make install-gcc install-target-libgcc
Details on this package are located in Section 10.16.2, “Contents of GCC.”
The EGLIBC package contains the main C library. This library provides the basic routines for allocating memory, searching directories, opening and closing files, reading and writing files, string handling, pattern matching, arithmetic, and so on.
It should be noted that compiling EGLIBC in any way other than the method suggested in this book puts the stability of the system at risk.
The EGLIBC documentation recommends building EGLIBC outside of the source directory in a dedicated build directory:
mkdir -v ../eglibc-build cd ../eglibc-build
Add the following to config.cache
to disable ssp when building
EGLIBC:
echo "libc_cv_ssp=no" > config.cache
Prepare EGLIBC for compilation:
BUILD_CC="gcc" CC="${CLFS_TARGET}-gcc" \ AR="${CLFS_TARGET}-ar" RANLIB="${CLFS_TARGET}-ranlib" \ CFLAGS="-march=$(cut -d- -f1 <<< $CLFS_TARGET) -O2" \ ../eglibc-2.18/configure --prefix=/tools \ --host=${CLFS_TARGET} --build=${CLFS_HOST} \ --disable-profile --with-tls --enable-kernel=2.6.32 --with-__thread \ --with-binutils=/cross-tools/bin --with-headers=/tools/include \ --enable-obsolete-rpc --cache-file=config.cache
The meaning of the new configure options:
BUILD_CC="gcc"
This sets EGLIBC to use the current compiler on our system. This is used to create the tools EGLIBC uses during its build.
CC="${CLFS_TARGET}-gcc"
This forces EGLIBC to use the GCC compiler that we made for our target architecture.
AR="${CLFS_TARGET}-ar"
This forces EGLIBC to use the ar utility we made for our target architecture.
RANLIB="${CLFS_TARGET}-ranlib"
This forces EGLIBC to use the ranlib utility we made for our target architecture.
CFLAGS="-march=$(cut -d- -f1
<<< $CLFS_TARGET)" -O2
Forces EGLIBC to optimize for our target system.
--disable-profile
This builds the libraries without profiling information. Omit this option if profiling on the temporary tools is necessary.
--with-tls
This tells EGLIBC to use Thread Local Storage.
--enable-kernel=2.6.32
This tells EGLIBC to compile the library with support for 2.6.32 and later Linux kernels.
--with-__thread
This tells EGLIBC to use use the __thread for libc and libpthread builds.
--with-binutils=/cross-tools/bin
This tells EGLIBC to use the Binutils that are specific to our target architecture.
--with-headers=/tools/include
This tells EGLIBC to compile itself against the headers
recently installed to the /tools
directory, so that it knows
exactly what features the kernel has and can optimize
itself accordingly.
--cache-file=config.cache
This tells EGLIBC to utilize a premade cache file.
During this stage the following warning might appear:
configure: WARNING: *** These auxiliary programs are missing or *** incompatible versions: msgfmt *** some features will be disabled. *** Check the INSTALL file for required versions.
The missing or incompatible msgfmt program is generally harmless. This msgfmt program is part of the Gettext package which the host distribution should provide.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.7.5, “Contents of EGLIBC.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch contains a number of updates to the 4.8.1 branch by the GCC developers:
patch -Np1 -i ../gcc-4.8.1-branch_update-3.patch
Make a couple of essential adjustments to the specs
file to ensure GCC uses our build
environment:
patch -Np1 -i ../gcc-4.8.1-specs-1.patch
Change the StartFile Spec so that GCC looks in /tools
:
echo -en '\n#undef STANDARD_STARTFILE_PREFIX_1\n#define STANDARD_STARTFILE_PREFIX_1 "/tools/lib/"\n' >> gcc/config/linux.h echo -en '\n#undef STANDARD_STARTFILE_PREFIX_2\n#define STANDARD_STARTFILE_PREFIX_2 ""\n' >> gcc/config/linux.h
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
AR=ar LDFLAGS="-Wl,-rpath,/cross-tools/lib" \ ../gcc-4.8.1/configure --prefix=/cross-tools \ --build=${CLFS_HOST} --target=${CLFS_TARGET} --host=${CLFS_HOST} \ --with-sysroot=${CLFS} --with-local-prefix=/tools \ --with-native-system-header-dir=/tools/include --disable-nls \ --enable-shared --disable-static --enable-languages=c,c++ \ --enable-__cxa_atexit --enable-c99 --enable-long-long --enable-threads=posix \ --disable-multilib --with-mpc=/cross-tools --with-mpfr=/cross-tools \ --with-gmp=/cross-tools --with-cloog=/cross-tools \ --enable-cloog-backend=isl --with-isl=/cross-tools \ --disable-isl-version-check --with-system-zlib --enable-checking=release \ --enable-libstdcxx-time
The meaning of the new configure options:
--enable-languages=c,c++
This option ensures that only the C and C++ compilers are built.
--enable-__cxa_atexit
This option allows use of __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects and is essential for fully standards-compliant handling of destructors. It also affects the C++ ABI and therefore results in C++ shared libraries and C++ programs that are interoperable with other Linux distributions.
--enable-c99
Enable C99 support for C programs.
--enable-long-long
Enables long long support in the compiler.
--enable-threads=posix
This enables C++ exception handling for multi-threaded code.
Continue with compiling the package:
make AS_FOR_TARGET="${CLFS_TARGET}-as" \ LD_FOR_TARGET="${CLFS_TARGET}-ld"
Install the package:
make install
Details on this package are located in Section 10.16.2, “Contents of GCC.”
This chapter shows how to compile and install a minimal Linux system. This system will contain just enough tools to start constructing the final CLFS system in Installing Basic System Software and allow a working environment with more user convenience than a minimum environment would.
The tools in this chapter are cross-compiled using the
toolchain in /cross-tools
and
will be installed under the ${CLFS}/tools
directory to keep them separate
from the files installed in Installing
Basic System Software and the host production directories.
Since the packages compiled here are temporary, we do not want
them to pollute the soon-to-be CLFS system.
Check one last time that the CLFS
environment variable is set up properly:
echo ${CLFS}
Make sure the output shows the path to the CLFS partition's
mount point, which is /mnt/clfs
,
using our example.
During this section of the build you will see several WARNING messages like the one below. It is safe to ignore these messages.
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
Setup target-specific variables for the compiler and linkers:
export CC="${CLFS_TARGET}-gcc" export CXX="${CLFS_TARGET}-g++" export AR="${CLFS_TARGET}-ar" export AS="${CLFS_TARGET}-as" export RANLIB="${CLFS_TARGET}-ranlib" export LD="${CLFS_TARGET}-ld" export STRIP="${CLFS_TARGET}-strip"
Then add the build variables to ~/.bashrc
to prevent issues if you stop and
come back later:
echo export CC=\""${CC}\"" >> ~/.bashrc echo export CXX=\""${CXX}\"" >> ~/.bashrc echo export AR=\""${AR}\"" >> ~/.bashrc echo export AS=\""${AS}\"" >> ~/.bashrc echo export RANLIB=\""${RANLIB}\"" >> ~/.bashrc echo export LD=\""${LD}\"" >> ~/.bashrc echo export STRIP=\""${STRIP}\"" >> ~/.bashrc
GMP is a library for arithmetic on arbitrary precision integers, rational numbers, and floating-point numbers.
Prepare GMP for compilation:
HOST_CC=gcc ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --enable-cxx
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.9.2, “Contents of GMP.”
The MPFR library is a C library for multiple-precision floating-point computations with correct rounding.
Prepare MPFR for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --enable-shared
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.10.2, “Contents of MPFR.”
MPC is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result.
Prepare MPC for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.11.2, “Contents of MPC.”
ISL is a library for manipulating sets and relations of integer points bounded by linear constraints.
Prepare ISL for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --with-gmp-prefix=/tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.12.2, “Contents of ISL.”
CLooG is a library to generate code for scanning Z-polyhedra. In other words, it finds code that reaches each integral point of one or more parameterized polyhedra. GCC links with this library in order to enable the new loop generation code known as Graphite.
Prepare CLooG for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --with-gmp-prefix=/tools --with-isl-prefix=/tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.13.2, “Contents of CLooG.”
The Zlib package contains compression and decompression routines used by some programs.
Prepare Zlib for compilation:
./configure --prefix=/tools
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.14.2, “Contents of Zlib.”
The Binutils package contains a linker, an assembler, and other tools for handling object files.
Apply the following sed for hosts using Texinfo-5.x:
sed -i -e 's/@colophon/@@colophon/' \ -e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
../binutils-2.23.2/configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --target=${CLFS_TARGET} \ --with-lib-path=/tools/lib --disable-nls --enable-shared \ --disable-multilib
Compile the package:
make configure-host make
Install the package:
make install
Details on this package are located in Section 10.15.2, “Contents of Binutils.”
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch contains a number of updates to the 4.8.1 branch by the GCC developers:
patch -Np1 -i ../gcc-4.8.1-branch_update-3.patch
Make a couple of essential adjustments to the specs
file to ensure GCC uses our build
environment:
patch -Np1 -i ../gcc-4.8.1-specs-1.patch
Change the StartFile Spec so that GCC looks in /tools
:
echo -en '\n#undef STANDARD_STARTFILE_PREFIX_1\n#define STANDARD_STARTFILE_PREFIX_1 "/tools/lib/"\n' >> gcc/config/linux.h echo -en '\n#undef STANDARD_STARTFILE_PREFIX_2\n#define STANDARD_STARTFILE_PREFIX_2 ""\n' >> gcc/config/linux.h
Apply a sed subsitution that will suppress the execution of the fixincludes script:
cp -v gcc/Makefile.in{,.orig} sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig > gcc/Makefile.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Before starting to build GCC, remember to unset any environment variables that override the default optimization flags.
Prepare GCC for compilation:
../gcc-4.8.1/configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --target=${CLFS_TARGET} \ --libexecdir=/tools/lib --with-local-prefix=/tools --enable-long-long \ --enable-c99 --enable-shared --enable-threads=posix --disable-multilib \ --disable-nls --enable-__cxa_atexit --enable-languages=c,c++ \ --disable-libstdcxx-pch --enable-cloog-backend=isl --with-gmp=/tools \ --with-mpfr=/tools --with-mpc=/tools --with-isl=/tools \ --disable-isl-version-check --with-cloog=/tools --with-system-zlib \ --with-native-system-header-dir=/tools/include --disable-libssp \ --disable-install-libiberty --enable-checking=release \ --enable-libstdcxx-time
The meaning of the new configure options:
--disable-libstdcxx-pch
Do not build the pre-compiled header (PCH) for
libstdc++
. It takes up a
lot of space, and we have no use for it.
The following will prevent GCC from looking in the wrong directories for headers and libraries:
cp -v Makefile{,.orig} sed "/^HOST_\(GMP\|ISL\|CLOOG\)\(LIBS\|INC\)/s:/tools:/cross-tools:g" \ Makefile.orig > Makefile
Compile the package:
make AS_FOR_TARGET="${AS}" \ LD_FOR_TARGET="${LD}"
Install the package:
make install
Details on this package are located in Section 10.16.2, “Contents of GCC.”
The Ncurses package contains libraries for terminal-independent handling of character screens.
The following patch fixes an issue with some Bash versions:
patch -Np1 -i ../ncurses-5.9-bash_fix-1.patch
Prepare Ncurses for compilation:
./configure --prefix=/tools --with-shared \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --without-debug --without-ada \ --enable-overwrite --with-build-cc=gcc
The meaning of the new configure options:
--with-shared
This tells Ncurses to create a shared library.
--without-debug
This tells Ncurses not to build with debug information.
--without-ada
This ensures that Ncurses does not build support for the Ada compiler which may be present on the host but will not be available when building the final system.
--enable-overwrite
This tells Ncurses to install its header files into
/tools/include
, instead
of /tools/include/ncurses
, to ensure
that other packages can find the Ncurses headers
successfully.
--with-build-cc=gcc
This tells Ncurses what type of compiler we are using.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.18.2, “Contents of Ncurses.”
The Bash package contains the Bourne-Again SHell.
The following patch contains updates from the maintainer. The maintainer of Bash only releases these patches to fix serious issues:
patch -Np1 -i ../bash-4.2-branch_update-7.patch
When Bash is cross-compiled, it cannot test for the presence
of named pipes, among other things. If you used su to become an
unprivileged user, this combination will cause Bash to build
without process
substitution, which will break one of the C++
test scripts in eglibc
. The
following prevents future problems by skipping the check for
named pipes, as well as other tests that can not run while
cross-compiling or that do not run properly:
cat > config.cache << "EOF" ac_cv_func_mmap_fixed_mapped=yes ac_cv_func_strcoll_works=yes ac_cv_func_working_mktime=yes bash_cv_func_sigsetjmp=present bash_cv_getcwd_malloc=yes bash_cv_job_control_missing=present bash_cv_printf_a_format=yes bash_cv_sys_named_pipes=present bash_cv_ulimit_maxfds=yes bash_cv_under_sys_siglist=yes bash_cv_unusable_rtsigs=no gt_cv_int_divbyzero_sigfpe=yes EOF
Prepare Bash for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --without-bash-malloc --cache-file=config.cache
The meaning of the configure option:
--without-bash-malloc
This option turns off the use of Bash's memory allocation (malloc) function which is known to cause segmentation faults. By turning this option off, Bash will use the malloc functions from Glibc which are more stable.
Compile the package:
make
Install the package:
make install
Make a link for programs that use sh for a shell:
ln -sv bash /tools/bin/sh
Details on this package are located in Section 10.35.2, “Contents of Bash.”
The Bison package contains a parser generator.
Apply a sed
which disables the building of bison.help
when cross-compiling.
cp -v Makefile.in{,.orig} sed '/bison.help:/s/^/# /' Makefile.in.orig > Makefile.in
The configure script does not determine the correct value for the following. Set the value manually:
echo "ac_cv_prog_lex_is_flex=yes" > config.cache
Prepare Bison for compilation:
M4=m4 ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.27.2, “Contents of Bison.”
The Bzip2 package contains programs for compressing and decompressing files. Compressing text files with bzip2 yields a much better compression percentage than with the traditional gzip.
Bzip2's default Makefile
target
automatically runs the testsuite as well. Disable the tests
since they won't work on a multi-architecture build:
cp -v Makefile{,.orig} sed -e 's@^\(all:.*\) test@\1@g' Makefile.orig > Makefile
The Bzip2 package does not contain a configure script. Compile it with:
make CC="${CC}" AR="${AR}" RANLIB="${RANLIB}"
Install the package:
make PREFIX=/tools install
Details on this package are located in Section 10.37.2, “Contents of Bzip2.”
The Coreutils package contains utilities for showing and setting the basic system characteristics.
Configure can not properly determine how to get free space
when cross-compiling - as a result, the df program will not be
built. Add the following entries to config.cache
to correct this, and fix
various cross-compiling issues:
cat > config.cache << EOF fu_cv_sys_stat_statfs2_bsize=yes gl_cv_func_working_mkstemp=yes EOF
Prepare Coreutils for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --enable-install-program=hostname --cache-file=config.cache
The meaning of the new configure option:
--enable-install-program=hostname
Tells Coreutils to install hostname, which is needed for the Perl testsuite.
Apply a sed to allow completion of the build:
cp -v Makefile{,.orig} sed -e 's/^#run_help2man\|^run_help2man/#&/' \ -e 's/^\##run_help2man/run_help2man/' Makefile.orig > Makefile
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.24.2, “Contents of Coreutils.”
The Diffutils package contains programs that show the differences between files or directories.
Prepare Diffutils for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.38.2, “Contents of Diffutils.”
The Findutils package contains programs to find files. These programs are provided to recursively search through a directory tree and to create, maintain, and search a database (often faster than the recursive find, but unreliable if the database has not been recently updated).
The following cache entries set the values for tests that do not run while cross-compiling:
echo "gl_cv_func_wcwidth_works=yes" > config.cache echo "ac_cv_func_fnmatch_gnu=yes" >> config.cache
Prepare Findutils for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.41.2, “Contents of Findutils.”
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.39.2, “Contents of File.”
The Flex package contains a utility for generating programs that recognize patterns in text.
When cross compiling, the configure script does not determine the correct values for the following. Set the values manually:
cat > config.cache << EOF ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes EOF
Prepare Flex for compilation:
M4=m4 ./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.29.2, “Contents of Flex.”
The Gawk package contains programs for manipulating text files.
Apply a sed which will allow the build system to complete without error:
cp -v extension/Makefile.in{,.orig} sed -e 's/check-recursive all-recursive: check-for-shared-lib-support/check-recursive all-recursive:/' \ extension/Makefile.in.orig > extension/Makefile.in
Prepare Gawk for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.40.2, “Contents of Gawk.”
The Gettext package contains utilities for internationalization and localization. These allow programs to be compiled with NLS (Native Language Support), enabling them to output messages in the user's native language.
Only the programs in the gettext-tools
directory need to be
installed for the temp-system:
cd gettext-tools
When cross-compiling the Gettext configure script assumes we don't have a working wcwidth when we do. The following will fix possible compilation errors because of this assumption:
echo "gl_cv_func_wcwidth_works=yes" > config.cache
Prepare Gettext for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --disable-shared --cache-file=config.cache
The meaning of the configure options:
--disable-shared
This tells Gettext not to create a shared library.
Compile the package:
make -C gnulib-lib make -C src msgfmt
Install the msgfmt binary:
cp -v src/msgfmt /tools/bin
Details on this package are located in Section 10.42.2, “Contents of Gettext.”
The Grep package contains programs for searching through files.
When cross compiling, the configure script does not determine the correct values for the following. Set the values manually:
cat > config.cache << EOF ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes EOF
Prepare Grep for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --without-included-regex --cache-file=config.cache
The meaning of the new configure option:
--without-included-regex
When cross-compiling, Grep's configure assumes
there is no usable regex.h
installed and instead uses
the one included with Grep. This switch forces the use
of the regex functions from EGLIBC.
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.43.2, “Contents of Grep.”
The Gzip package contains programs for compressing and decompressing files.
Prepare Gzip for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.46.2, “Contents of Gzip.”
The M4 package contains a macro processor.
Configure can not properly determine the results of the following tests:
cat > config.cache << EOF gl_cv_func_btowc_eof=yes gl_cv_func_mbrtowc_incomplete_state=yes gl_cv_func_mbrtowc_sanitycheck=yes gl_cv_func_mbrtowc_null_arg=yes gl_cv_func_mbrtowc_retval=yes gl_cv_func_mbrtowc_nul_retval=yes gl_cv_func_wcrtomb_retval=yes gl_cv_func_wctob_works=yes EOF
Prepare M4 for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.26.2, “Contents of M4.”
The Make package contains a program for compiling packages.
Prepare Make for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.49.2, “Contents of Make.”
The Patch package contains a program for modifying or creating files by applying a “patch” file typically created by the diff program.
Prepare Patch for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.53.2, “Contents of Patch.”
The Sed package contains a stream editor.
Prepare Sed for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.17.2, “Contents of Sed.”
The Tar package contains an archiving program.
EGLIBC-2.18 does not declare gets():
sed -i -e '/gets is a/d' gnu/stdio.in.h
Configure can not properly determine the results of a few tests. Set them manually:
cat > config.cache << EOF gl_cv_func_wcwidth_works=yes gl_cv_func_btowc_eof=yes ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes gl_cv_func_mbrtowc_incomplete_state=yes gl_cv_func_mbrtowc_nul_retval=yes gl_cv_func_mbrtowc_null_arg=yes gl_cv_func_mbrtowc_retval=yes gl_cv_func_wcrtomb_retval=yes EOF
Prepare Tar for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --cache-file=config.cache
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.59.2, “Contents of Tar.”
The Texinfo package contains programs for reading, writing, and converting info pages.
Prepare Texinfo for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make -C tools/gnulib/lib make -C tools make
Install the package:
make install
Details on this package are located in Section 10.60.2, “Contents of Texinfo.”
The Vim package contains a powerful text editor.
The following patch merges all updates from the 7.4 Branch from the Vim developers:
patch -Np1 -i ../vim-7.4-branch_update-1.patch
The configure script is full of logic that aborts at the first sign of cross compiling. Work around this by setting the cached values of several tests with the following command:
cat > src/auto/config.cache << "EOF" vim_cv_getcwd_broken=no vim_cv_memmove_handles_overlap=yes vim_cv_stat_ignores_slash=no vim_cv_terminfo=yes vim_cv_toupper_broken=no vim_cv_tty_group=world EOF
Change the default location of the vimrc
configuration file to /tools/etc
:
echo '#define SYS_VIMRC_FILE "/tools/etc/vimrc"' >> src/feature.h
Prepare Vim for compilation:
./configure \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --prefix=/tools --enable-multibyte --enable-gui=no \ --disable-gtktest --disable-xim --with-features=normal \ --disable-gpm --without-x --disable-netbeans \ --with-tlib=ncurses
Compile the package:
make
Install the package:
make install
Many users are accustomed to using vi instead of vim. Some programs, such as vigr and vipw, also use vi. Create a symlink to permit execution of vim when users habitually enter vi and allow programs that use vi to work:
ln -sv vim /tools/bin/vi
Create a temporary vimrc to make it function more the way you may expect it to. This is explained more in the final system:
cat > /tools/etc/vimrc << "EOF"
" Begin /etc/vimrc
set nocompatible
set backspace=2
set ruler
syntax on
" End /etc/vimrc
EOF
Details on this package are located in Section 10.62.3, “Contents of Vim.”
The XZ-Utils package contains programs for compressing and decompressing files. Compressing text files with XZ-Utils yields a much better compression percentage than with the traditional gzip.
Prepare XZ-Utils for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET}
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.50.2, “Contents of XZ-Utils.”
There are two different ways you can proceed from this point to build the final system. You can build a kernel, a bootloader, and a few other utilities, boot into the temporary system, and build the rest there. Alternatively, you can chroot into the temporary system.
The boot method is needed when you are building on a different architecture. For example, if you are building a PowerPC system from an x86, you can't chroot. The chroot method is for when you are building on the same architecture. If you are building on, and for, an x86 system, you can simply chroot. The rule of thumb here is if the architectures match and you are running the same series kernel you can just chroot. If you aren't running the same series kernel, or are wanting to run a different ABI, you will need to use the boot option.
If you are in any doubt about this, you can try the following commands to see if you can chroot:
/tools/lib/libc.so.6 /tools/bin/gcc -v
If either of these commands fail, you will have to follow the boot method.
To chroot, you will also need a Linux Kernel-2.6.32 or greater (having been compiled with GCC-4.1.2 or greater). The reason for the kernel version requirement is that eglibc is built to generate the library for the smallest version of the Linux kernel expected to be supported.
To check your kernel version, run cat /proc/version - if it does not say that you are running a 2.6.32 or later Linux kernel, compiled with GCC 4.1.2 or later, you cannot chroot.
For the boot method, follow If You Are Going to Boot.
For the chroot method, follow If You Are Going to Chroot.
This chapter shows how to complete the build of temporary tools to create a minimal system that will be used to boot the target machine and to build the final system packages.
There are a few additional packages that will need to be
installed to allow you to boot the minimal system. Some of
these packages will be installed onto root or in /usr on the
CLFS partition (${CLFS}/bin, ${CLFS}/usr/bin, etc...), rather
than /tools, using the "DESTDIR" option with make. This will
require the clfs
user to have
write access to the rest of the CLFS partition, so you will
need to temporarily change the ownership of ${CLFS} to the
clfs
user. Run the following
command as root
:
chown -v clfs ${CLFS}
It is time to create some structure in the CLFS file system. Create a standard directory tree by issuing the following commands:
mkdir -pv ${CLFS}/{bin,boot,dev,{etc/,}opt,home,lib,mnt} mkdir -pv ${CLFS}/{proc,media/{floppy,cdrom},run/{,shm},sbin,srv,sys} mkdir -pv ${CLFS}/var/{lock,log,mail,spool} mkdir -pv ${CLFS}/var/{opt,cache,lib/{misc,locate},local} install -dv -m 0750 ${CLFS}/root install -dv -m 1777 ${CLFS}{/var,}/tmp mkdir -pv ${CLFS}/usr/{,local/}{bin,include,lib,sbin,src} mkdir -pv ${CLFS}/usr/{,local/}share/{doc,info,locale,man} mkdir -pv ${CLFS}/usr/{,local/}share/{misc,terminfo,zoneinfo} mkdir -pv ${CLFS}/usr/{,local/}share/man/man{1,2,3,4,5,6,7,8} for dir in ${CLFS}/usr{,/local}; do ln -sv share/{man,doc,info} $dir done
Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands
above, two changes are made—one to the home directory of
user root
, and another to the
directories for temporary files.
The first mode change ensures that not just anybody can enter
the /root
directory—the
same as a normal user would do with his or her home directory.
The second mode change makes sure that any user can write to
the /tmp
and /var/tmp
directories, but cannot remove
another user's files from them. The latter is prohibited by the
so-called “sticky bit,”
the highest bit (1) in the 1777 bit mask.
The directory tree is based on the Filesystem Hierarchy
Standard (FHS) (available at http://www.pathname.com/fhs/).
In addition to the tree created above, this standard
stipulates the existence of /usr/local/games
and /usr/share/games
. The FHS is not precise as
to the structure of the /usr/local/share
subdirectory, so we create
only the directories that are needed. However, feel free to
create these directories if you prefer to conform more
strictly to the FHS.
Some programs use hard-wired paths to programs which do not exist yet. In order to satisfy these programs, create a number of symbolic links which will be replaced by real files throughout the course of the next chapter after the software has been installed.
ln -sv /tools/bin/{bash,cat,echo,grep,login,passwd,pwd,sleep,stty} ${CLFS}/bin ln -sv /tools/sbin/{agetty,blkid} ${CLFS}/sbin ln -sv /tools/bin/file ${CLFS}/usr/bin ln -sv /tools/lib/libgcc_s.so{,.1} ${CLFS}/usr/lib ln -sv /tools/lib/libstd*so* ${CLFS}/usr/lib ln -sv bash ${CLFS}/bin/sh ln -sv /run ${CLFS}/var/run
The Util-linux package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
Prepare Util-linux for compilation:
PKG_CONFIG=true \ ./configure --prefix=/tools --exec-prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --disable-makeinstall-chown --disable-login --disable-su
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.20.3, “Contents of Util-linux.”
The Shadow package contains programs for handling passwords in a secure way.
Disable the installation of the groups program, as Coreutils provides a better version:
cp -v src/Makefile.in{,.orig} sed -e 's/groups$(EXEEXT) //' src/Makefile.in.orig > src/Makefile.in
Prepare Shadow for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --sysconfdir=/etc
The meaning of the configure options:
--sysconfdir=/etc
Tells Shadow to install its configuration files into
/etc
, rather than
/tools/etc
.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.23.4, “Contents of Shadow.”
The E2fsprogs package contains the utilities for handling the
ext2
file system. It also
supports the ext3
and
ext4
journaling file systems.
The E2fsprogs documentation recommends that the package be built in a subdirectory of the source tree:
mkdir -v build cd build
Prepare E2fsprogs for compilation:
PKG_CONFIG=true \ ../configure --prefix=/tools \ --enable-elf-shlibs --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --disable-libblkid --disable-libuuid --disable-fsck \ --disable-uuidd
The meaning of the configure options:
--enable-elf-shlibs
This creates the shared libraries which some programs in this package use.
Compile the package:
make LIBUUID="-luuid" STATIC_LIBUUID="-luuid" \ LIBBLKID="-lblkid" STATIC_LIBBLKID="-lblkid"
Install the binaries, documentation and shared libraries:
make install
Install the static libraries and headers:
make install-libs
Create needed symlinks for a bootable system:
ln -sv /tools/sbin/{fsck.ext2,fsck.ext3,fsck.ext4,e2fsck} ${CLFS}/sbin
Details on this package are located in Section 10.22.2, “Contents of E2fsprogs.”
The Sysvinit package contains programs for controlling the startup, running, and shutdown of the system.
The following modifications help locate files specific to this particular build:
cp -v src/Makefile{,.orig} sed -e 's,/usr/lib,/tools/lib,g' \ src/Makefile.orig > src/Makefile
Compile the package:
make -C src clobber make -C src CC="${CC}"
Install the package:
make -C src ROOT=${CLFS} install
Create a new file ${CLFS}/etc/inittab
by running the
following:
cat > ${CLFS}/etc/inittab << "EOF"
# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc sysinit
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016:once:/sbin/sulogin
EOF
The following command adds the standard virtual terminals to
${CLFS}/etc/inittab
. If your
system only has a serial console skip the following command:
cat >> ${CLFS}/etc/inittab << "EOF"
1:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty1 9600
2:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty2 9600
3:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty3 9600
4:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty4 9600
5:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty5 9600
6:2345:respawn:/sbin/agetty --noclear -I '\033(K' tty6 9600
EOF
If your system has a serial console, run the following
command to add the entry to ${CLFS}/etc/inittab
.
cat >> ${CLFS}/etc/inittab << "EOF"
c0:12345:respawn:/sbin/agetty --noclear 115200 ttyS0 vt100
EOF
Finally, add the end line to ${CLFS}/etc/inittab
.
cat >> ${CLFS}/etc/inittab << "EOF"
# End /etc/inittab
EOF
Details on this package are located in Section 10.58.3, “Contents of Sysvinit.”
The Kmod package contains programs for loading, inserting and removing kernel modules for Linux. Kmod replaces the Module-Init-tools package.
Prepare Kmod for compilation:
liblzma_CFLAGS="-I/tools/include" liblzma_LIBS="-L/tools/lib -llzma" \ zlib_CFLAGS="-I/tools/include" zlib_LIBS="-L/tools/lib -lz" \ ./configure --prefix=/tools --bindir=/bin \ --build=${CLFS_HOST} --host=${CLFS_TARGET} --with-xz --with-zlib \ --disable-manpages
Compile the package:
make
Install the package:
make DESTDIR=${CLFS} install
Create symbolic links for programs that expect Module-Init-Tools.
ln -sv kmod ${CLFS}/bin/lsmod ln -sv ../bin/kmod ${CLFS}/sbin/depmod ln -sv ../bin/kmod ${CLFS}/sbin/insmod ln -sv ../bin/kmod ${CLFS}/sbin/modprobe ln -sv ../bin/kmod ${CLFS}/sbin/modinfo ln -sv ../bin/kmod ${CLFS}/sbin/rmmod
Details on this package are located in Section 10.52.2, “Contents of Kmod.”
The Eudev package contains programs for dynamic creation of device nodes.
Prepare Eudev for compilation:
BLKID_CFLAGS="-I/tools/include" BLKID_LIBS="-L/tools/lib -lblkid" \ KMOD_CFLAGS="-I/tools/include/" KMOD_LIBS="-L/tools/lib -lkmod" \ LDFLAGS="-Wl,-rpath,/tools/lib:/lib" ./configure --prefix=/usr \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --with-rootprefix='' --enable-split-usr --sysconfdir=/etc \ --libexecdir=/lib --bindir=/sbin --sbindir=/sbin --libdir=/usr/lib \ --with-rootlibdir=/lib --disable-introspection --disable-gtk-doc-html \ --disable-gudev --disable-keymap --with-firmware-path=/lib/firmware \ --enable-libkmod
Compile the package:
make
Install the package:
make DESTDIR=${CLFS} install
Create a directory for storing firmware that can be loaded by udev:
install -dv ${CLFS}/lib/firmware
Create a dummy rule so that Eudev will name ethernet devices properly for the system.
echo "# dummy, so that network is once again on eth*" \ > ${CLFS}/etc/udev/rules.d/80-net-name-slot.rules
Details on this package are located in Section 10.61.2, “Contents of Eudev.”
In order for user root
to be
able to login and for the name “root” to be recognized, there must be
relevant entries in the /etc/passwd
and /etc/group
files.
Create the ${CLFS}/etc/passwd
file by running the following command:
cat > ${CLFS}/etc/passwd << "EOF"
root::0:0:root:/root:/bin/bash
EOF
The actual password for root
(the “::” used here is
just a placeholder and allows you to login with no password)
will be set later.
Additional users you may want to add:
bin:x:1:1:bin:/bin:/bin/false
Can be useful for compatibility with legacy applications.
daemon:x:2:6:daemon:/sbin:/bin/false
It is often recommended to use an unprivileged User ID/Group ID for daemons to run as, in order to limit their access to the system.
adm:x:3:16:adm:/var/adm:/bin/false
Was used for programs that performed administrative tasks.
lp:x:10:9:lp:/var/spool/lp:/bin/false
Used by programs for printing
mail:x:30:30:mail:/var/mail:/bin/false
Often used by email programs
news:x:31:31:news:/var/spool/news:/bin/false
Often used for network news servers
operator:x:50:0:operator:/root:/bin/bash
Often used to allow system operators to access the system
postmaster:x:51:30:postmaster:/var/spool/mail:/bin/false
Generally used as an account that receives all the information of troubles with the mail server
nobody:x:65534:65534:nobody:/:/bin/false
Used by NFS
Create the ${CLFS}/etc/group
file
by running the following command:
cat > ${CLFS}/etc/group << "EOF"
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:5:
tape:x:4:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
video:x:12:
utmp:x:13:
usb:x:14:
cdrom:x:15:
EOF
Additional groups you may want to add
adm:x:16:root,adm,daemon
All users in this group are allowed to do administrative tasks
console:x:17:
This group has direct access to the console
cdrw:x:18:
This group is allowed to use the CDRW drive
mail:x:30:mail
Used by MTAs (Mail Transport Agents)
news:x:31:news
Used by Network News Servers
users:x:1000:
The default GID used by shadow for new users
nogroup:x:65533:
This is a default group used by some programs that do not require a group
nobody:x:65534:
This is used by NFS
The created groups are not part of any standard—they are groups decided on in part by the requirements of the Eudev configuration in the final system, and in part by common convention employed by a number of existing Linux distributions. The Linux Standard Base (LSB, available at http://www.linuxbase.org) recommends only that, besides the group “root” with a Group ID (GID) of 0, a group “bin” with a GID of 1 be present. All other group names and GIDs can be chosen freely by the system administrator since well-written programs do not depend on GID numbers, but rather use the group's name.
The login, agetty, and init programs (and others) use a number of log files to record information such as who was logged into the system and when. However, these programs will not write to the log files if they do not already exist. Initialize the log files and give them proper permissions:
touch ${CLFS}/var/run/utmp ${CLFS}/var/log/{btmp,lastlog,wtmp} chmod -v 664 ${CLFS}/var/run/utmp ${CLFS}/var/log/lastlog chmod -v 600 ${CLFS}/var/log/btmp
The /var/run/utmp
file records
the users that are currently logged in. The /var/log/wtmp
file records all logins and
logouts. The /var/log/lastlog
file records when each user last logged in. The /var/log/btmp
file records the bad login
attempts.
The Linux package contains the Linux kernel.
Here a temporary cross-compiled kernel will be built. When configuring it, select the minimal amount of options required to boot the target machine and build the final system. I.e., no support for sound, printers, etc. will be needed.
Also, try to avoid the use of modules if possible, and don't use the resulting kernel image for production systems.
Building the kernel involves a few steps—configuration,
compilation, and installation. Read the README
file in the kernel source tree for
alternative methods to the way this book configures the
kernel.
Prepare for compilation by running the following command:
make mrproper
This ensures that the kernel tree is absolutely clean. The kernel team recommends that this command be issued prior to each kernel compilation. Do not rely on the source tree being clean after un-tarring.
Configure the kernel via a menu-driven interface:
make ARCH=i386 CROSS_COMPILE=${CLFS_TARGET}- menuconfig
Compile the kernel image and modules:
make ARCH=i386 CROSS_COMPILE=${CLFS_TARGET}-
If the use of kernel modules can't be avoided, an
/etc/modprobe.conf
file may be
needed. Information pertaining to modules and kernel
configuration is located in the kernel documentation in the
Documentation
directory of the
kernel sources tree. The modprobe.conf
man page may also be of
interest.
Be very careful when reading other documentation relating to
kernel modules because it usually applies to 2.4.x kernels
only. As far as we know, kernel configuration issues specific
to Hotplug and Eudev are not documented. The problem is that
Eudev will create a device node only if Hotplug or a
user-written script inserts the corresponding module into the
kernel, and not all modules are detectable by Hotplug. Note
that statements like the one below in the /etc/modprobe.conf
file do not work with
Eudev:
alias char-major-XXX some-module
Install the modules, if the kernel configuration uses them:
make ARCH=i386 CROSS_COMPILE=${CLFS_TARGET}- \ INSTALL_MOD_PATH=${CLFS} modules_install
Install the firmware, if the kernel configuration uses them:
make ARCH=i386 CROSS_COMPILE=${CLFS_TARGET}- \ INSTALL_FW_PATH=${CLFS}/lib/firmware firmware_install
After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be
copied to the ${CLFS}/boot
directory.
Issue the following command to install the kernel:
cp -v arch/i386/boot/bzImage ${CLFS}/boot/vmlinuz-clfs-3.10.14
System.map
is a symbol file for
the kernel. It maps the function entry points of every
function in the kernel API, as well as the addresses of the
kernel data structures for the running kernel. Issue the
following command to install the map file:
cp -v System.map ${CLFS}/boot/System.map-3.10.14
The kernel configuration file .config
produced by the make menuconfig step above
contains all the configuration selections for the kernel that
was just compiled. It is a good idea to keep this file for
future reference:
cp -v .config ${CLFS}/boot/config-3.10.14
Details on this package are located in Section 13.3.2, “Contents of Linux.”
The GRUB package contains the GRand Unified Bootloader.
If you would like use a different bootloader than this one you can go to the following link for alterative bootloaders and the instructions to use them. http://trac.cross-lfs.org/wiki/bootloaders
EGLIBC-2.18 does not declare gets():
sed -i -e '/gets is a/d' grub-core/gnulib/stdio.in.h
Prepare GRUB for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --sysconfdir=/etc --disable-werror
Compile the package:
make
Install the package:
make DESTDIR=${CLFS} install
Details on this package are located in Section 10.63.3, “Contents of GRUB.”
The new instance of the shell that will start when the system
is booted is a login
shell, which will read .bash_profile
file. Create the .bash_profile
file now:
cat > ${CLFS}/root/.bash_profile << "EOF"
set +h
PS1='\u:\w\$ '
LC_ALL=POSIX
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin:/tools/sbin
export LC_ALL PATH PS1
EOF
The LC_ALL
variable controls the
localization of certain programs, making their messages follow
the conventions of a specified country. Setting LC_ALL
to “POSIX” or “C” (the two are equivalent) ensures that
everything will work as expected on your temporary system.
By putting /tools/bin
and
/tools/sbin
at the end of the
standard PATH
, all the programs
installed in Constructing
a Temporary System are only picked up by the shell if they
have not yet been built on the target system. This
configuration forces use of the final system binaries as they
are built over the temp-system, minimising the chance of final
system programs being built against the temp-system.
The /etc/fstab
file is used by
some programs to determine where file systems are to be mounted
by default, which must be checked, and in which order. Create a
new file systems table like this:
cat > ${CLFS}/etc/fstab << "EOF"
# Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/[xxx]
/ [fff]
defaults 1 1
/dev/[yyy]
swap swap pri=1 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
# End /etc/fstab
EOF
Replace [xxx]
,
[yyy]
, and [fff]
with the values
appropriate for the system, for example, hda2
, hda5
, and
ext2
. For details on the six
fields in this file, see man 5
fstab.
The /dev/shm
mount point for
tmpfs
is included to allow
enabling POSIX-shared memory. The kernel must have the required
support built into it for this to work (more about this is in
the next section). Please note that very little software
currently uses POSIX-shared memory. Therefore, consider the
/dev/shm
mount point optional.
For more information, see Documentation/filesystems/tmpfs.txt
in the
kernel source tree.
The Bootscripts package contains a set of scripts to start/stop the CLFS system at bootup/shutdown.
Install the package:
make DESTDIR=${CLFS} install-minimal
The setclock
script reads the time from the hardware clock, also known as
the BIOS or the Complementary Metal Oxide Semiconductor
(CMOS) clock. If the hardware clock is set to UTC, this
script will convert the hardware clock's time to the local
time using the /etc/localtime
file (which tells the hwclock program which
timezone the user is in). There is no way to detect whether
or not the hardware clock is set to UTC, so this needs to be
configured manually.
If you do not know whether or not the hardware clock is set
to UTC, you can find out after you have booted the new
machine by running the hwclock --localtime --show
command, and if necessary editing the /etc/sysconfig/clock
script. The worst that
will happen if you make a wrong guess here is that the time
displayed will be wrong.
Change the value of the UTC
variable below to a value of 0
(zero) if the hardware clock is not set to UTC time.
cat > ${CLFS}/etc/sysconfig/clock << "EOF"
# Begin /etc/sysconfig/clock
UTC=1
# End /etc/sysconfig/clock
EOF
Details on this package are located in Section 11.2.2, “Contents of Bootscripts.”
The commands in the remainder of the book should be run as
the root
user. Check that
${CLFS} is set in the root
user’s environment before proceeding.
When the kernel boots the system, it requires the presence of
a few device nodes, in particular the console
and null
devices. The device nodes will be
created on the hard disk so that they are available before
udev has been
started, and additionally when Linux is started in single
user mode (hence the restrictive permissions on console
). Create these by running the
following commands:
mknod -m 600 ${CLFS}/dev/console c 5 1 mknod -m 666 ${CLFS}/dev/null c 1 3
Before udev starts, a tmpfs filesystem is mounted over
/dev
and the previous entries
are no longer available. The following command creates files
that are copied over by the udev bootscript:
mknod -m 600 ${CLFS}/lib/udev/devices/console c 5 1 mknod -m 666 ${CLFS}/lib/udev/devices/null c 1 3
Currently, the ${CLFS}
directory
and all of its subdirectories are owned by the user
clfs
, a user that exists only
on the host system. For security reasons, the ${CLFS} root
directory and all of its subdirectories should be owned by
root
. Change the ownership for
${CLFS} and its subdirectories by running this command:
chown -Rv 0:0 ${CLFS}
The following files are to be owned by the group utmp
not by root
.
chgrp -v 13 ${CLFS}/var/run/utmp ${CLFS}/var/log/lastlog
This chapter shows how to prepare a chroot jail to build the final system packages into.
The Util-linux package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
Prepare Util-linux for compilation:
./configure --prefix=/tools \ --build=${CLFS_HOST} --host=${CLFS_TARGET} \ --disable-makeinstall-chown --disable-su --disable-login
Compile the package:
make
Install the package:
make install
Details on this package are located in Section 10.20.3, “Contents of Util-linux.”
The commands in the remainder of the book should be run as
the root
user. Check that
${CLFS} is set in the root
user’s environment before proceeding.
Various file systems exported by the kernel are used to communicate to and from the kernel itself. These file systems are virtual in that no disk space is used for them. The content of the file systems resides in memory.
Begin by creating directories onto which the file systems will be mounted:
mkdir -pv ${CLFS}/{dev,proc,sys}
Now mount the file systems:
mount -vt proc proc ${CLFS}/proc mount -vt sysfs sysfs ${CLFS}/sys
Remember that if for any reason you stop working on the CLFS system and start again later, it is important to check that these file systems are mounted again before entering the chroot environment.
Two device nodes, /dev/console and /dev/null, are required to be present on the filesystem. These are needed by the kernel even before starting Eudev early in the boot process, so we create them here:
mknod -m 600 ${CLFS}/dev/console c 5 1 mknod -m 666 ${CLFS}/dev/null c 1 3
Once the system is complete and booting, the rest of our device nodes are created by the Eudev package. Since this package is not available to us right now, we must take other steps to provide device nodes under on the CLFS filesystem. We will use the “bind” option in the mount command to make our host system's /dev structure appear in the new CLFS filesystem:
mount -v -o bind /dev ${CLFS}/dev
Additional file systems will soon be mounted from within the chroot environment. To keep the host up to date, perform a “fake mount” for each of these now:
if [ -h ${CLFS}/dev/shm ]; then link=$(readlink ${CLFS}/dev/shm) mkdir -p ${CLFS}/$link mount -f -vt tmpfs shm ${CLFS}/$link unset link else mount -f -vt tmpfs shm ${CLFS}/dev/shm fi mount -f -vt devpts -o gid=5,mode=620 devpts ${CLFS}/dev/pts
Before we can enter the chroot we have to make sure that the
system is in the proper state. From this point on the
${CLFS_TARGET}
environment
variable will no longer exist, so it will have no bearing on
the rest of the book - most packages will rely on
config.guess
provided by Section 10.34,
“Automake-1.12.4”. Packages that do not use
autotools either do not care about the target triplet, or
have their own means of determining its value.
In both cases, the information about the host cpu used to determine the target triplet is gathered from the same place, uname -m. Executing this command outside of the chroot as well as inside the chroot will have the exact same output.
If you're unsure if your host and target have the same target triplet, you can use this test to determine what the host's target triplet is and if you need to take any steps to ensure that you don't build for the wrong architecture. Extract the Section 10.34, “Automake-1.12.4” tarball and cd into the created directory. Then execute the following to see what the detected target triplet is by config.guess:
build-aux/config.guess
If the output of that command does not equal what is in
${CLFS_TARGET}
then you need to
read on. If it does then you can safely continue onto
Section 8.5,
“Entering the Chroot Environment”.
If your host has a tool called setarch this may solve your problems. The reason for saying may is because on a architecture such as x86_64, using setarch linux32 uname -m will only ever output i686. It is not possible to get an output of i486 or i586.
To test if setarch does everything you need it to, execute the following command from inside the Section 10.34, “Automake-1.12.4” directory:
setarch linux32 build-aux/config.guess
If the output of the command above equals what is in
${CLFS_TARGET}
then you have a
viable solution. You can wrap the chroot command on the next
page with setarch
linux32. It will look like the following:
setarch linux32 chroot "${CLFS}" /tools/bin/env -i \ HOME=/root TERM="${TERM}" PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h
If setarch works for you then you can safely continue onto Section 8.5, “Entering the Chroot Environment”. If not, there is one more option covered in this book.
The Uname Hack is a kernel module that modifies the output of uname -m by directly changing the value of the detected machine type. The kernel module will save the original value and restore it when the module is unloaded.
Download: http://cross-lfs.org/files/extras/uname_hack-20080713.tar.bz2
MD5 sum: dd7694f28ccc6e6bfb326b1790adb5e9
Extract the tarball and cd into the created directory. To build the Uname Hack you must have the kernel sources for your currently running kernel available. Build the Uname Hack with the following or similar command:
make uname_hack_fake_machine=i486
The meaning of the make and install options:
uname_hack_fake_machine=i486
This parameter sets the value that the uts machine type will be changed to. Alternatively this could be set to i586 or i686.
In the top level directory of the Uname Hack package you
should see a file named uname_hack.ko
. As soon as that module is
loaded into the running kernel the output of uname -m will be affected
immediately system-wide. Load the kernel module with the
following command:
insmod uname_hack.ko
To test if the Uname Hack is working properly, execute the following command from inside the Section 10.34, “Automake-1.12.4” directory:
build-aux/config.guess
The output of the above command should be the same as the
${CLFS_TARGET}
environment
variable. If this is not the case, you can try and get help
on the CLFS Support Mailing List or the IRC Channel. See
Section 1.6, “Help” for
more information.
It is time to enter the chroot environment to begin building
and installing the final CLFS system. As user root
, run the following command to enter
the realm that is, at the moment, populated with only the
temporary tools:
chroot "${CLFS}" /tools/bin/env -i \ HOME=/root TERM="${TERM}" PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h
The -i
option given to
the env command
will clear all variables of the chroot environment. After that,
only the HOME
, TERM
, PS1
, and
PATH
variables are set again. The
TERM=${TERM}
construct
will set the TERM
variable inside
chroot to the same value as outside chroot. This variable is
needed for programs like vim and less to operate properly. If
other variables are needed, such as CFLAGS
or CXXFLAGS
,
this is a good place to set them again.
From this point on, there is no need to use the CLFS
variable anymore, because all work will be
restricted to the CLFS file system. This is because the Bash
shell is told that ${CLFS}
is now
the root (/
) directory.
Notice that /tools/bin
comes last
in the PATH
. This means that a
temporary tool will no longer be used once its final version is
installed. This occurs when the shell does not
“remember” the locations
of executed binaries—for this reason, hashing is switched
off by passing the +h
option to bash.
It is important that all the commands throughout the remainder
of this chapter and the following chapters are run from within
the chroot environment. If you leave this environment for any
reason (rebooting for example), remember to first mount the
proc
and devpts
file systems (discussed in the
previous section) and enter chroot again before continuing with
the installations.
Note that the bash prompt will say
I have no name!
This is
normal because the /etc/passwd
file has not been created yet.
This step is not optional as some of the binaries in
/tools
are set u+s. leaving the
permissions as is could cause some commands, mount in
particular, to fail later.
Currently, the /tools
and
/cross-tools
directories are
owned by the user clfs,
a user that exists only on the host system. Although the
/tools
and /cross-tools
directories can be deleted once
the CLFS system has been finished, they can be retained to
build additional CLFS systems. If the /tools
and /cross-tools
directories are kept as is, the
files are owned by a user ID without a corresponding account.
This is dangerous because a user account created later could
get this same user ID and would own the /tools
directory and all the files therein,
thus exposing these files to possible malicious manipulation.
To avoid this issue, add the clfs
user to the new CLFS system later when
creating the /etc/passwd
file,
taking care to assign it the same user and group IDs as on the
host system. Alternatively, assign the contents of the
/tools
and /cross-tools
directories to user root
by running the following commands:
chown -Rv 0:0 /tools chown -Rv 0:0 /cross-tools
The commands use 0:0
instead of root:root
,
because chown is
unable to resolve the name “root” until the passwd
file has been created.
It is time to create some structure in the CLFS file system. Create a standard directory tree by issuing the following commands:
mkdir -pv /{bin,boot,dev,{etc/,}opt,home,lib,mnt} mkdir -pv /{proc,media/{floppy,cdrom},run/shm,sbin,srv,sys} mkdir -pv /var/{lock,log,mail,spool} mkdir -pv /var/{opt,cache,lib/{misc,locate},local} install -dv -m 0750 /root install -dv -m 1777 {/var,}/tmp mkdir -pv /usr/{,local/}{bin,include,lib,sbin,src} mkdir -pv /usr/{,local/}share/{doc,info,locale,man} mkdir -pv /usr/{,local/}share/{misc,terminfo,zoneinfo} mkdir -pv /usr/{,local/}share/man/man{1..8} for dir in /usr{,/local}; do ln -sv share/{man,doc,info} $dir done
Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands
above, two changes are made—one to the home directory of
user root
, and another to the
directories for temporary files.
The first mode change ensures that not just anybody can enter
the /root
directory—the
same as a normal user would do with his or her home directory.
The second mode change makes sure that any user can write to
the /tmp
and /var/tmp
directories, but cannot remove
another user's files from them. The latter is prohibited by the
so-called “sticky bit,”
the highest bit (1) in the 1777 bit mask.
The directory tree is based on the Filesystem Hierarchy
Standard (FHS) (available at http://www.pathname.com/fhs/).
In addition to the tree created above, this standard
stipulates the existence of /usr/local/games
and /usr/share/games
. The FHS is not precise as
to the structure of the /usr/local/share
subdirectory, so we create
only the directories that are needed. However, feel free to
create these directories if you prefer to conform more
strictly to the FHS.
Some programs use hard-wired paths to programs which do not exist yet. In order to satisfy these programs, create a number of symbolic links which will be replaced by real files throughout the course of the next chapter after the software has been installed.
ln -sv /tools/bin/{bash,cat,echo,grep,pwd,stty} /bin ln -sv /tools/bin/file /usr/bin ln -sv /tools/lib/libgcc_s.so{,.1} /usr/lib ln -sv /tools/lib/libstd* /usr/lib ln -sv bash /bin/sh ln -sv /run /var/run
In order for user root
to be
able to login and for the name “root” to be recognized, there must be
relevant entries in the /etc/passwd
and /etc/group
files.
Create the /etc/passwd
file by
running the following command:
cat > /etc/passwd << "EOF"
root:x:0:0:root:/root:/bin/bash
EOF
The actual password for root
(the “x” used here is
just a placeholder) will be set later.
Additional users you may want to add:
bin:x:1:1:bin:/bin:/bin/false
Can be useful for compatibility with legacy applications.
daemon:x:2:6:daemon:/sbin:/bin/false
It is often recommended to use an unprivileged User ID/Group ID for daemons to run as, in order to limit their access to the system.
adm:x:3:16:adm:/var/adm:/bin/false
Was used for programs that performed administrative tasks.
lp:x:10:9:lp:/var/spool/lp:/bin/false
Used by programs for printing
mail:x:30:30:mail:/var/mail:/bin/false
Often used by email programs
news:x:31:31:news:/var/spool/news:/bin/false
Often used for network news servers
operator:x:50:0:operator:/root:/bin/bash
Often used to allow system operators to access the system
postmaster:x:51:30:postmaster:/var/spool/mail:/bin/false
Generally used as an account that receives all the information of troubles with the mail server
nobody:x:65534:65534:nobody:/:/bin/false
Used by NFS
Create the /etc/group
file by
running the following command:
cat > /etc/group << "EOF"
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:5:
tape:x:4:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
video:x:12:
utmp:x:13:
usb:x:14:
cdrom:x:15:
EOF
Additional groups you may want to add
adm:x:16:root,adm,daemon
All users in this group are allowed to do administrative tasks
console:x:17:
This group has direct access to the console
cdrw:x:18:
This group is allowed to use the CDRW drive
mail:x:30:mail
Used by MTAs (Mail Transport Agents)
news:x:31:news
Used by Network News Servers
users:x:1000:
The default GID used by shadow for new users
nogroup:x:65533:
This is a default group used by some programs that do not require a group
nobody:x:65534:
This is used by NFS
The created groups are not part of any standard—they are groups decided on in part by the requirements of the Eudev configuration in the final system, and in part by common convention employed by a number of existing Linux distributions. The Linux Standard Base (LSB, available at http://www.linuxbase.org) recommends only that, besides the group “root” with a Group ID (GID) of 0, a group “bin” with a GID of 1 be present. All other group names and GIDs can be chosen freely by the system administrator since well-written programs do not depend on GID numbers, but rather use the group's name.
To remove the “I have no
name!” prompt, start a new shell. Since a full
Glibc was installed in Constructing
Cross-Compile Tools and the /etc/passwd
and /etc/group
files have been created, user name
and group name resolution will now work.
exec /tools/bin/bash --login +h
Note the use of the +h
directive. This tells bash not to use its internal
path hashing. Without this directive, bash would remember the paths
to binaries it has executed. To ensure the use of the newly
compiled binaries as soon as they are installed, the +h
directive will be used for the
duration of the next chapters.
The login, agetty, and init programs (and others) use a number of log files to record information such as who was logged into the system and when. However, these programs will not write to the log files if they do not already exist. Initialize the log files and give them proper permissions:
touch /var/run/utmp /var/log/{btmp,lastlog,wtmp} chgrp -v utmp /var/run/utmp /var/log/lastlog chmod -v 664 /var/run/utmp /var/log/lastlog chmod -v 600 /var/log/btmp
The /var/run/utmp
file records
the users that are currently logged in. The /var/log/wtmp
file records all logins and
logouts. The /var/log/lastlog
file records when each user last logged in. The /var/log/btmp
file records the bad login
attempts.
Mount the proper virtual (kernel) file systems on the newly-created directories:
mount -vt devpts -o gid=5,mode=620 none /dev/pts mount -vt tmpfs none /dev/shm
The mount commands executed above may result in the following warning message:
can't open /etc/fstab: No such file or directory.
This file—/etc/fstab
—has not been created yet
(unless using the boot method), but is also not required for
the file systems to be properly mounted. The warning can be
safely ignored.
This chapter builds the tools needed by some packages to run the tests that they have. I.e., make check. Tcl, Expect, and DejaGNU are needed for the GCC and Binutils testsuites. Check is needed for KBD tests. Installing four packages for testing purposes may seem excessive, but it is very reassuring, if not essential, to know that the most important tools are working properly.
The Tcl package contains the Tool Command Language.
Increase memory size for regular expressions where required.
sed -i s/500/5000/ generic/regc_nfa.c
Prepare Tcl for compilation:
cd unix ./configure --prefix=/tools
Build the package:
make
Install the package:
make install
Tcl's private header files are needed for the next package, Expect. Install them into /tools:
make install-private-headers
Now make a necessary symbolic link:
ln -sv tclsh8.6 /tools/bin/tclsh
The Expect package contains a program for carrying out scripted dialogues with other interactive programs.
Now prepare Expect for compilation:
./configure --prefix=/tools --with-tcl=/tools/lib \ --with-tclinclude=/tools/include
The meaning of the configure options:
--with-tcl=/tools/lib
This ensures that the configure script finds the Tcl installation in the temporary testsuite-tools location.
--with-tclinclude=/tools/include
This explicitly tells Expect where to find Tcl's internal headers. Using this option avoids conditions where configure fails because it cannot automatically discover the location of the Tcl source directory.
Build the package:
make
Install the package:
make SCRIPTS="" install
The meaning of the make parameter:
SCRIPTS=""
This prevents installation of the supplementary expect scripts, which are not needed.
The DejaGNU package contains a framework for testing other programs.
Prepare DejaGNU for compilation:
./configure --prefix=/tools
Build and install the package:
make install
The Check package is a unit testing framework for C.
Prepare Check for compilation:
./configure --prefix=/tools
Build the package:
make
Install the package:
make install
In this chapter, we enter the building site and start constructing the CLFS system in earnest. The installation of this software is straightforward. Although in many cases the installation instructions could be made shorter and more generic, we have opted to provide the full instructions for every package to minimize the possibilities for mistakes. The key to learning what makes a Linux system work is to know what each package is used for and why the user (or the system) needs it. For every installed package, a summary of its contents is given, followed by concise descriptions of each program and library the package installed.
If using compiler optimizations, please review the optimization
hint at http://hints.cross-lfs.org/index.php/Optimization.
Compiler optimizations can make a program run slightly faster,
but they may also cause compilation difficulties and problems
when running the program. If a package refuses to compile when
using optimization, try to compile it without optimization and
see if that fixes the problem. Even if the package does compile
when using optimization, there is the risk it may have been
compiled incorrectly because of the complex interactions
between the code and build tools. Also note that the
-march
and -mtune
options may cause problems with the
toolchain packages (Binutils, GCC and Glibc). The small
potential gains achieved in using compiler optimizations are
often outweighed by the risks. First-time builders of CLFS are
encouraged to build without custom optimizations. The
subsequent system will still run very fast and be stable at the
same time.
The order that packages are installed in this chapter needs to
be strictly followed to ensure that no program accidentally
acquires a path referring to /tools
hard-wired into it. For the same
reason, do not compile packages in parallel. Compiling in
parallel may save time (especially on dual-CPU machines), but
it could result in a program containing a hard-wired path to
/tools
, which will cause the
program to stop working when that directory is removed.
To keep track of which package installs particular files, a package manager can be used. For a general overview of different styles of package managers, please take a look at the next page.
Package Management is an often-requested addition to the CLFS Book. A Package Manager allows tracking the installation of files making it easy to remove and upgrade packages. Before you begin to wonder, NO—this section will not talk about nor recommend any particular package manager. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques. This section briefly mentions issues that may arise when upgrading packages.
Some reasons why no specific package manager is recommended in CLFS or CBLFS include:
Dealing with package management takes the focus away from the goals of these books—teaching how a Linux system is built.
There are multiple solutions for package management, each having its strengths and drawbacks. Including one that satisfies all audiences is difficult.
There are some hints written on the topic of package management. Visit the Hints subproject and see if one of them fits your need.
A Package Manager makes it easy to upgrade to newer versions when they are released. Generally the instructions in CLFS and CBLFS can be used to upgrade to the newer versions. Here are some points that you should be aware of when upgrading packages, especially on a running system.
If one of the toolchain packages (Glibc, GCC or Binutils) needs to be upgraded to a newer minor version, it is safer to rebuild CLFS. Though you may be able to get by rebuilding all the packages in their dependency order, we do not recommend it. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer to rebuild. For micro version updates, a simple reinstallation usually works, but is not guaranteed. For example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not usually cause any problems.
If a package containing a shared library is updated,
and if the name of the library changes, then all the
packages dynamically linked to the library need to be
recompiled to link against the newer library. (Note
that there is no correlation between the package
version and the name of the library.) For example,
consider a package foo-1.2.3 that installs a shared
library with name libfoo.so.1
. Say you upgrade the
package to a newer version foo-1.2.4 that installs a
shared library with name libfoo.so.2
. In this case, all
packages that are dynamically linked to libfoo.so.1
need to be recompiled to
link against libfoo.so.2
.
Note that you should not remove the previous libraries
until the dependent packages are recompiled.
If you are upgrading a running system, be on the lookout for packages that use cp instead of install to install files. The latter command is usually safer if the executable or library is already loaded in memory.
The following are some common package management techniques. Before making a decision on a package manager, do some research on the various techniques, particularly the drawbacks of the particular scheme.
Yes, this is a package management technique. Some folks do not find the need for a package manager because they know the packages intimately and know what files are installed by each package. Some users also do not need any package management because they plan on rebuilding the entire system when a package is changed.
This is a simplistic package management that does not need
any extra package to manage the installations. Each package
is installed in a separate directory. For example, package
foo-1.1 is installed in /usr/pkg/foo-1.1
and a symlink is made
from /usr/pkg/foo
to
/usr/pkg/foo-1.1
. When
installing a new version foo-1.2, it is installed in
/usr/pkg/foo-1.2
and the
previous symlink is replaced by a symlink to the new
version.
Environment variables such as PATH
, LD_LIBRARY_PATH
, MANPATH
, INFOPATH
and CPPFLAGS
need to be expanded
to include /usr/pkg/foo
. For
more than a few packages, this scheme becomes unmanageable.
This is a variation of the previous package management
technique. Each package is installed similar to the
previous scheme. But instead of making the symlink, each
file is symlinked into the /usr
hierarchy. This removes the need to
expand the environment variables. Though the symlinks can
be created by the user to automate the creation, many
package managers have been written using this approach. A
few of the popular ones include Stow, Epkg, Graft, and
Depot.
The installation needs to be faked, so that the package
thinks that it is installed in /usr
though in reality it is installed in
the /usr/pkg
hierarchy.
Installing in this manner is not usually a trivial task.
For example, consider that you are installing a package
libfoo-1.1. The following instructions may not install the
package properly:
./configure --prefix=/usr/pkg/libfoo/1.1 make make install
The installation will work, but the dependent packages may
not link to libfoo as you would expect. If you compile a
package that links against libfoo, you may notice that it
is linked to /usr/pkg/libfoo/1.1/lib/libfoo.so.1
instead of /usr/lib/libfoo.so.1
as you would expect.
The correct approach is to use the DESTDIR
strategy to fake installation of the
package. This approach works as follows:
./configure --prefix=/usr make make DESTDIR=/usr/pkg/libfoo/1.1 install
Most packages support this approach, but there are some
which do not. For the non-compliant packages, you may
either need to manually install the package, or you may
find that it is easier to install some problematic packages
into /opt
.
In this technique, a file is timestamped before the installation of the package. After the installation, a simple use of the find command with the appropriate options can generate a log of all the files installed after the timestamp file was created. A package manager written with this approach is install-log.
Though this scheme has the advantage of being simple, it has two drawbacks. If, during installation, the files are installed with any timestamp other than the current time, those files will not be tracked by the package manager. Also, this scheme can only be used when one package is installed at a time. The logs are not reliable if two packages are being installed on two different consoles.
In this approach, a library is preloaded before installation. During installation, this library tracks the packages that are being installed by attaching itself to various executables such as cp, install, mv and tracking the system calls that modify the filesystem. For this approach to work, all the executables need to be dynamically linked without the suid or sgid bit. Preloading the library may cause some unwanted side-effects during installation. Therefore, it is advised that one performs some tests to ensure that the package manager does not break anything and logs all the appropriate files.
In this scheme, the package installation is faked into a separate tree as described in the Symlink style package management. After the installation, a package archive is created using the installed files. This archive is then used to install the package either on the local machine or can even be used to install the package on other machines.
This approach is used by most of the package managers found in the commercial distributions. Examples of package managers that follow this approach are RPM (which, incidentally, is required by the Linux Standard Base Specification), pkg-utils, Debian's apt, and Gentoo's Portage system. A hint describing how to adopt this style of package management for CLFS systems is located at http://hints.cross-lfs.org/index.php/Fakeroot.
In the final-system build, you are no longer cross-compiling so it is possible to run package testsuites. Some test suites are more important than others. For example, the test suites for the core toolchain packages—GCC, Binutils, and Glibc—are of the utmost importance due to their central role in a properly functioning system. The test suites for GCC and Glibc can take a very long time to complete, especially on slower hardware, but are strongly recommended.
A common issue with running the test suites for Binutils and
GCC is running out of pseudo terminals (PTYs). This can result
in a high number of failing tests. This may happen for several
reasons, but the most likely cause (if you chrooted) is that
the host system does not have the devpts
file system set up correctly. This
issue is discussed in greater detail at http://trac.cross-lfs.org/wiki/faq#no-ptys.
Sometimes package test suites will fail, but for reasons which the developers are aware of and have deemed non-critical. Consult the logs located at http://cross-lfs.org/testsuite-logs/git/ to verify whether or not these failures are expected. This site is valid for all tests throughout this book.
The Perl package contains the Practical Extraction and Report Language.
First adapt some hard-wired paths to the C library by applying the following patch:
patch -Np1 -i ../perl-5.18.1-libc-1.patch
Change a hardcoded path from /usr/include
to /tools/include
:
sed -i 's@/usr/include@/tools/include@g' ext/Errno/Errno_pm.PL
Prepare Temporary Perl for compilation:
./configure.gnu --prefix=/tools -Dcc="gcc"
The meaning of the configure option:
-Dcc="gcc"
Tells Perl to use gcc instead of the default cc.
Compile the package:
make
Although Perl comes with a test suite, it is not recommended to run it at this point, as this Perl installation is only temporary. The test suite can be run later in this chapter if desired.
Install the package:
make install
Finally, create a necessary symlink:
ln -sfv /tools/bin/perl /usr/bin
Details on this package are located in Section 10.31.2, “Contents of Perl.”
The Linux Kernel contains a make target that installs “sanitized” kernel headers.
For this step you will need the kernel tarball.
Install the kernel header files:
make mrproper make headers_check make INSTALL_HDR_PATH=/usr headers_install find /usr/include -name .install -or -name ..install.cmd | xargs rm -fv
The meaning of the make commands:
make
mrproper
Ensures that the kernel source dir is clean.
make
headers_check
Sanitizes the raw kernel headers so that they can be used by userspace programs.
make
INSTALL_HDR_PATH=/usr headers_install
This will install the kernel headers into /usr/include
.
find
/usr/include -name .install -or -name ..install.cmd |
xargs rm -fv
Removes a number of unneeded debugging files that were installed.
The Man-pages package contains over 1,200 man pages.
Install Man-pages by running:
make install
This package contains man pages that describe the following: POSIX headers (section 0p), POSIX utilities (section 1p), POSIX functions (section 3p), user commands (section 1), system calls (section 2), libc calls (section 3), device information (section 4), file formats (section 5), games (section 6), conventions and macro packages (section 7), system administration (section 8), and kernel (section 9). |
The EGLIBC package contains the main C library. This library provides the basic routines for allocating memory, searching directories, opening and closing files, reading and writing files, string handling, pattern matching, arithmetic, and so on.
Some packages outside of CLFS suggest installing GNU
libiconv in order to translate data from one encoding to
another. The project's home page (http://www.gnu.org/software/libiconv/)
says “This library provides an
iconv()
implementation, for
use on systems which don't have one, or whose
implementation cannot convert from/to
Unicode.” EGLIBC provides an iconv()
implementation and can convert
from/to Unicode, therefore libiconv is not required on a
CLFS system.
At the end of the installation, the build system will run a sanity test to make sure everything installed properly. This script will attempt to test for a library that is only used in the test suite and is never installed. Prevent the script from testing for this library with the following command:
sed -i 's/\(&& $name ne\) "db1"/ & \1 "nss_test1"/' scripts/test-installation.pl
This same script performs its tests by attempting to compile test programs against certain libraries. However it does not specify the ld.so, and our toolchain is still configured to use the one in /tools. The following set of commands will force the script to use the complete path of the new ld.so that was just installed:
LINKER=$(readelf -l /tools/bin/bash | sed -n 's@.*interpret.*/tools\(.*\)]$@\1@p') sed -i "s|libs -o|libs -L/usr/lib -Wl,-dynamic-linker=${LINKER} -o|" \ scripts/test-installation.pl unset LINKER
The EGLIBC build system is self-contained and will install
perfectly, even though the compiler specs file and linker are
still pointing at /tools
. The
specs and linker cannot be adjusted before the EGLIBC install
because the EGLIBC Autoconf tests would give false results
and defeat the goal of achieving a clean build.
The EGLIBC documentation recommends building EGLIBC outside of the source directory in a dedicated build directory:
mkdir -v ../eglibc-build cd ../eglibc-build
Prepare EGLIBC for compilation:
CFLAGS="-march=$(cut -d- -f1 <<< $MACHTYPE) -O2" \ ../eglibc-2.18/configure --prefix=/usr \ --disable-profile --enable-kernel=2.6.32 --libexecdir=/usr/lib/eglibc \ --enable-obsolete-rpc
The meaning of the new configure option:
--libexecdir=/usr/lib/eglibc
This changes the location of the getconf utility from
its default of /usr/libexec
to /usr/lib/eglibc
.
Compile the package:
make
The test suite for EGLIBC is considered critical. Do not skip it under any circumstance.
Before running the tests, copy a file from the source tree into our build tree to prevent a couple of test failures, then run the tests:
cp -v ../eglibc-2.18/iconvdata/gconv-modules iconvdata make -k check 2>&1 | tee eglibc-check-log; grep Error eglibc-check-log
The EGLIBC test suite is highly dependent on certain
functions of the host system, in particular the kernel. The
posix/annexc test normally fails and you should see
Error 1 (ignored)
in the output.
Apart from this, the EGLIBC test suite is always expected to
pass. However, in certain circumstances, some failures are
unavoidable. If a test fails because of a missing program (or
missing symbolic link), or a segfault, you will see an error
code greater than 127 and the details will be in the log.
More commonly, tests will fail with Error 2
- for these, the contents of the
corresponding .out
file, e.g.
posix/annexc.out
may be
informative. Here is a list of the most common issues:
The math tests, at least on i686, fail in the test-double and test-idouble tests with gcc-4.8.1 . These two failures in the math tests appear to be harmless. The math tests may also fail on systems where the CPU is not a relatively new genuine Intel or authentic AMD. Certain optimization settings are also known to be a factor here.
If you have mounted the CLFS partition with the
noatime
option,
the atime test
will fail. As mentioned in Section 2.4,
“Mounting the New Partition”, do not
use the noatime
option while building CLFS.
When running on older and slower hardware, some tests can fail because of test timeouts being exceeded.
Though it is a harmless message, the install stage of EGLIBC
will complain about the absence of /etc/ld.so.conf
. Prevent this warning with:
touch /etc/ld.so.conf
Install the package:
make install
The locales that can make the system respond in a different language were not installed by the above command. Install them with:
make localedata/install-locales
To save time, an alternative to running the previous command
(which generates and installs every locale listed in the
eglibc-2.18/localedata/SUPPORTED
file) is
to install only those locales that are wanted and needed.
This can be achieved by using the localedef command.
Information on this command is located in the INSTALL
file in the EGLIBC source. However,
there are a number of locales that are essential in order for
the tests of future packages to pass, in particular, the
libstdc++ tests from
GCC. The following instructions, instead of the install-locales
target used
above, will install the minimum set of locales necessary for
the tests to run successfully:
mkdir -pv /usr/lib/locale localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8 localedef -i de_DE -f ISO-8859-1 de_DE localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro localedef -i en_HK -f ISO-8859-1 en_HK localedef -i en_PH -f ISO-8859-1 en_PH localedef -i en_US -f ISO-8859-1 en_US localedef -i es_MX -f ISO-8859-1 es_MX localedef -i fa_IR -f UTF-8 fa_IR localedef -i fr_FR -f ISO-8859-1 fr_FR localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro localedef -i it_IT -f ISO-8859-1 it_IT localedef -i ja_JP -f EUC-JP ja_JP
Some locales installed by the make localedata/install-locales command above are not properly supported by some applications that are in CLFS and CBLFS. Because of the various problems that arise due to application programmers making assumptions that break in such locales, CLFS should not be used in locales that utilize multibyte character sets (including UTF-8) or right-to-left writing order. Numerous unofficial and unstable patches are required to fix these problems, and it has been decided by the CLFS developers not to support such complex locales at this time. This applies to the ja_JP and fa_IR locales as well—they have been installed only for GCC and Gettext tests to pass, and the watch program (part of the Procps package) does not work properly in them. Various attempts to circumvent these restrictions are documented in internationalization-related hints.
The /etc/nsswitch.conf
file
needs to be created because, although EGLIBC provides
defaults when this file is missing or corrupt, the EGLIBC
defaults do not work well in a networked environment. The
time zone also needs to be configured.
Create a new file /etc/nsswitch.conf
by running the
following:
cat > /etc/nsswitch.conf << "EOF"
# Begin /etc/nsswitch.conf
passwd: files
group: files
shadow: files
hosts: files dns
networks: files
protocols: files
services: files
ethers: files
rpc: files
# End /etc/nsswitch.conf
EOF
Install timezone data:
tar -xf ../tzdata2013g.tar.gz ZONEINFO=/usr/share/zoneinfo mkdir -pv $ZONEINFO/{posix,right} for tz in etcetera southamerica northamerica europe africa antarctica \ asia australasia backward pacificnew solar87 solar88 solar89 \ systemv; do zic -L /dev/null -d $ZONEINFO -y "sh yearistype.sh" ${tz} zic -L /dev/null -d $ZONEINFO/posix -y "sh yearistype.sh" ${tz} zic -L leapseconds -d $ZONEINFO/right -y "sh yearistype.sh" ${tz} done cp -v zone.tab iso3166.tab $ZONEINFO zic -d $ZONEINFO -p America/New_York unset ZONEINFO
The meaning of the zic commands:
zic -L
/dev/null ...
This creates posix timezones, without any leap seconds.
It is conventional to put these in both zoneinfo
and zoneinfo/posix
. It is necessary to
put the POSIX timezones in zoneinfo
, otherwise various
test-suites will report errors. On an embedded system,
where space is tight and you do not intend to ever
update the timezones, you could save 1.9MB by not using
the posix
directory, but
some applications or test-suites might give less good
results
zic -L
leapseconds ...
This creates right timezones, including leap seconds.
On an embedded system, where space is tight and you do
not intend to ever update the timezones, or care about
the correct time, you could save 1.9MB by omitting the
right
directory.
zic ... -p
...
This creates the posixrules
file. We use New York
because POSIX requires the daylight savings time rules
to be in accordance with US rules.
To determine the local time zone, run the following script:
tzselect
After answering a few questions about the location, the
script will output the name of the time zone (e.g.,
EST5EDT or
Canada/Eastern). Then
create the /etc/localtime
file
by running:
cp -v --remove-destination /usr/share/zoneinfo/[xxx]
\
/etc/localtime
Replace [xxx]
with
the name of the time zone that tzselect provided (e.g.,
Canada/Eastern).
The meaning of the cp option:
--remove-destination
This is needed to force removal of the already existing
symbolic link. The reason for copying the file instead
of using a symlink is to cover the situation where
/usr
is on a separate
partition. This could be important when booted into
single user mode.
By default, the dynamic loader (/lib/ld-linux.so.2
) searches through
/lib
and /usr/lib
for dynamic libraries that are
needed by programs as they are run. However, if there are
libraries in directories other than /lib
and /usr/lib
, these need to be added to the
/etc/ld.so.conf
file in order
for the dynamic loader to find them. Two directories that are
commonly known to contain additional libraries are
/usr/local/lib
and /opt/lib
, so add those directories to the
dynamic loader's search path.
Create a new file /etc/ld.so.conf
by running the following:
cat > /etc/ld.so.conf << "EOF"
# Begin /etc/ld.so.conf
/usr/local/lib
/opt/lib
# End /etc/ld.so.conf
EOF
Can be used to create a stack trace when a program terminates with a segmentation fault |
|
Generates message catalogues |
|
Displays the system configuration values for file system specific variables |
|
Gets entries from an administrative database |
|
Performs character set conversion |
|
Creates fastloading iconv module configuration files |
|
Configures the dynamic linker runtime bindings |
|
Reports which shared libraries are required by each given program or shared library |
|
Assists ldd with object files |
|
Tells the compiler to enable or disable the use of POSIX locales for built-in operations |
|
Compiles locale specifications |
|
Creates a simple database from textual input |
|
Reads and interprets a memory trace file and displays a summary in human-readable format |
|
A daemon that provides a cache for the most common name service requests |
|
Dumps information generated by PC profiling |
|
Lists dynamic shared objects used by running processes |
|
Generates C code to implement the Remote Procecure Call (RPC) protocol |
|
A statically linked program that creates symbolic links |
|
Traces shared library procedure calls of a specified command |
|
Reads and displays shared object profiling data |
|
Asks the user about the location of the system and reports the corresponding time zone description |
|
Traces the execution of a program by printing the currently executed function |
|
The time zone dumper |
|
The time zone compiler |
|
The helper program for shared library executables |
|
Used by programs, such as Mozilla, to solve broken locales |
|
The segmentation fault signal handler |
|
An asynchronous name lookup library |
|
Provides the portability needed in order to run certain Berkey Software Distribution (BSD) programs under Linux |
|
The main C library |
|
Used internally by EGLIBC for handling
internationalized domain names in the |
|
The cryptography library |
|
The dynamic linking interface library |
|
A runtime library for g++ |
|
The Institute of Electrical and Electronic Engineers (IEEE) floating point library |
|
The mathematical library |
|
Contains code run at boot |
|
Used by memusage (included in EGLIBC, but not built in a base CLFS system as it has additional dependencies) to help collect information about the memory usage of a program |
|
The network services library |
|
The Name Service Switch libraries, containing functions for resolving host names, user names, group names, aliases, services, protocols, etc. |
|
Contains profiling functions used to track the amount of CPU time spent in specific source code lines |
|
The POSIX threads library |
|
Contains functions for creating, sending, and interpreting packets to the Internet domain name servers |
|
Contains functions providing miscellaneous RPC services |
|
Contains functions providing most of the interfaces specified by the POSIX.1b Realtime Extension |
|
Contains functions useful for building debuggers for multi-threaded programs |
|
Contains code for “standard” functions used in many different Unix utilities |
Now we amend the GCC specs file so that it points to the new dynamic linker. A perl command accomplishes this:
gcc -dumpspecs | \ perl -p -e 's@/tools/lib/ld@/lib/ld@g;' \ -e 's@\*startfile_prefix_spec:\n@$_/usr/lib/ @g;' > \ $(dirname $(gcc --print-libgcc-file-name))/specs
It is a good idea to visually inspect the specs file to verify the intended change was actually made.
Note that /lib
is now the prefix
of our dynamic linker.
It is imperative at this point to stop and ensure that the basic functions (compiling and linking) of the adjusted toolchain are working as expected. To do this, perform a sanity check:
echo 'main(){}' > dummy.c gcc dummy.c readelf -l a.out | grep ': /lib'
If everything is working correctly, there should be no errors, and the output of the last command will be:
[Requesting program interpreter: /lib/ld-linux.so.2]
Note that /lib
is now the
prefix of our dynamic linker.
If the output does not appear as shown above or is not received at all, then something is seriously wrong. Investigate and retrace the steps to find out where the problem is and correct it. The most likely reason is that something went wrong with the specs file amendment above. Any issues will need to be resolved before continuing on with the process.
Once everything is working correctly, clean up the test files:
rm -v dummy.c a.out
GMP is a library for arithmetic on arbitrary precision integers, rational numbers, and floating-point numbers.
If you are compiling this package on a different CPU than
you plan to run the CLFS system on, you must replace GMP's
config.guess
and config.sub
wrappers with the originals.
This will prevent GMP from optimizing for the wrong CPU.
You can make this change with the following command:
mv -v config{fsf,}.guess mv -v config{fsf,}.sub
Prepare GMP for compilation:
CC="gcc -isystem /usr/include" \ CXX="g++ -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr --enable-cxx
Compile the package:
make
The test suite for GMP is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make install
The MPFR library is a C library for multiple-precision floating-point computations with correct rounding.
Prepare MPFR for compilation:
CC="gcc -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr --enable-shared \ --with-gmp=/usr
Compile the package:
make
The test suite for MPFR is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make install
MPC is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result.
Prepare MPC for compilation:
CC="gcc -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr
Compile the package:
make
The test suite for MPC is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make install
ISL is a library for manipulating sets and relations of integer points bounded by linear constraints.
Prepare ISL for compilation:
CC="gcc -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr
Compile the package:
make
The test suite for ISL is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make install
Finally, move a misplaced file:
mkdir -pv /usr/share/gdb/auto-load/usr/lib mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib
CLooG is a library to generate code for scanning Z-polyhedra. In other words, it finds code that reaches each integral point of one or more parameterized polyhedra. GCC links with this library in order to enable the new loop generation code known as Graphite.
Prepare CLooG for compilation:
CC="gcc -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr --enable-shared --with-isl=system
Compile the package:
make
The test suite for CLooG is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make install
The Zlib package contains compression and decompression routines used by some programs.
Prepare Zlib for compilation:
CC="gcc -isystem /usr/include" \ CXX="g++ -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The previous command installed two .so
files into /usr/lib
. We will move it into /lib
and then relink it to /usr/lib
:
mv -v /usr/lib/libz.so.* /lib ln -svf ../../lib/libz.so.1 /usr/lib/libz.so
The Binutils package contains a linker, an assembler, and other tools for handling object files.
Verify that the PTYs are working properly inside the build environment. Check that everything is set up correctly by performing a simple test:
expect -c "spawn ls"
This command should give the following output:
spawn ls
If, instead, it gives a message saying to create more ptys, then the environment is not set up for proper PTY operation. This issue needs to be resolved before running the test suites for Binutils and GCC.
The Binutils documentation recommends building Binutils outside of the source directory in a dedicated build directory:
mkdir -v ../binutils-build cd ../binutils-build
Prepare Binutils for compilation:
CC="gcc -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ../binutils-2.23.2/configure --prefix=/usr \ --enable-shared
Compile the package:
make configure-host
During make configure-host you may receive the following error message. It is safe to ignore.
WARNING: `flex' is missing on your system. You should only
need it if you modified a `.l' file. You may need the `Flex'
package in order for those modifications to take effect. You
can get `Flex' from any GNU archive site.
make tooldir=/usr
The meaning of the make parameter:
tooldir=/usr
Normally, the tooldir (the directory where the
executables will ultimately be located) is set to
$(exec_prefix)/$(target_alias)
.
Because this is a custom system, this target-specific
directory in /usr
is not
required.
The test suite for Binutils is considered critical. Do not skip it under any circumstance.
Test the results:
make check
Install the package:
make tooldir=/usr install
Install the libiberty
header
file that is needed by some packages:
cp -v ../binutils-2.23.2/include/libiberty.h /usr/include
Translates program addresses to file names and line numbers; given an address and the name of an executable, it uses the debugging information in the executable to determine which source file and line number are associated with the address |
|
Creates, modifies, and extracts from archives |
|
An assembler that assembles the output of gcc into object files |
|
Used by the linker to de-mangle C++ and Java symbols and to keep overloaded functions from clashing |
|
Updates the ELF header of ELF files |
|
Displays call graph profile data |
|
A linker that combines a number of object and archive files into a single file, relocating their data and tying up symbol references |
|
Hard link to ld |
|
Lists the symbols occurring in a given object file |
|
Translates one type of object file into another |
|
Displays information about the given object file, with options controlling the particular information to display; the information shown is useful to programmers who are working on the compilation tools |
|
Generates an index of the contents of an archive and stores it in the archive; the index lists all of the symbols defined by archive members that are relocatable object files |
|
Displays information about ELF type binaries |
|
Lists the section sizes and the total size for the given object files |
|
Outputs, for each given file, the sequences of printable characters that are of at least the specified length (defaulting to four); for object files, it prints, by default, only the strings from the initializing and loading sections while for other types of files, it scans the entire file |
|
Discards symbols from object files |
|
Contains routines used by various GNU programs, including getopt, obstack, strerror, strtol, and strtoul |
|
The Binary File Descriptor library |
|
A library for dealing with opcodes—the “readable text” versions of instructions for the processor; it is used for building utilities like objdump. |
The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.
The following patch contains a number of updates to the 4.8.1 branch by the GCC developers:
patch -Np1 -i ../gcc-4.8.1-branch_update-3.patch
Apply a sed subsitution that will suppress the execution of the fixincludes script:
cp -v gcc/Makefile.in{,.orig} sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig > gcc/Makefile.in
Apply a sed
substitution that will suppress the installation of
libiberty.a
. The version of
libiberty.a
provided by
Binutils will be used instead:
sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in
The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:
mkdir -v ../gcc-build cd ../gcc-build
Prepare GCC for compilation:
CC="gcc -isystem /usr/include" \ CXX="g++ -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ../gcc-4.8.1/configure --prefix=/usr \ --libexecdir=/usr/lib --enable-shared --enable-threads=posix \ --enable-__cxa_atexit --enable-c99 --enable-long-long \ --enable-clocale=gnu --enable-languages=c,c++ \ --disable-multilib --disable-libstdcxx-pch \ --enable-cloog-backend=isl --disable-isl-version-check --with-system-zlib \ --enable-checking=release --enable-libstdcxx-time \ --disable-install-libiberty
Compile the package:
make
The test suite for GCC is considered critical. Do not skip it under any circumstance.
Increase the stack size prior to running the tests:
ulimit -s 32768
Test the results, but do not stop at errors:
make -k check
The -k
flag is used
to make the test suite run through to completion and not stop
at the first failure. The GCC test suite is very
comprehensive and is almost guaranteed to generate a few
failures. To receive a summary of the test suite results,
run:
../gcc-4.8.1/contrib/test_summary
For only the summaries, pipe the output through
grep -A7
Summ
.
A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet.
Install the package:
make install
Some packages expect the C preprocessor to be installed in
the /lib
directory. To support
those packages, create this symlink:
ln -sv ../usr/bin/cpp /lib
Many packages use the name cc to call the C compiler. To satisfy those packages, create a symlink:
ln -sv gcc /usr/bin/cc
Finally, move a misplaced file:
mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib
The C compiler |
|
The C preprocessor; it is used by the compiler to expand the #include, #define, and similar statements in the source files |
|
The C++ compiler |
|
The C++ compiler |
|
The C compiler |
|
A coverage testing tool; it is used to analyze programs to determine where optimizations will have the most effect |
|
Contains run-time support for gcc |
|
Library that is linked into a program when gcc is instructed to enable profiling |
|
GNU implementation of the OpenMP API for multi-platform shared-memory parallel programming in C/C++ and Fortran |
|
The libmudflap libraries are used by GCC for instrumenting pointer and array dereferencing operations. |
|
Contains routines supporting GCC's stack-smashing protection functionality |
|
The standard C++ library |
|
Provides supporting routines for the C++ programming language |
The Sed package contains a stream editor.
Prepare Sed for compilation:
./configure --prefix=/usr --bindir=/bin
Compile the package:
make
Build the HTML documentation:
make html
To test the results, issue: make check
.
Install the package:
make install
Install the HTML documentation:
make -C doc install-html
The Ncurses package contains libraries for terminal-independent handling of character screens.
The following patch contains updates from the 5.9 branch by the Ncurses developers:
patch -Np1 -i ../ncurses-5.9-branch_update-4.patch
Prepare Ncurses for compilation:
./configure --prefix=/usr --libdir=/lib \ --with-shared --without-debug --enable-widec \ --with-manpage-format=normal \ --with-default-terminfo-dir=/usr/share/terminfo
Compile the package:
make
This package has a test suite, and can be ran after the
package is installed. The tests are in the test/
directory. See the README
file in that directory for details.
Install the package:
make install
Move the Ncurses static libraries to the proper location:
mv -v /lib/lib{panelw,menuw,formw,ncursesw,ncurses++w}.a /usr/lib
Create symlinks in /usr/lib:
rm -v /lib/lib{ncursesw,menuw,panelw,formw}.so ln -svf ../../lib/libncursesw.so.5 /usr/lib/libncursesw.so ln -svf ../../lib/libmenuw.so.5 /usr/lib/libmenuw.so ln -svf ../../lib/libpanelw.so.5 /usr/lib/libpanelw.so ln -svf ../../lib/libformw.so.5 /usr/lib/libformw.so
Now we will make our Ncurses compatible for older and non-widec compatible programs can build properly:
for lib in curses ncurses form panel menu ; do echo "INPUT(-l${lib}w)" > /usr/lib/lib${lib}.so ln -sfv lib${lib}w.a /usr/lib/lib${lib}.a done ln -sfv libncursesw.so /usr/lib/libcursesw.so ln -sfv libncursesw.a /usr/lib/libcursesw.a ln -sfv libncurses++w.a /usr/lib/libncurses++.a ln -sfv ncursesw5-config /usr/bin/ncurses5-config
Now we will create a symlink for /usr/share/terminfo in
/usr/lib
for compatibility:
ln -sfv ../share/terminfo /usr/lib/terminfo
Converts a termcap description into a terminfo description |
|
Clears the screen, if possible |
|
Compares or prints out terminfo descriptions |
|
Converts a terminfo description into a termcap description |
|
Provides configuration information for ncurses |
|
Reinitializes a terminal to its default values |
|
Sets and clears tab stops on a terminal |
|
The terminfo entry-description compiler that translates a terminfo file from source format into the binary format needed for the ncurses library routines. A terminfo file contains information on the capabilities of a certain terminal |
|
Lists all available terminal types, giving the primary name and description for each |
|
Makes the values of terminal-dependent capabilities available to the shell; it can also be used to reset or initialize a terminal or report its long name |
|
Can be used to initialize terminals |
|
A link to |
|
Contains functions to display text in many complex ways on a terminal screen; a good example of the use of these functions is the menu displayed during the kernel's make menuconfig |
|
Contains functions to implement forms |
|
Contains functions to implement menus |
|
Contains functions to implement panels |
Pkg-config-lite is a tool to help you insert the correct compiler options on the command line when compiling applications and libraries.
Prepare Pkg-config-lite for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Util-linux package contains miscellaneous utility programs. Among them are utilities for handling file systems, consoles, partitions, and messages.
The FHS recommends using the /var/lib/hwclock
directory instead of the
usual /etc
directory as the
location for the adjtime
file.
To make the hwclock program
FHS-compliant, run the following:
sed -i -e 's@etc/adjtime@var/lib/hwclock/adjtime@g' \ $(grep -rl '/etc/adjtime' .) mkdir -pv /var/lib/hwclock
Prepare Util-linux for compilation:
./configure --enable-write --disable-login --disable-su
The meaning of the configure options:
--enable-write
This option allows the write program to be installed.
--disable-login
--disable-su
Disables building the login and su programs, as the Shadow package installs its own versions.
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
Move the logger
binary to /bin
as it is needed
by the CLFS-Bootscripts package:
mv -v /usr/bin/logger /bin
Informs the kernel of a new partition |
|
Opens a tty port, prompts for a login name, and then invokes the login program |
|
A command line utility to locate and print block device attributes |
|
Allows users to call block device ioctls from the command line |
|
Displays a simple calendar |
|
Manipulates the partition table of the given device |
|
Utility to configure CPUs |
|
Manipulates real-time attributes of a process |
|
Filters out reverse line feeds |
|
Filters nroff output for terminals that lack some capabilities, such as overstriking and half-lines |
|
Filters out the given columns |
|
Formats a given file into multiple columns |
|
Sets the function of the Ctrl+Alt+Del key combination to a hard or a soft reset |
|
Tunes the parameters of the serial line drivers for Cyclades cards |
|
Gives the Discordian date or converts the given Gregorian date to a Discordian one |
|
Asks the kernel to remove a partition |
|
Dumps the kernel boot messages |
|
Eject removable media |
|
Preallocates space to a file |
|
Low-level formats a floppy disk |
|
Manipulates the partition table of the given device |
|
Finds a file system by label or Universally Unique Identifier (UUID) |
|
Lists mounted filesystems or searches for a filesystem |
|
Acquires a file lock and then executes a command with the lock held |
|
Is used to check, and optionally repair, file systems |
|
Performs a consistency check on the Cramfs file system on the given device |
|
Performs a consistency check on the Minix file system on the given device |
|
Suspends and resumes access to a filesystem |
|
Discards unused blocks on a mounted filesystem |
|
Parses options in the given command line |
|
Dumps the given file in hexadecimal or in another given format |
|
Reads or sets the system's hardware clock, also called the Real-Time Clock (RTC) or Basic Input-Output System (BIOS) clock |
|
Gives and sets program I/O scheduling class and priority |
|
Creates various IPC resources |
|
Removes the given Inter-Process Communication (IPC) resource |
|
Provides IPC status information |
|
Reports the size of an iso9660 file system |
|
Send a signal to a process |
|
Attaches a line discipline to a serial line |
|
Enters the given message into the system log |
|
Displays lines that begin with the given string |
|
Sets up and controls loop devices |
|
Prints information about block devices |
|
Prints CPU architechture information |
|
Lists local system locks |
|
Generates magic cookies (128-bit random hexadecimal numbers) for xauth |
|
Builds a file system on a device (usually a hard disk partition) |
|
Creates a Santa Cruz Operations (SCO) bfs file system |
|
Creates a cramfs file system |
|
Creates a Minix file system |
|
Initializes the given device or file to be used as a swap area |
|
A filter for paging through text one screen at a time |
|
Attaches the file system on the given device to a specified directory in the file-system tree |
|
Tells you whether or not a directory is a mount point. |
|
Shows the symbolic links in the given pathnames |
|
Tells the kernel about the presence and numbering of on-disk partitions |
|
Displays a text file one screen full at a time |
|
Makes the given file system the new root file system of the current process |
|
Gets and sets a process' resource limits |
|
Binds a Linux raw character device to a block device |
|
Reads kernel profiling information |
|
Renames the given files, replacing a given string with another |
|
Alters the priority of running processes |
|
Asks the Linux kernel to resize a partition |
|
Reverses the lines of a given file |
|
Enters a system sleep state until a specified wakeup time |
|
Makes a typescript of a terminal session |
|
Plays back typescripts created by script |
|
Changes reported architecture in new program environment and sets personality flags |
|
Runs the given program in a new session |
|
Sets terminal attributes |
|
A disk partition table manipulator |
|
Allows root to log in; it is normally invoked by init when the system goes into single user mode |
|
Prints or changes the label or UUID of a swap area |
|
Disables devices and files for paging and swapping |
|
Enables devices and files for paging and swapping and lists the devices and files currently in use |
|
Switches to another filesystem as the root of the mount tree |
|
Tracks the growth of a log file. Displays the last 10 lines of a log file, then continues displaying any new entries in the log file as they are created |
|
Retrieves or sets a process's CPU affinity |
|
Tunes the parameters of the line printer |
|
A filter for translating underscores into escape sequences indicating underlining for the terminal in use |
|
Disconnects a file system from the system's file tree |
|
Runs a program with some namespaces unshared from parent |
|
Displays the content of the given login file in a more user-friendly format |
|
A daemon used by the UUID library to generate time-based UUIDs in a secure and guranteed-unique fashion. |
|
Creates new UUIDs. Each new UUID can reasonably be considered unique among all UUIDs created, on the local system and on other systems, in the past and in the future |
|
Writes a message to all logged-in users |
|
Show hardware watchdog status |
|
Reports the location of the binary, source, and man page for the given command |
|
Wipes a filesystem signature from a device |
|
Sends a message to the given user if that user has not disabled receipt of such messages |
|
Contains routines for device identification and token extraction |
|
Contains routines for parsing the |
|
Contains routines for generating unique identifiers for objects that may be accessible beyond the local system |
The Procps package contains programs for monitoring processes.
The following patch adds process control group support to ps:
patch -Np1 -i ../procps-3.2.8-ps_cgroup-1.patch
The following patch fixes an issue where some procps utils print an error on the screen if the monitor isn't running at 60Hz:
patch -Np1 -i ../procps-3.2.8-fix_HZ_errors-1.patch
The following fixes an issue with Make 3.82:
sed -i -r '/^-include/s/\*(.*)/proc\1 ps\1/' Makefile
Compile the package:
make
This package does not come with a test suite.
Install the package:
make SKIP='/bin/kill /usr/share/man/man1/kill.1' install
Reports the amount of free and used memory (both physical and swap memory) in the system |
|
Looks up processes based on their name and other attributes |
|
Signals processes based on their name and other attributes |
|
Reports the memory map of the given process |
|
Lists the current running processes |
|
Reports the current working directory of a process |
|
Sends signals to processes matching the given criteria |
|
Displays detailed kernel slab cache information in real time |
|
Changes the scheduling priority of processes matching the given criteria |
|
Modifies kernel parameters at run time |
|
Prints a graph of the current system load average |
|
Displays a list of the most CPU intensive processes; it provides an ongoing look at processor activity in real time |
|
Reports how long the system has been running, how many users are logged on, and the system load averages |
|
Reports virtual memory statistics, giving information about processes, memory, paging, block Input/Output (IO), traps, and CPU activity |
|
Shows which users are currently logged on, where, and since when |
|
Runs a given command repeatedly, displaying the first screen-full of its output; this allows a user to watch the output change over time |
|
Contains the functions used by most programs in this package |
The E2fsprogs package contains the utilities for handling the
ext2
file system. It also
supports the ext3
and
ext4
journaling file systems.
The E2fsprogs documentation recommends that the package be built in a subdirectory of the source tree:
mkdir -v build cd build
Prepare E2fsprogs for compilation:
../configure --prefix=/usr --with-root-prefix="" \ --enable-elf-shlibs --disable-libblkid \ --disable-libuuid --disable-fsck \ --disable-uuidd
The meaning of the configure options:
--with-root-prefix=""
Certain programs (such as the e2fsck program) are
considered essential programs. When, for example,
/usr
is not mounted,
these programs still need to be available. They belong
in directories like /lib
and /sbin
. If this option
is not passed to E2fsprogs' configure, the programs are
installed into the /usr
directory.
--enable-elf-shlibs
This creates the shared libraries which some programs in this package use.
Compile the package:
make
To test the results, issue: make check
.
Install the binaries, documentation and shared libraries:
make install
Install the static libraries and headers:
make install-libs
Searches a device (usually a disk partition) for bad blocks |
|
Changes the attributes on a Linux file system |
|
An error table compiler; it converts a table of
error-code names and messages into a C source file
suitable for use with the |
|
A file system debugger; it can be used to examine
and change the state of an |
|
Prints the super block and blocks group information for the file system present on a given device |
|
Reports free space fragmentation information |
|
Is used to check, and optionally repair
|
|
Is used to save critical |
|
Prints the FS type of a given filesystem, given either a device name or label |
|
Displays or changes the file system label on the
|
|
Replays an undo log for an ext2/ext3/ext4 filesystem |
|
Online defragmenter for ext4 filesystems |
|
Reports on how badly fragmented a particular file might be |
|
By default checks |
|
By default checks |
|
By default checks |
|
By default checks |
|
Saves the output of a command in a log file |
|
Lists the attributes of files on a second extended file system |
|
Converts a table of command names and help messages
into a C source file suitable for use with the
|
|
Creates an |
|
By default creates |
|
By default creates |
|
By default creates |
|
By default creates |
|
Used to create a |
|
Can be used to enlarge or shrink an |
|
Adjusts tunable file system parameters on an
|
|
The common error display routine |
|
Used by dumpe2fs, chattr, and lsattr |
|
Contains routines to enable user-level programs to
manipulate an |
|
Provides an interface for creating and updating quota files and ext4 superblock fields |
|
Used by debugfs |
The Shadow package contains programs for handling passwords in a secure way.
If you would like to enforce the use of strong passwords,
refer to http://cblfs.cross-lfs.org/index.php/Cracklib
for installing Cracklib prior to building Shadow. Then add
--with-libcrack
to
the configure
command below.
Disable the installation of the groups program and its man pages, as Coreutils provides a better version:
sed -i 's/groups$(EXEEXT) //' src/Makefile.in find man -name Makefile.in -exec sed -i '/groups\.1\.xml/d' '{}' \; find man -name Makefile.in -exec sed -i 's/groups\.1 / /' {} \;
Prepare Shadow for compilation:
./configure --sysconfdir=/etc
The meaning of the configure options:
--sysconfdir=/etc
Tells Shadow to install its configuration files into
/etc
, rather than
/usr/etc
.
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
Instead of using the default
crypt method, use the
more secure SHA512
method of password encryption, which also allows passwords
longer than 8 characters. It is also necessary to change the
obsolete /var/spool/mail
location for user mailboxes that Shadow uses by default to
the /var/mail
location used
currently. Use the following sed command to make these
changes to the appropriate configuration file:
sed -i /etc/login.defs \ -e 's@#\(ENCRYPT_METHOD \).*@\1SHA512@' \ -e 's@/var/spool/mail@/var/mail@'
If you built Shadow with Cracklib support, execute this sed to correct the path to the Cracklib dictionary:
sed -i 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@' /etc/login.defs
Move a misplaced program to its proper location:
mv -v /usr/bin/passwd /bin
This package contains utilities to add, modify, and delete
users and groups; set and change their passwords; and perform
other administrative tasks. For a full explanation of what
password shadowing
means, see the doc/HOWTO
file
within the unpacked source tree. If using Shadow support,
keep in mind that programs which need to verify passwords
(display managers, FTP programs, pop3 daemons, etc.) must be
Shadow-compliant. That is, they need to be able to work with
shadowed passwords.
To enable shadowed passwords, run the following command:
pwconv
To enable shadowed group passwords, run:
grpconv
To view or change the default settings for new user accounts
that you create, you can edit /etc/default/useradd
. See man useradd or
http://cblfs.cross-lfs.org/index.php/Configuring_for_Adding_Users
for more information.
Choose a password for user root
and set it by running:
passwd root
Used to change the maximum number of days between obligatory password changes |
|
Used to change a user's full name and other information |
|
Used to update group passwords in batch mode |
|
Used to update the passwords of an entire series of user accounts |
|
Used to change a user's default login shell |
|
Checks and enforces the current password expiration policy |
|
Is used to examine the log of login failures, to set a maximum number of failures before an account is blocked, or to reset the failure count |
|
Is used to add and delete members and administrators to groups |
|
Creates a group with the given name |
|
Deletes the group with the given name |
|
Allows a user to administer his/her own group membership list without the requirement of superuser privileges |
|
Is used to modify the given group's name or GID |
|
Verifies the integrity of the group files
|
|
Creates or updates the shadow group file from the normal group file |
|
Updates |
|
Reports the most recent login of all users or of a given user |
|
Is used by the system to let users sign on |
|
Is a daemon used to enforce restrictions on log-on time and ports |
|
Is used to change the current GID during a login session |
|
Is used to create or update an entire series of user accounts |
|
Displays a message that an account is not available. Designed to be used as the default shell for accounts that have been disabled |
|
Is used to change the password for a user or group account |
|
Verifies the integrity of the password files
|
|
Creates or updates the shadow password file from the normal password file |
|
Updates |
|
Executes a given command while the user's GID is set to that of the given group |
|
Runs a shell with substitute user and group IDs |
|
Creates a new user with the given name, or updates the default new-user information |
|
Deletes the given user account |
|
Is used to modify the given user's login name, User Identification (UID), shell, initial group, home directory, etc. |
|
Edits the |
|
Edits the |
The Coreutils package contains utilities for showing and setting the basic system characteristics.
A known issue with the uname program from this
package is that the -p
switch
always returns unknown
.
The following patch fixes this behavior for all
architectures:
patch -Np1 -i ../coreutils-8.21-uname-1.patch
Now prepare Coreutils for compilation:
FORCE_UNSAFE_CONFIGURE=1 \ ./configure --prefix=/usr \ --enable-no-install-program=kill,uptime \ --enable-install-program=hostname
The meaning of the configure options:
FORCE_UNSAFE_CONFIGURE=1
Forces Coreutils to compile when using the root user.
Compile the package:
make
The test suite of Coreutils makes several assumptions about the presence of system users and groups that are not valid within the minimal environment that exists at the moment. Therefore, additional items need to be set up before running the tests. Skip down to “Install the package” if not running the test suite.
Create two dummy
groups and a
dummy
user:
echo "dummy1:x:1000:" >> /etc/group echo "dummy2:x:1001:dummy" >> /etc/group echo "dummy:x:1000:1000::/root:/bin/bash" >> /etc/passwd
Now the test suite is ready to be run. First, run the tests
that are meant to be run as user root
:
make NON_ROOT_USERNAME=dummy SUBDIRS= check-root
The testsuite will now be run as the dummy
user. Fix the permissions for a few
files to allow this:
chown -Rv dummy .
Then run the remainder of the tests as the dummy
user:
su dummy -s /bin/bash \ -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes -k check || true"
When testing is complete, remove the dummy
user and groups:
sed -i '/dummy/d' /etc/passwd /etc/group
Install the package:
make install
Move programs to the locations specified by the FHS:
mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date} /bin mv -v /usr/bin/{dd,df,echo,false,hostname,ln,ls,mkdir,mknod} /bin mv -v /usr/bin/{mv,pwd,rm,rmdir,stty,true,uname} /bin mv -v /usr/bin/chroot /usr/sbin
Other Coreutils programs are used by some of the scripts in
the CLFS-Bootscripts package. As /usr
may not be available during the early
stages of booting, those binaries need to be on the root
partition:
mv -v /usr/bin/{[,basename,head,install,nice} /bin mv -v /usr/bin/{readlink,sleep,sync,test,touch} /bin ln -svf ../../bin/install /usr/bin
Base64 encode/decode data and print to standard output |
|
Strips any path and a given suffix from a file name |
|
Concatenates files to standard output |
|
Changes security context for files and directories |
|
Changes the group ownership of files and directories |
|
Changes the permissions of each file to the given mode; the mode can be either a symbolic representation of the changes to make or an octal number representing the new permissions |
|
Changes the user and/or group ownership of files and directories |
|
Runs a command with the specified directory as the
|
|
Prints the Cyclic Redundancy Check (CRC) checksum and the byte counts of each specified file |
|
Compares two sorted files, outputting in three columns the lines that are unique and the lines that are common |
|
Copies files |
|
Splits a given file into several new files, separating them according to given patterns or line numbers and outputting the byte count of each new file |
|
Prints sections of lines, selecting the parts according to given fields or positions |
|
Displays the current time in the given format, or sets the system date |
|
Copies a file using the given block size and count, while optionally performing conversions on it |
|
Reports the amount of disk space available (and used) on all mounted file systems, or only on the file systems holding the selected files |
|
Lists the contents of each given directory (the same as the ls command) |
|
Outputs commands to set the |
|
Strips the non-directory suffix from a file name |
|
Reports the amount of disk space used by the current directory, by each of the given directories (including all subdirectories) or by each of the given files |
|
Displays the given strings |
|
Runs a command in a modified environment |
|
Converts tabs to spaces |
|
Evaluates expressions |
|
Prints the prime factors of all specified integer numbers |
|
Does nothing, unsuccessfully; it always exits with a status code indicating failure |
|
Reformats the paragraphs in the given files |
|
Wraps the lines in the given files |
|
Reports a user's group memberships |
|
Prints the first ten lines (or the given number of lines) of each given file |
|
Reports the numeric identifier (in hexadecimal) of the host |
|
Reports or sets the name of the host |
|
Reports the effective user ID, group ID, and group memberships of the current user or specified user |
|
Copies files while setting their permission modes and, if possible, their owner and group |
|
Joins the lines that have identical join fields from two separate files |
|
Creates a hard link with the given name to a file |
|
Makes hard links or soft (symbolic) links between files |
|
Reports the current user's login name |
|
Lists the contents of each given directory |
|
Reports or checks Message Digest 5 (MD5) checksums |
|
Creates directories with the given names |
|
Creates First-In, First-Outs (FIFOs), a “named pipe” in UNIX parlance, with the given names |
|
Creates device nodes with the given names; a device node is a character special file, a block special file, or a FIFO |
|
Creates temporary files in a secure manner; it is used in scripts |
|
Moves or renames files or directories |
|
Runs a program with modified scheduling priority |
|
Numbers the lines from the given files |
|
Runs a command immune to hangups, with its output redirected to a log file |
|
Prints the number of processing units available to the current process |
|
Dumps files in octal and other formats |
|
Merges the given files, joining sequentially corresponding lines side by side, separated by tab characters |
|
Checks if file names are valid or portable |
|
Is a lightweight finger client; it reports some information about the given users |
|
Paginates and columnates files for printing |
|
Prints the environment |
|
Prints the given arguments according to the given format, much like the C printf function |
|
Produces a permuted index from the contents of the given files, with each keyword in its context |
|
Reports the name of the current working directory |
|
Reports the value of the given symbolic link |
|
Prints the resolved path |
|
Removes files or directories |
|
Removes directories if they are empty |
|
Runs a command with specified security context |
|
Prints a sequence of numbers within a given range and with a given increment |
|
Prints or checks 160-bit Secure Hash Algorithm 1 (SHA1) checksums |
|
Prints or checks SHA224 checksums |
|
Prints or checks SHA256 checksums |
|
Prints or checks SHA384 checksums |
|
Prints or checks SHA512 checksums |
|
Overwrites the given files repeatedly with complex patterns, making it difficult to recover the data |
|
Write a random permutation of the input lines to standard output or a file |
|
Pauses for the given amount of time |
|
Sorts the lines from the given files |
|
Splits the given file into pieces, by size or by number of lines |
|
Displays file or filesystem status |
|
Runs a command with modified buffering operations for its standard streams |
|
Sets or reports terminal line settings |
|
Prints checksum and block counts for each given file |
|
Flushes file system buffers; it forces changed blocks to disk and updates the super block |
|
Concatenates the given files in reverse |
|
Prints the last ten lines (or the given number of lines) of each given file |
|
Reads from standard input while writing both to standard output and to the given files |
|
Compares values and checks file types |
|
Runs a command with a time limit |
|
Changes file timestamps, setting the access and modification times of the given files to the current time; files that do not exist are created with zero length |
|
Translates, squeezes, and deletes the given characters from standard input |
|
Does nothing, successfully; it always exits with a status code indicating success |
|
Shrinks or expands a file to the specified size |
|
Performs a topological sort; it writes a completely ordered list according to the partial ordering in a given file |
|
Reports the file name of the terminal connected to standard input |
|
Reports system information |
|
Converts spaces to tabs |
|
Discards all but one of successive identical lines |
|
Removes the given file |
|
Reports the names of the users currently logged on |
|
Is the same as ls -l |
|
Reports the number of lines, words, and bytes for each given file, as well as a total line when more than one file is given |
|
Reports who is logged on |
|
Reports the user name associated with the current effective user ID |
|
Repeatedly outputs “y” or a given string until killed |
|
Library used by stdbuf |
The Iana-Etc package provides data for network services and protocols.
This package has the option of downloading updated data when internet access is available. If /etc/resolv.conf has a nameserver entry and internet access is available at this step, then apply the IANA get patch and get the updated data:
patch -Np1 -i ../iana-etc-2.30-get_fix-1.patch make get
Do not apply the following patch.
The following patch updates the services and protocol files:
patch -Np1 -i ../iana-etc-2.30-numbers_update-20120610-2.patch
The following command converts the raw data provided by IANA
into the correct formats for the /etc/protocols
and /etc/services
data files:
make
This package does not come with a test suite.
Install the package:
make install
The M4 package contains a macro processor.
Prepare M4 for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
copies the given files while expanding the macros that they contain. These macros are either built-in or user-defined and can take any number of arguments. Besides performing macro expansion, m4 has built-in functions for including named files, running Unix commands, performing integer arithmetic, manipulating text, recursion, etc. The m4 program can be used either as a front-end to a compiler or as a macro processor in its own right. |
The Bison package contains a parser generator.
The configure script does not determine the correct value for the following. Set the value manually:
echo "ac_cv_prog_lex_is_flex=yes" > config.cache
Prepare Bison for compilation:
./configure --prefix=/usr --cache-file=config.cache
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
Generates, from a series of rules, a program for analyzing the structure of text files; Bison is a replacement for Yacc (Yet Another Compiler Compiler) |
|
A wrapper for bison, meant for
programs that still call yacc instead of
bison; it calls
bison
with the |
|
The Yacc library containing implementations of Yacc-compatible yyerror and main functions; this library is normally not very useful, but POSIX requires it |
The Libtool package contains the GNU generic library support script. It wraps the complexity of using shared libraries in a consistent, portable interface.
Prepare Libtool for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Flex package contains a utility for generating programs that recognize patterns in text.
Prepare Flex for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
There are some packages that expect to find the lex
library in /usr/lib
. Create a symlink to account for
this:
ln -sv libfl.a /usr/lib/libl.a
A few programs do not know about flex yet and try to run its
predecessor, lex. To support those
programs, create a wrapper script named lex
that calls flex
in lex emulation mode:
cat > /usr/bin/lex << "EOF"
#!/bin/sh
# Begin /usr/bin/lex
exec /usr/bin/flex -l "$@"
# End /usr/bin/lex
EOF
chmod -v 755 /usr/bin/lex
A tool for generating programs that recognize patterns in text; it allows for the versatility to specify the rules for pattern-finding, eradicating the need to develop a specialized program |
|
Link to flex which makes it generate C++ scanner classes |
|
A script that runs flex in lex emulation mode |
|
The |
|
The |
The IPRoute2 package contains programs for basic and advanced IPV4-based networking.
By default, this package builds the arpd program, which is dependent on Berkeley DB. Because arpd is not a very common requirement on a base Linux system, remove the dependency on Berkeley DB by using the commands below. If the arpd binary is needed, instructions for compiling Berkeley DB can be found in CBLFS at http://cblfs.cross-lfs.org/index.php/Berkeley_DB.
sed -i '/^TARGETS/s@arpd@@g' misc/Makefile sed -i '/ARPD/d' Makefile rm -v man/man8/arpd.8
Remove unused libnl headers:
sed -i '/netlink\//d' ip/ipl2tp.c
Compile the package:
make DESTDIR= DOCDIR=/usr/share/doc/iproute2 \ MANDIR=/usr/share/man
The meaning of the make option:
DESTDIR=
This option overrides the default DESTDIR of /usr, so
that that the IPRoute2 binaries will be installed into
/sbin
. This is the
correct location according to the FHS, because some of
the IPRoute2 binaries are used by the CLFS-Bootscripts
package.
DOCDIR=/usr/share/doc/iproute2
MANDIR=/usr/share/man
The DESTDIR=/ parameter would cause documentation to be
installed into /share/doc
and /share/man
. These
options ensure the docs are installed to the correct
locations.
This package does not come with a test suite.
Install the package:
make DESTDIR= DOCDIR=/usr/share/doc/iproute2 \ MANDIR=/usr/share/man install
Connection status utility |
|
Needs description |
|
A shell script wrapper for the ip command |
|
Shows the interface statistics, including the amount of transmitted and received packets by interface |
|
The main executable. It has several different functions:
ip link ip addr allows users to look at addresses and their properties, add new addresses, and delete old ones ip neighbor allows users to look at neighbor bindings and their properties, add new neighbor entries, and delete old ones ip rule allows users to look at the routing policies and change them ip route allows users to look at the routing table and change routing table rules ip tunnel allows users to look at the IP tunnels and their properties, and change them ip maddr allows users to look at the multicast addresses and their properties, and change them ip mroute allows users to set, change, or delete the multicast routing ip monitor allows users to continously monitor the state of devices, addresses and routes |
|
Provides Linux network statistics. It is a generalized and more feature-complete replacement for the old rtstat program |
|
Shows network statistics |
|
A component of ip route. This is for flushing the routing tables |
|
A component of ip route. This is for listing the routing tables |
|
Displays the contents of |
|
Route monitoring utility |
|
Converts the output of ip -o back into a readable form |
|
Route status utility |
|
Similar to the netstat command; shows active connections |
|
Traffic Controlling Executable; this is for Quality Of Service (QOS) and Class Of Service (COS) implementations tc qdisc allows users to setup the queueing discipline tc class allows users to setup classes based on the queuing discipline scheduling tc estimator allows users to estimate the network flow into a network tc filter allows users to setup the QOS/COS packet filtering tc policy allows users to setup the QOS/COS policies |
The Perl package contains the Practical Extraction and Report Language.
By default, Perl's Compress::Raw::Zlib module builds and links against its own internal copy of Zlib. The following command will tell it to use the system-installed Zlib:
sed -i -e '/^BUILD_ZLIB/s/True/False/' \ -e '/^INCLUDE/s,\./zlib-src,/usr/include,' \ -e '/^LIB/s,\./zlib-src,/usr/lib,' \ cpan/Compress-Raw-Zlib/config.in
If you are following the boot method you will need to enable the loopback device as well as set a hostname for some of the tests:
ip link set lo up hostname clfs
Before starting to configure, create a basic /etc/hosts
file which will be referenced by
one of Perl's configuration files as well as used by the
testsuite:
echo "127.0.0.1 localhost $(hostname)" > /etc/hosts
To have full control over the way Perl is set up, you can run the interactive Configure script and hand-pick the way this package is built. If you prefer instead to use the defaults that Perl auto-detects, prepare Perl for compilation with:
./configure.gnu --prefix=/usr \ -Dvendorprefix=/usr \ -Dman1dir=/usr/share/man/man1 \ -Dman3dir=/usr/share/man/man3 \ -Dpager="/bin/less -isR" \ -Dusethreads -Duseshrplib
The meaning of the configure option:
-Dpager="/bin/less
-isR"
This corrects an error in the way that perldoc invokes the less program.
-Dman1dir=/usr/share/man/man1
-Dman3dir=/usr/share/man/man3
Since Groff is not installed yet, configure.gnu thinks that we do not want man pages for Perl. Issuing these parameters overrides this decision.
-Dusethreads
This tells Perl to use threads.
-Duseshrplib
This tells Perl to build a shared libperl.
Compile the package:
make
To test the results, issue: make test
.
Install the package:
make install
Translates awk to Perl |
|
Dumps C structures as generated from cc -g -S |
|
Queries or changes configuration of Perl modules |
|
A commandline frontend to Module::CoreList |
|
Shell script that provides a command interface to CPAN.pm |
|
The CPANPLUS distribution creator |
|
The CPANPLUS launcher |
|
Perl script that (description needed) |
|
Builds a Perl extension for the Encode module from either Unicode Character Mappings or Tcl Encoding Files |
|
Translates find commands to Perl |
|
Converts |
|
Converts |
|
A shell script for examining installed Perl modules, and can even create a tarball from an installed module |
|
Converts data between certain input and output formats |
|
Can be used to configure the |
|
Combines some of the best features of C, sed, awk and sh into a single swiss-army-knife language |
|
A hard link to perl |
|
Used to generate bug reports about Perl, or the modules that come with it, and mail them |
|
Displays a piece of documentation in pod format that is embedded in the Perl installation tree or in a Perl script |
|
The Perl Installation Verification Procedure; it can be used to verify that Perl and its libraries have been installed correctly |
|
Used to generate thank you messages to mail to the Perl developers |
|
A Perl version of the character encoding converter iconv |
|
A rough tool for converting Perl4 |
|
Converts files from pod format to HTML format |
|
Converts files from pod format to LaTeX format |
|
Converts pod data to formatted *roff input |
|
Converts pod data to formatted ASCII text |
|
Prints usage messages from embedded pod docs in files |
|
Checks the syntax of pod format documentation files |
|
Displays selected sections of pod documentation |
|
A command-line tool for running tests against Test::Harness |
|
A Perl version of the stream editor sed |
|
Dumps C structures as generated from cc -g -S stabs |
|
A tar-like program written in Perl |
|
A Perl program that compares an extracted archive with an unextracted one |
|
A Perl program that applies pattern matching to the contents of files in a tar archive |
|
Translates sed to Perl |
|
Prints or checks SHA checksums |
|
Is used to force verbose warning diagnostics in Perl |
|
Converts Perl XS code into C code |
|
Displays details about the internal structure of a Zip file |
The Readline package is a set of libraries that offers command-line editing and history capabilities.
The following patch contains updates from the maintainer. The maintainer of Readline only releases these patches to fix serious issues:
patch -Np1 -i ../readline-6.2-branch_update-3.patch
Prepare Readline for compilation:
./configure --prefix=/usr --libdir=/lib
Compile the package:
make SHLIB_LIBS=-lncurses
This package does not come with a test suite.
Install the package:
make install
Install the documentation:
make install-doc
Now move the static libraries to a more appropriate location:
mv -v /lib/lib{readline,history}.a /usr/lib
Next, remove the .so
files in
/lib
and relink them into
/usr/lib
.
rm -v /lib/lib{readline,history}.so ln -svf ../../lib/libreadline.so.6 /usr/lib/libreadline.so ln -svf ../../lib/libhistory.so.6 /usr/lib/libhistory.so
The Autoconf package contains programs for producing shell scripts that can automatically configure source code.
Prepare Autoconf for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check VERBOSE=yes
. 17
tests are skipped that use Automake and different GCC
languages. For full test coverage, Autoconf can be re-tested
after Automake has been installed.
Install the package:
make install
Produces shell scripts that automatically configure software source code packages to adapt to many kinds of Unix-like systems. The configuration scripts it produces are independent—running them does not require the autoconf program. |
|
A tool for creating template files of C #define statements for configure to use |
|
A wrapper for the M4 macro processor |
|
Automatically runs autoconf, autoheader, aclocal, automake, gettextize, and libtoolize in the correct order to save time when changes are made to autoconf and automake template files |
|
Helps to create a |
|
Modifies a |
|
Helps when writing |
The Automake package contains programs for generating Makefiles for use with Autoconf.
Prepare Automake for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
A script that installs aclocal-style M4 files |
|
Generates |
|
A hard link to aclocal |
|
A tool for automatically generating |
|
A hard link to automake |
|
A wrapper for compilers |
|
A script that attempts to guess the canonical triplet for the given build, host, or target architecture |
|
A configuration validation subroutine script |
|
A script for compiling a program so that dependency information is generated in addition to the desired output |
|
Byte-compiles Emacs Lisp code |
|
A script that installs a program, script, or data file |
|
A script that prints the modification time of a file or directory |
|
A script acting as a common stub for missing GNU programs during an installation |
|
A script that creates a directory tree |
|
Compiles a Python program |
|
A script to create a symlink tree of a directory tree |
|
A wrapper for lex and yacc |
The Bash package contains the Bourne-Again SHell.
The following patch contains updates from the maintainer. The maintainer of Bash only releases these patches to fix serious issues:
patch -Np1 -i ../bash-4.2-branch_update-7.patch
Prepare Bash for compilation:
./configure --prefix=/usr --bindir=/bin \ --without-bash-malloc --with-installed-readline
The meaning of the configure option:
--with-installed-readline
This option tells Bash to use the readline
library that is already
installed on the system rather than using its own
readline version.
Compile the package:
make
To test the results, issue: make tests
.
Install the package:
make htmldir=/usr/share/doc/bash-4.2 install
Run the newly compiled bash program (replacing the one that is currently being executed):
exec /bin/bash --login +h
The parameters used make the bash process an interactive login shell and continue to disable hashing so that new programs are found as they become available.
A widely-used command interpreter; it performs many types of expansions and substitutions on a given command line before executing it, thus making this interpreter a powerful tool |
|
A shell script to help the user compose and mail standard formatted bug reports concerning bash |
|
A symlink to the bash program; when invoked as sh, bash tries to mimic the startup behavior of historical versions of sh as closely as possible, while conforming to the POSIX standard as well |
The Bc pacakge contains an arbitrary precision numeric processing language.
Prepare Bc for compilation:
./configure --prefix=/usr --with-readline
Compile the package:
make
To test the results, issue: echo "quit" | ./bc/bc -l
Test/checklib.b
Install the package:
make install
The Bzip2 package contains programs for compressing and decompressing files. Compressing text files with bzip2 yields a much better compression percentage than with the traditional gzip.
By default Bzip2 creates some symlinks that use absolute pathnames. The following sed will cause them to be created with relative paths instead:
sed -i -e 's:ln -s -f $(PREFIX)/bin/:ln -s :' Makefile
The Bzip2 package does not contain a configure script. Compile it with:
make -f Makefile-libbz2_so make clean
The -f
flag will
cause Bzip2 to be built using a different Makefile
file, in this case the
Makefile-libbz2_so
file, which
creates a dynamic libbz2.so
library and links the Bzip2 utilities against it.
Recompile the package using a non-shared library and test it:
make
Install the programs:
make PREFIX=/usr install
Install the shared bzip2 binary into the
/bin
directory, make some
necessary symbolic links, and clean up:
cp -v bzip2-shared /bin/bzip2 cp -av libbz2.so* /lib ln -sv ../../lib/libbz2.so.1.0 /usr/lib/libbz2.so rm -v /usr/bin/{bunzip2,bzcat,bzip2} ln -sv bzip2 /bin/bunzip2 ln -sv bzip2 /bin/bzcat
Decompresses bzipped files |
|
Decompresses to standard output |
|
Runs cmp on bzipped files |
|
Runs diff on bzipped files |
|
Runs egrep on bzipped files |
|
Runs fgrep on bzipped files |
|
Runs grep on bzipped files |
|
Compresses files using the Burrows-Wheeler block sorting text compression algorithm with Huffman coding; the compression rate is better than that achieved by more conventional compressors using “Lempel-Ziv” algorithms, like gzip |
|
Tries to recover data from damaged bzipped files |
|
Runs less on bzipped files |
|
Runs more on bzipped files |
|
The library implementing lossless, block-sorting data compression, using the Burrows-Wheeler algorithm |
The Diffutils package contains programs that show the differences between files or directories.
Prepare Diffutils for compilation:
./configure --prefix=/usr
Diffutils wants ed as the default editor. The following sed will change the default to vim:
sed -i 's@\(^#define DEFAULT_EDITOR_PROGRAM \).*@\1"vi"@' lib/config.h
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The File package contains a utility for determining the type of a given file or files.
Prepare File for compilation:
./configure --prefix=/usr
Compile the package:
make
This package does not come with a test suite.
Install the package:
make install
The Gawk package contains programs for manipulating text files.
Prepare Gawk for compilation:
./configure --prefix=/usr --libexecdir=/usr/lib
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The Findutils package contains programs to find files. These programs are provided to recursively search through a directory tree and to create, maintain, and search a database (often faster than the recursive find, but unreliable if the database has not been recently updated).
Prepare Findutils for compilation:
./configure --prefix=/usr --libexecdir=/usr/lib/locate \ --localstatedir=/var/lib/locate
The meaning of the configure options:
--localstatedir
This option changes the location of the locate database to be
in /var/lib/locate
, which
is FHS-compliant.
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
The find
program is used by some of the scripts in the
CLFS-Bootscripts package. As /usr
may not be available during the early
stages of booting, the find binary needs to be on
the root partition:
mv -v /usr/bin/find /bin
The updatedb script needs to be modified to point to the new location for find:
sed -i 's@find:=${BINDIR}@find:=/bin@' /usr/bin/updatedb
Was formerly used to produce locate databases |
|
Was formerly used to produce locate databases; it is the ancestor of frcode. |
|
Searches given directory trees for files matching the specified criteria |
|
Is called by updatedb to compress the list of file names; it uses front-compression, reducing the database size by a factor of four to five. |
|
Searches through a database of file names and reports the names that contain a given string or match a given pattern |
|
Older version of find, using a different algorithm |
|
Updates the locate database; it scans the entire file system (including other file systems that are currently mounted, unless told not to) and puts every file name it finds into the database |
|
Can be used to apply a given command to a list of files |
The Gettext package contains utilities for internationalization and localization. These allow programs to be compiled with NLS (Native Language Support), enabling them to output messages in the user's native language.
Prepare Gettext for compilation:
./configure --prefix=/usr
Compile the package:
make
To test the results, issue: make check
.
Install the package:
make install
Copies standard Gettext infrastructure files into a source package |
|
Outputs a system-dependent table of character encoding aliases |
|
Outputs a system-dependent set of variables, describing how to set the runtime search path of shared libraries in an executable |
|
Substitutes environment variables in shell format strings |
|
Translates a natural language message into the user's language by looking up the translation in a message catalog |
|
Primarily serves as a shell function library for gettext |
|
Copies all standard Gettext files into the given top-level directory of a package to begin internationalizing it |
|
Displays a network hostname in various forms |
|
Filters the messages of a translation catalog according to their attributes and manipulates the attributes |
|
Concatenates and merges the given |
|
Compares two |
|
Finds the messages that are common to to the given
|
|
Converts a translation catalog to a different character encoding |
|
Creates an English translation catalog |
|
Applies a command to all translations of a translation catalog |
|
Applies a filter to all translations of a translation catalog |
|
Generates a binary message catalog from a translation catalog |
|
Extracts all messages of a translation catalog that match a given pattern or belong to some given source files |
|
Creates a new |
|
Combines two raw translations into a single file |
|
Decompiles a binary message catalog into raw translation text |
|
Unifies duplicate translations in a translation catalog |
|