If an issue or a question is encountered while working through this book, please check the FAQ page at https://fr.linuxfromscratch.org/faq#generalfaq. Questions are often already answered there. If your question is not answered on that page, try to find the source of the problem. The following hint will give you some guidance for troubleshooting: https://fr.linuxfromscratch.org/view/astuces/errors.txt.
Si votre problème n'est pas listé dans la FAQ, recherchez dans les listes de diffusion sur https://www.linuxfromscratch.org/search.html.
We also have a wonderful LFS community that is willing to offer assistance through the mailing lists and IRC (see the Section 1.4, « Ressources » section of this book). However, we get several support questions every day, and many of them could have been easily answered by going to the FAQ or by searching the mailing lists first. So, for us to offer the best assistance possible, you should first do some research on your own. That allows us to focus on the more unusual support needs. If your searches do not produce a solution, please include all the relevant information (mentioned below) in your request for help.
Apart from a brief explanation of the problem being experienced, any request for help should include these essential things:
La version du livre que vous utilisez (dans ce cas, r11.2-166+)
La distribution hôte (et sa version) que vous utilisez pour créer LFS
La sortie du script Prérequis du système hôte
Le paquet ou la section où le problème a été rencontré
The exact error message, or a clear description of the problem
Indiquez si vous avez dévié du livre
Deviating from this book does not mean that we will not help you. After all, LFS is about personal preference. Being up-front about any changes to the established procedure helps us evaluate and determine possible causes of your problem.
Si quelque chose se passe mal lors de l'exécution du script
configure, regardez
le fichier config.log
Ce fichier
pourrait contenir les erreurs rencontrées lors de l'exécution de
configure qui n'ont
pas été affichées à l'écran. Incluez les lignes intéressantes si vous avez besoin
d'aide.
Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output from the configure script and the make 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 make screen output.
gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
-DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_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
Dans ce cas, beaucoup de personnes n’incluraient que la section du bas :
make [2]: *** [make] Error 1
This is not enough information to diagnose the problem, because it only notes that something went wrong, not what 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.
An excellent article about asking for help on the Internet is available online at 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.