Source strings

24 Strings 100%
Browse Translate
722 Words 100%
5,008 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
24 722 5,008
All strings Browse Translate Zen
24 722 5,008
Read-only strings Browse Translate Zen
2 85 559
Strings with any failing checks Browse Translate Zen
2 85 559
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 ea511400c9ad6f1baca13debd05f2b10ac984059 e362137d3e
Julien Lepiller authored 7 hours ago
Last commit in Weblate Automatic BLFS commit based on ea511400c9ad6f1baca13debd05f2b10ac984059 e362137d3e
Julien Lepiller authored 7 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter01/askforhelp.po
Translation file Not available
Last change June 30, 2024, 5:19 p.m.
Last author None
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 24 722 5,008
Translated 100% 24 100% 722 100% 5,008
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 24 100% 722 100% 5,008
Failing checks 8% 2 11% 85 11% 559
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 22 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 2 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

722
Hosted words
24
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
<computeroutput>gcc -D ALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-D LOCALEDIR=\"/mnt/lfs/usr/share/locale\"
-D LIBDIR=\"/mnt/lfs/usr/lib\"
-D INCLUDEDIR=\"/mnt/lfs/usr/include\" -D HAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
expand.o file.o function.o getopt.o implicit.o job.o main.o
misc.o read.o remake.o rule.o signame.o variable.o vpath.o
default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/lfs/tmp/make-3.79.1/job.c:1565: undefined reference
to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</computeroutput>
4 months ago
User avatar None

Source string added
In case you've hit an issue building one package with the LFS instruction, we strongly discourage posting the issue directly onto the upstream support channel before discussing via a LFS support channel listed in <xref linkend="ch-intro-resources" role='.'/> Doing so is often quite inefficient because the upstream maintainers are rarely familiar with LFS building procedure. Even if you've really hit an upstream issue, the LFS community can still help to isolate the information wanted by the upstream maintainers and make a proper report.
5 months ago
User avatar None

Source string added
If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.
a year ago
User avatar None

Source string added
An excellent article about asking for help on the Internet is available online at <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read this document, and follow the hints. Doing so will increase the likelihood of getting the help you need.
a year ago
User avatar None

Source string added
This is not enough information to diagnose the problem, because it only notes that something went wrong, not <emphasis>what</emphasis> went wrong. The entire section, as in the example above, is what should be saved because it includes the command that was executed and all the associated error messages.
a year ago
User avatar None

Source string added
<computeroutput>make [2]: *** [make] Error 1</computeroutput>
a year ago
User avatar None

Source string added
In this case, many people would just include the bottom section:
a year ago
User avatar None

Source string added
Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output from the <command>configure</command> script and the <command>make</command> run can be helpful. It is not necessary to include the entire output, but do include all of the relevant information. Here is an example of the type of information to include from the <command>make</command> screen output.
a year ago
User avatar None

Source string added
Compilation Problems
a year ago
User avatar None

Source string added
If something goes wrong while running the <command>configure</command> script, review the <filename>config.log</filename> file. This file may contain errors encountered during <command>configure</command> which were not printed to the screen. Include the <emphasis>relevant</emphasis> lines if you need to ask for help.
a year ago
Browse all translation changes