Source strings

65 Strings 100%
Browse Translate
2,306 Words 100%
15,427 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
65 2,306 15,427
All strings Browse Translate Zen
65 2,306 15,427
Read-only strings Browse Translate Zen
6 256 1,768
Strings with any failing checks Browse Translate Zen
1 12 179
Failing check: Ellipsis Browse Translate Zen
5 244 1,589
Failing check: Multiple failing checks Browse Translate Zen

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.2
Last remote commit Add sed-es d5df9b577b
Julien Lepiller authored 12 days ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-2/index/
File mask lfs/*/part3intro/toolchaintechnotes.po
Translation file Not available
Last change Sept. 5, 2024, 8:16 p.m.
Last author None
12 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 65 2,306 15,427
Translated 100% 65 100% 2,306 100% 15,427
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 65 100% 2,306 100% 15,427
Failing checks 9% 6 11% 256 11% 1,768
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

2,306
Hosted words
65
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
Next up: sanitized Linux API headers. These allow the standard C library (glibc) to interface with features that the Linux kernel will provide.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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.)
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
<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>
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
The next package installed is gcc. An example of what can be seen during its run of <command>configure</command> is:
13 days ago
User avatar None

Source string added

  1. Linux From Scratch 12.2
  2. part3intro_toolchaintechnotes
  3. English
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>).
13 days ago
Browse all translation changes