Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 100% 0 0 0 0 1 0 1
French 100% 0 0 0 0 6 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 trunk
Last remote commit Automatic BLFS commit based on 5bf03fdf81fb303b45c2ab19555b98853e822770 6f88856c49
Julien Lepiller authored an hour ago
Last commit in Weblate Automatic BLFS commit based on 5bf03fdf81fb303b45c2ab19555b98853e822770 6f88856c49
Julien Lepiller authored an hour ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/introduction/important/building-notes.po
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 567 21,633 152,037
Source 189 7,211 50,679
Translated 100% 567 100% 21,633 100% 152,037
Needs editing 0% 0 0% 0 0% 0
Read-only 33% 189 33% 7,211 33% 50,679
Failing checks 1% 7 2% 644 2% 4,380
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 10 changes 325 changes 5 changes 25 changes 0 changes 7 changes 0 changes 14 changes 16 changes 160 changes 282 changes 44 changes 221 changes 239 changes 14 changes 0 changes 12 changes 0 changes 6 changes 0 changes 0 changes 8 changes 28 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

21,633
Hosted words
567
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “blfs/fr/introduction/important/building-notes.po” file was changed. 2 days ago
User avatar None

String updated in the repository
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
Par le passé, il existait un Hardened LFS (LFS durci) où gcc (une version beaucoup plus vieille) était forcé à utiliser le durcissement (avec des options pour les désactiver au cas par cas). Les livres LFS et BLFS actuels portent encore une partie de cet esprit en activant PIE (<option>-fPIE -pie</option>) et SSP (<option>-fstack-protector-strong</option>) dans les options par défaut de GCC et de clang. De plus, l'éditeur des liens (<command>ld</command>) a également activé <option>-Wl,-z,relro</option> ce qui rend une partie de la table globale de décalage (GOT) immuable par défaut depuis Binutils 2.27. Ce dont on parle ici est différent — vous devrez déjà vous assurer que le paquet utilise bien vos options supplémentaires et qu'il ne les écrase pas.
2 days ago
User avatar None

String updated in the repository
Note that the <option>-j</option> switches only limits the parallel jobs started by <command>make</command> or <command>ninja</command>, but each job may still spawn its own processes or threads. For example, some tests of packages can spawn multiple threads for testing thread safety properties. There is no generic way for the building system to know the number of processes or threads spawned by a job. So generally we should not consider the value passed with <option>-j</option> a hard limit of the number of logical cores to use. Read <xref linkend='build-in-cgroup'/> if you want to set such a hard limit.
Remarquez que les options <option>-j</option> ne limitent que les tâche parallèles démarrées par <command>make</command> ou <command>ninja</command>, mais chaque tâche peut encore générer ses propres processus ou threads. Par exemple, certains tests des paquets peuvent créer plusieurs threads pour tester les propriétés de sûreté en parallèle. Il n'y a pas de manière générique pour un système de construction de connaître le nombre de processus ou de threads générés par une tâche. En général, il ne faut pas considérer la valeur passée avec <option>-j</option> comme une limite en dur sur le nombre de cœurs logiques à utiliser. Consultez <xref linkend='build-in-cgroup'/> si vous voulez mettre en place ce genre de limite.
2 days ago
User avatar None

Changes committed
Changes committed 2 days ago
User avatar admin

Comment added

the linker (singular) have (plural) also enabled ...

2 days ago
User avatar admin

Translation completed
Translation completed 2 days ago
User avatar admin

Translation changed
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
Par le passé, il existait un Hardened LFS (LFS durci) où gcc (une version beaucoup plus vieille) était forcé à utiliser le durcissement (avec des options pour les désactiver au cas par cas). Les livres LFS et BLFS actuels portent encore une partie de cet esprit en activant PIE (<option>-fPIE -pie</option>) et SSP (<option>-fstack-protector-strong</option>) dans les options par défaut de GCC et de clang. De plus, les 'éditeurs des liens (<command>ld.bfd</command> et <command>ld.gold</command>) ont aussi) a également activé <option>-Wl,-z,relro</option> ce qui rend une partie de la table globale de décalage (GOT) immuable par défaut depuis Binutils 2.27. Ce dont on parle ici est différent — vous devrez déjà vous assurer que le paquet utilise bien vos options supplémentaires et qu'il ne les écrase pas.
2 days ago
User avatar admin

Translation changed
Note that the <option>-j</option> switches only limits the parallel jobs started by <command>make</command> or <command>ninja</command>, but each job may still spawn its own processes or threads. For example, some tests of packages can spawn multiple threads for testing thread safety properties. There is no generic way for the building system to know the number of processes or threads spawned by a job. So generally we should not consider the value passed with <option>-j</option> a hard limit of the number of logical cores to use. Read <xref linkend='build-in-cgroup'/> if you want to set such a hard limit.
Remarquez que les options <option>-j</option> ne limitent que les tâche parallèles démarrées par <command>make</command> ou <command>ninja</command>, mais chaque tâche peut encore générer ses propres processus ou threads. Par exemple, <command>ld.gold</command> utilisera plusieurs threads pour l'édition des liens, et certains tests des paquets peuvent créer plusieurs threads pour tester les propriétés de sûreté en parallèle. Il n'y a pas de manière générique pour un système de construction de connaître le nombre de processus ou de threads générés par une tâche. En général, il ne faut pas considérer la valeur passée avec <option>-j</option> comme une limite en dur sur le nombre de cœurs logiques à utiliser. Consultez <xref linkend='build-in-cgroup'/> si vous voulez mettre en place ce genre de limite.
2 days ago
User avatar None

Resource updated
The “blfs/pt_BR/introduction/important/building-notes.po” file was changed. 2 weeks ago
User avatar None

String updated in the repository
In the past, there was Hardened LFS where gcc (a much older version) was forced to use hardening (with options to turn some of it off on a per-package basis). The current LFS and BLFS books are carrying forward a part of its spirit by enabling PIE (<option>-fPIE -pie</option>) and SSP (<option>-fstack-protector-strong</option>) as the defaults for GCC and clang. And, the linker (<command>ld</command>) have also enabled <option>-Wl,-z,relro</option> which makes a part of the Global Offset Table (GOT) immutable, by default since Binutils 2.27. What is being covered here is different - first you have to make sure that the package is indeed using your added flags and not over-riding them.
No passado, existia o LFS Reforçado, onde o gcc (uma versão muito mais antiga) era forçado a usar o reforçamento (com opções para desativar parte dele na base do por pacote). Os livros atuais do LFS e BLFS estão levando adiante uma parte do espírito dele ao habilitar PIE (<option>-fPIE -pie</option>) e SSP (<option>-fstack-protector-strong</option>) como padrões para GCC e clang. E o lincador (<command>ld</command>) também habilitou <option>-Wl,-z,relro</option>, o que torna uma parte da Global Offset Table (GOT) imutável, por padrão desde Binutils 2.27. O que está sendo coberto aqui é diferente - primeiro você tem que ter certeza de que o pacote está realmente usando teus sinalizadores adicionados e não os substituindo.
2 weeks ago
Browse all component changes