Source strings

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

Strings status

Strings Words Characters
65 2,338 15,634
All strings Browse Translate Zen
65 2,338 15,634
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 trunk
Last remote commit Automatic BLFS commit based on 2c934200354dfc23017574d3d5a7daba8069ee64 8c54d58a14
Julien Lepiller authored 9 hours ago
Last commit in Weblate Translated using Weblate (French) 65d75ab687
Weblate Admin authored 5 months ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/part3intro/toolchaintechnotes.po
Translation file Not available
Last change Jan. 27, 2024, 4:19 a.m.
Last author None
3 days ago

String statistics

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

Quick numbers

2,338
Hosted words
65
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

  1. Linux From Scratch
  2. part3intro_toolchaintechnotes
  3. English
is the machine where we build programs. Note that this machine is also referred to as the <quote>host.</quote>
6 months ago
User avatar None

Source string added

  1. Linux From Scratch
  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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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 is generally not an issue since glibc will always use the compiler 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>. The binary tools and kernel headers can be a bit more complicated. Therefore, we take no risks and use the available configure switches to enforce the correct selections. 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. Note the use of <parameter>CC="$LFS_TGT-gcc"</parameter> (with <envar>$LFS_TGT</envar> expanded) to control which binary tools are used and the use of the <parameter>-nostdinc</parameter> and <parameter>-isystem</parameter> flags to control the compiler's include search path. 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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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.
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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.)
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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>
a year ago
User avatar None

Source string added

  1. Linux From Scratch
  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:
a year ago
Browse all translation changes