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 d6cda5163a2b191bd1f67b49f251a5eb1157701a a7505c5cf4
Julien Lepiller authored 39 minutes ago
Last commit in Weblate Automatic BLFS commit based on d6cda5163a2b191bd1f67b49f251a5eb1157701a a7505c5cf4
Julien Lepiller authored 39 minutes ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/introduction/important/building-notes.po
Translation file Download blfs/fr/introduction/important/building-notes.po
Last change Oct. 27, 2024, 4:19 a.m.
Last author None
11 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 189 7,135 50,219
Translated 99% 188 98% 7,013 98% 49,240
Needs editing 1% 1 1% 122 1% 979
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 6 6% 460 6% 3,195
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 4 changes 0 changes 9 changes 161 changes 5 changes 12 changes 0 changes 0 changes 0 changes 14 changes 11 changes 116 changes 22 changes 40 changes 116 changes 213 changes 13 changes 0 changes 3 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

7,135
Hosted words
189
Hosted strings
99%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

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

String added in the repository
With <phrase revision='systemd'> <parameter>MemoryHigh=8G</parameter>, </phrase> <phrase revision='sysv'> <literal>8589934592</literal> (the output of <userinput>bc -e '8*2^30'</userinput>, 2^30 represents 2<superscript>30</superscript>, i.e. a Gigabyte) in the <filename>memory.high</filename> entry, </phrase> a soft limit of memory usage is set. If the processes in the cgroup (<command>make</command> and all the descendants of it) uses more than 8 GB of system memory in total, the kernel will throttle down the processes and try to reclaim the system memory from them. But they can still use more than 8 GB of system memory. If you want to make a hard limit instead, replace <phrase revision='systemd'> <parameter>MemoryHigh</parameter> with <parameter>MemoryMax</parameter>. </phrase> <phrase revision='sysv'> <filename>memory.high</filename> with <filename>memory.max</filename>. </phrase> But doing so will cause the processes killed if 8 GB is not enough for them.
Avec <phrase revision='systemd'><parameter>MemoryHigh=8G</parameter></phrase><phrase revision='sysv'><literal>8589934592</literal> (la sortie de <userinput>bc -e '8*2^30'</userinput>, 2^30 représentant 2<superscript>30</superscript>, c.-à-d. un gigaoctet) dans l'entrée <filename>memory.high</filename></phrase>, une limite souple pour l'utilisation de la mémoire est mise en place. Si les processus du cgroup (<command>make</command> et tous ses descendants) utilisent plus de 8&nbsp;Go de mémoire système en tout, le noyau va les ralentir et essayer de récupérer la mémoire système qui leur a alloué. Mais ils peuvent toujours utiliser plus de 8&nbsp;Go de mémoire système. Si vous voulez plutôt donner une limite nette, remplacez <phrase revision='systemd'><parameter>MemoryHigh</parameter> par <parameter>MemoryMax</parameter>.</phrase><phrase revision='sysv'><filename>memory.high</filename> par <filename>memory.max</filename>.</phrase> Mais cela fera tuer les processus si 8&nbsp;Go n'est pas suffisant pour eux.
12 days ago
User avatar None

Source string changed
With <phrase revision='systemd'> <parameter>MemoryHigh=8G</parameter>, </phrase> <phrase revision='sysv'> <literal>8589934592</literal> (the output of <userinput>bc -e '8*2^30'</userinput>, 2^30 represents 2<superscript>30</superscript>, i.e. a Gigabyte) in the <filename>memory.high</filename> entry, </phrase>, a soft limit of memory usage is set. If the processes in the cgroup (<command>make</command> and all the descendants of it) uses more than 8 GB of system memory in total, the kernel will throttle down the processes and try to reclaim the system memory from them. But they can still use more than 8 GB of system memory. If you want to make a hard limit instead, replace <phrase revision='systemd'> <parameter>MemoryHigh</parameter> with <parameter>MemoryMax</parameter>. </phrase> <phrase revision='sysv'> <filename>memory.high</filename> with <filename>memory.max</filename>. </phrase> But doing so will cause the processes killed if 8 GB is not enough for them.
12 days ago
User avatar admin

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

Changes committed
Changes committed 2 months ago
User avatar admin

Translation changed
Most released rustc programs are provided as crates (source tarballs) which will query a server to check current versions of dependencies and then download them as necessary. These packages are built using <command>cargo --release</command>. In theory, you can manipulate the RUSTFLAGS to change the optimize-level (default for <option>--release</option> is 3, i. e. <option>-Copt-level=3</option>, like <option>-O3</option>) or to force it to build for the machine it is being compiled on, using <option>-Ctarget-cpu=native</option> but in practice this seems to make no significant difference.
La plupart des programmes rustc publiés sont fournis dans des archives (ou «&nbsp;crates&nbsp;») qui demanderont à un serveur de vérifier les versions actuelles des dépendances et les téléchargera au besoin. Ces paquets sont construits avec <command>cargo --release</command>. En théorie, on peut manipuler les RUSTFLAGS pour changer le niveau d'optimisation (la valeur par défaut pour <option>--release</option> est 3, c.-à-d. <option>-Copt-level=3</option>, comme <option>-O3</option>) ou pour forcer la construction pour la machine sur laquelle il est compilé, avec <literaloption>-Ctarget-cpu=native</literaloption> mais en pratique cela ne semble pas faire de réelle différence.
2 months ago
User avatar admin

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

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

Changes committed
Changes committed 2 months ago
User avatar admin

Translation changed
With <option>-Wl,-O1</option>, the linker will optimize the hash table to speed up the dynamic linking. Note that <option>-Wl,-O1</option> is completely unrelated to the compiler optimization flag <option>-O1</option>.
Avec <option>-Wl,-O1</option>, l'éditeur des liens optimisera la table de hash pour accélérer la liaison dynamique. Remarquez que <option>-Zl,-O1</option> est complètement décorrélée du drapeau d'optimisation du compilateur <option>-O1</option>.
2 months ago
Browse all translation changes