Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
chapter08_gettext 0 0 0 0 0 0 0
chapter08_glibc 100% 0 0 0 0 9 0 0
chapter08_gmp 100% 0 0 0 0 2 0 0
chapter08_gperf 0 0 0 0 0 0 0
chapter08_grep 0 0 0 0 0 0 0
chapter08_groff 0 0 0 0 0 0 0
chapter08_grub 100% 0 0 0 0 1 0 0
chapter08_gzip 0 0 0 0 0 0 0
chapter08_iana-etc 0 0 0 0 0 0 0
chapter08_inetutils 0 0 0 0 0 0 0
chapter08_intltool 0 0 0 0 0 0 0
chapter08_introduction 0 0 0 0 0 0 0
chapter08_iproute2 0 0 0 0 0 0 0
chapter08_jinja2 0 0 0 0 0 0 0
chapter08_kbd 100% 0 0 0 0 2 0 0
chapter08_kmod 100% 0 0 0 0 1 0 0
chapter08_less 0 0 0 0 0 0 0
chapter08_libcap 0 0 0 0 0 0 0
chapter08_libelf 0 0 0 0 0 0 0
chapter08_libffi 0 0 0 0 0 0 0
chapter08_libpipeline 0 0 0 0 0 0 0
chapter08_libtool 0 0 0 0 0 0 0
chapter08_libxcrypt 0 0 0 0 0 0 0
chapter08_lz4 0 0 0 0 0 0 0
chapter08_m4 0 0 0 0 0 0 0
chapter08_make 100% 0 0 0 0 1 0 0
chapter08_man-db 100% 0 0 0 0 2 0 0
chapter08_man-pages 0 0 0 0 0 0 0
chapter08_markupsafe 0 0 0 0 0 0 0
chapter08_meson 0 0 0 0 0 0 0
chapter08_mpc 0 0 0 0 0 0 0
chapter08_mpfr 0 0 0 0 0 0 0
chapter08_ncurses 100% 0 0 0 0 1 0 0
chapter08_ninja 0 0 0 0 0 0 0
chapter08_openssl 100% 0 0 0 0 3 0 0
chapter08_patch 100% 0 0 0 0 1 0 0
chapter08_perl 0 0 0 0 0 0 0
chapter08_pkgconf 0 0 0 0 0 0 0
chapter08_pkgmgt 0 0 0 0 0 0 0
chapter08_procps 100% 0 0 0 0 1 0 0
chapter08_psmisc 0 0 0 0 0 0 0
chapter08_python 0 0 0 0 0 0 0
chapter08_readline 100% 0 0 0 0 2 0 0
chapter08_sed 0 0 0 0 0 0 0
chapter08_setuptools 0 0 0 0 0 0 0
chapter08_shadow 100% 0 0 0 0 3 0 0
chapter08_stripping 100% 0 0 0 0 1 0 0
chapter08_sysklogd 100% 0 0 0 0 1 0 0
chapter08_systemd 100% 0 0 0 0 2 0 0
chapter08_sysvinit 0 0 0 0 0 0 0
chapter08_tar 0 0 0 0 0 0 0
chapter08_tcl 0 0 0 0 0 0 0
chapter08_texinfo 100% 0 0 0 0 1 0 0
chapter08_udev 0 0 0 0 0 0 0
chapter08_util-linux 0 0 0 0 0 0 0
chapter08_vim 0 0 0 0 0 0 0
chapter08_wheel 0 0 0 0 0 0 0
chapter08_xml-parser 0 0 0 0 0 0 0
chapter08_xz 0 0 0 0 0 0 0
chapter08_zlib 0 0 0 0 0 0 0
chapter08_zstd 0 0 0 0 0 0 0
chapter09_bootscripts 0 0 0 0 0 0 0
chapter09_chapter09 0 0 0 0 0 0 0
chapter09_clock 0 0 0 0 0 0 0
chapter09_consoled 100% 0 0 0 0 2 0 0
chapter09_etcshells 0 0 0 0 0 0 0
chapter09_inputrc 0 0 0 0 0 0 0
chapter09_introduction 0 0 0 0 0 0 0
chapter09_introductiond 100% 0 0 0 0 10 0 0
chapter09_locale 100% 0 0 0 0 1 0 0
chapter09_network 100% 0 0 0 0 3 0 0
chapter09_networkd 100% 0 0 0 0 3 0 0
chapter09_symlinks 100% 0 0 0 0 1 0 0
chapter09_systemd-custom 100% 0 0 0 0 1 0 0
chapter09_udev 100% 0 0 0 0 1 0 0
chapter09_usage 100% 0 0 0 0 2 0 0
chapter10_chapter10 0 0 0 0 0 0 0
chapter10_fstab 0 0 0 0 0 0 0
chapter10_grub 0 0 0 0 0 0 0
chapter10_introduction 0 0 0 0 0 0 0
chapter10_kernel 0 0 0 0 0 0 0
chapter10_kernel_highmem 0 0 0 0 0 0 0
chapter10_kernel_nvme 0 0 0 0 0 0 0
chapter10_kernel_systemd 100% 0 0 0 0 1 0 0
chapter10_kernel_sysv 100% 0 0 0 0 1 0 0
chapter10_kernel_x2apic 0 0 0 0 0 0 0
chapter11_afterlfs 0 0 0 0 0 0 0
chapter11_chapter11 0 0 0 0 0 0 0
chapter11_getcounted 0 0 0 0 0 0 0
chapter11_reboot 100% 0 0 0 0 1 0 0
chapter11_theend 100% 0 0 0 0 1 0 0
chapter11_whatnow 0 0 0 0 0 0 0
index 0 0 0 0 0 0 0
Glossary Linux From Scratch 12.2 0 0 0 0 0 0 0
part3intro_generalinstructions 0 0 0 0 0 0 0
part3intro_introduction 0 0 0 0 0 0 0
part3intro_part3intro 0 0 0 0 0 0 0
part3intro_toolchaintechnotes 100% 0 0 0 0 6 0 0
prologue_architecture 100% 0 0 0 0 1 0 0
prologue_audience 0 0 0 0 0 0 0

Overview

Project website www.linuxfromscratch.org
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,900,209
6 minutes ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 9,040 87,539 738,687
Translated 100% 9,040 100% 87,539 100% 738,687
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 9,040 100% 87,539 100% 738,687
Failing checks 1% 131 4% 3,714 4% 32,875
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 9,040 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

87,539
Hosted words
9,040
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added
Upon entering the chroot environment in <xref linkend="chapter-chroot-temporary-tools"/>, the temporary installations of programs needed for the proper operation of the toolchain are performed. From this point onwards, the core toolchain is self-contained and self-hosted. In <xref linkend="chapter-building-system"/>, final versions of all the packages needed for a fully functional system are built, tested, and installed.
5 months ago
User avatar None

Source string added
At the end of <xref linkend="chapter-temporary-tools"/> the native LFS compiler is installed. First binutils-pass2 is built, in the same <envar>DESTDIR</envar> directory as the other programs, then the second pass of gcc is constructed, omitting some non-critical libraries. Due to some weird logic in gcc's configure script, <envar>CC_FOR_TARGET</envar> ends up as <command>cc</command> when the host is the same as the target, but different from the build system. This is why <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is declared explicitly as one of the configuration options.
5 months ago
User avatar None

Source string added
As mentioned above, the standard C++ library is compiled next, followed in <xref linkend="chapter-temporary-tools"/> by other programs that must be cross-compiled to break circular dependencies at build time. The install step of all those packages uses the <envar>DESTDIR</envar> variable to force installation in the LFS filesystem.
5 months ago
User avatar None

Source string added
Next comes glibc. The most important considerations for building glibc are the compiler, binary tools, and kernel headers. The compiler and binary tools are generally not an issue since glibc will always those relating to the <parameter>--host</parameter> parameter passed to its configure script; e.g., in our case, the compiler will be <command>$LFS_TGT-gcc</command> and the <command>readelf</command> tool will be <command>$LFS_TGT-readelf</command>. The kernel headers can be a bit more complicated. Therefore, we take no risks and use the available configure switch to enforce the correct selection. After the run of <command>configure</command>, check the contents of the <filename>config.make</filename> file in the <filename class="directory">build</filename> directory for all important details. These items highlight an important aspect of the glibc package&mdash;it is very self-sufficient in terms of its build machinery, and generally does not rely on toolchain defaults.
5 months ago
User avatar None

Source string added
Next up: sanitized Linux API headers. These allow the standard C library (glibc) to interface with features that the Linux kernel will provide.
5 months ago
User avatar None

Source string added
Detailed information can be obtained from <command>gcc</command> by passing it the <parameter>-v</parameter> command line option while compiling a program. For example, <command>$LFS_TGT-gcc -v <replaceable>example.c</replaceable></command> (or without <command> $LFS_TGT-</command> if coming back later) will show detailed information about the preprocessor, compilation, and assembly stages, including <command>gcc</command>'s search paths for included headers and their order.
5 months ago
User avatar None

Source string added
This is important for the reasons mentioned above. It also demonstrates that gcc's configure script does not search the PATH directories to find which tools to use. However, during the actual operation of <command>gcc</command> itself, the same search paths are not necessarily used. To find out which standard linker <command>gcc</command> will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. (Again, remove the <command>$LFS_TGT-</command> prefix if coming back to this later.)
5 months ago
User avatar None

Source string added
<computeroutput>checking what assembler to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/as
checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</computeroutput>
5 months ago
User avatar None

Source string added
The next package installed is gcc. An example of what can be seen during its run of <command>configure</command> is:
5 months ago
User avatar None

Source string added
Binutils installs its assembler and linker in two locations, <filename class="directory">$LFS/tools/bin</filename> and <filename class="directory">$LFS/tools/$LFS_TGT/bin</filename>. The tools in one location are hard linked to the other. An important facet of the linker is its library search order. Detailed information can be obtained from <command>ld</command> by passing it the <parameter>--verbose</parameter> flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command> will illustrate the current search paths and their order. (Note that this example can be run as shown only while logged in as user <systemitem class="username">lfs</systemitem>. If you come back to this page later, replace <command>$LFS_TGT-ld</command> with <command>ld</command>).
5 months ago
Browse all changes for this language