Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 5 0 0
Chinese (Simplified) 32% 44 2,211 14,748 9 14 0 0
French 0 0 0 0 0 0 0
Greek 0% 65 2,338 15,634 65 0 0 0
Portuguese (Brazil) 0 0 0 0 0 0 0
Please sign in to see the alerts.

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.0
Last remote commit Add Portuguese (Brazil) BLFS 5a031b636f
Julien Lepiller authored 2 months ago
Last commit in Weblate Translated using Weblate (French) f1a0442a45
Weblate Admin authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask lfs/*/part3intro/toolchaintechnotes.po
10 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 325 11,690 78,170
Source 65 2,338 15,634
Translated 66% 216 61% 7,141 61% 47,788
Needs editing 10% 35 13% 1,635 14% 10,967
Read-only 20% 65 20% 2,338 20% 15,634
Failing checks 5% 19 7% 824 7% 5,887
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 22% 74 24% 2,914 24% 19,415
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 367 changes 0 changes 0 changes 0 changes 5 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
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

11,690
Hosted words
325
Hosted strings
66%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. French
Changes committed 7 months ago
User avatar admin

Translation changed

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. French
In order to fake a cross-compilation in LFS, the name of the host triplet is slightly adjusted by changing the &quot;vendor&quot; field in the <envar>LFS_TGT</envar> variable so it says &quot;lfs&quot;. We also use the <parameter>--with-sysroot</parameter> option when building the cross-linker and cross-compiler, to tell them where to find the needed host files. This ensures that none of the other programs built in <xref linkend="chapter-temporary-tools"/> can link to libraries on the build machine. Only two stages are mandatory, plus one more for tests.
Pour simuler une compilation croisée dans LFS, le nom du triplet hôte est légèrement modifié en changeant le champ «&nbsp;fabriquant&nbsp;» dans la variable d’environnement <envar>LFS_TGT</envar> pour qu’il indique «&nbsp;lfs&nbsp;. Nous utilisons également l'option <parameter>--with-sysroot</parameter> lors de la construction de l'éditeur de liens et du compilateur croisés pour leur indiquer l’emplacement des fichiers hôte requis. Cette option permet de s’assurer qu'aucun autre programme construit dans le <xref linkend="chapter-temporary-tools"/> ne peut s’associer aux bibliothèques sur la machine de construction.Seules deux étapes sont obligatoires, en plus d’une étape supplémentaire destinée aux tests&nbsp;:.
7 months ago
User avatar admin

Translation changed

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. French
As an example, let us imagine the following scenario (sometimes referred to as <quote>Canadian Cross</quote>). We have a compiler on a slow machine only, let's call it machine A, and the compiler ccA. We also have a fast machine (B), but no compiler for (B), and we want to produce code for a third, slow machine (C). We will build a compiler for machine C in three stages.
Par exemple, imaginons le scénario suivant (parfois appelé <quote>Canadian Cross</quote>)&nbsp;: nous avons un compilateur sur une machine lente, que nous appellerons A, et le compilateur ccA. Nous avons également une machine rapide (B), mais aucun compilateur pour (B). Nous voulons produire du code pour une troisième machine, lente cette fois (C). Il y a trois étapes à suivre pour construire un compilateur destiné à la machine C&nbsp;:.
7 months ago
User avatar admin

Translation changed

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. French
Let us first define some terms used in this context.
Définissons d'abord certains termes utilisés dans ce contexte&nbsp;:.
7 months ago
User avatar admin

Contributor joined

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. French
Contributor joined 7 months ago
User avatar admin

Resource updated

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. Greek
File “lfs/el/part3intro/toolchaintechnotes.po” was added. 8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. Greek
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.
 
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. Greek
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.
 
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. Greek
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.
 
8 months ago
User avatar None

String updated in the repository

  1. Linux From Scratch 12.0
  2. part3intro_toolchaintechnotes
  3. Greek
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.
 
8 months ago
Browse all component changes