Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
Chinese (Simplified Han script) 36% 7 422 2,831 1 0 0 0
French 0 0 0 0 0 0 0
Greek 0% 11 559 3,705 11 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 9 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask lfs/*/chapter08/introduction.po
11 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 55 2,795 18,525
Source 11 559 3,705
Translated 67% 37 64% 1,814 64% 11,989
Needs editing 10% 6 12% 338 12% 2,257
Read-only 20% 11 20% 559 20% 3,705
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 21% 12 23% 643 23% 4,279
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 68 changes 1 change 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

2,795
Hosted words
55
Hosted strings
67%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Alert triggered
Component seems unused. 3 months ago
User avatar admin

Resource updated
File “lfs/el/chapter08/introduction.po” was added. a year ago
User avatar None

String updated in the repository
For a more complete discussion of libraries, see <ulink url="&blfs-book;introduction/libraries.html"> Libraries: Static or shared?</ulink> in the BLFS book.
 
a year ago
User avatar None

String updated in the repository
The procedures in this chapter remove or disable installation of most static libraries. Usually this is done by passing a <option>--disable-static</option> option to <command>configure</command>. In other cases, alternate means are needed. In a few cases, especially Glibc and GCC, the use of static libraries remains an essential feature of the package building process.
 
a year ago
User avatar None

String updated in the repository
In general, the LFS editors discourage building and installing static libraries. Most static libraries have been made obsolete in a modern Linux system. In addition, linking a static library into a program can be detrimental. If an update to the library is needed to remove a security problem, every program that uses the static library will need to be relinked with the new library. Since the use of static libraries is not always obvious, the relevant programs (and the procedures needed to do the linking) may not even be known.
 
a year ago
User avatar None

String updated in the repository
About Libraries
 
a year ago
User avatar None

String updated in the repository
The SBU values and required disk space include test suite data for all applicable packages in <xref linkend="chapter-building-system"/>. SBU values have been calculated using four CPU cores (-j4) for all operations unless specified otherwise.
 
a year ago
User avatar None

String updated in the repository
Before the installation instructions, each installation page provides information about the package, including a concise description of what it contains, approximately how long it will take to build, and how much disk space is required during this building process. Following the installation instructions, there is a list of programs and libraries (along with brief descriptions) that the package installs.
 
a year ago
User avatar None

String updated in the repository
On the other hand, we keep the optimizations enabled by the default configuration of the packages. In addition, we sometimes explicitly enable an optimized configuration provided by a package but not enabled by default. The package maintainers have already tested these configurations and consider them safe, so it's not likely they would break the build. Generally the default configuration already enables <option>-O2</option> or <option>-O3</option>, so the resulting system will still run very fast without any customized optimization, and be stable at the same time.
 
a year ago
User avatar None

String updated in the repository
We do not recommend using customized optimizations. They can make a program run slightly faster, but they may also cause compilation difficulties, and problems when running the program. If a package refuses to compile with a customized optimization, try to compile it without optimization and see if that fixes the problem. Even if the package does compile when using a customized optimization, there is the risk it may have been compiled incorrectly because of the complex interactions between the code and the build tools. Also note that the <option>-march</option> and <option>-mtune</option> options using values not specified in the book have not been tested. This may cause problems with the toolchain packages (Binutils, GCC and Glibc). The small potential gains achieved by customizing compiler optimizations are often outweighed by the risks. First-time builders of LFS are encouraged to build without custom optimizations.
 
a year ago
Browse all component changes