1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <sect1 id="prepare-askforhelp">
|
---|
7 | <title>Help</title>
|
---|
8 | <?dbhtml filename="askforhelp.html"?>
|
---|
9 |
|
---|
10 | <para>If an issue or a question is encountered while working
|
---|
11 | through this book, check the FAQ page at <ulink url="&faq-root;#generalfaq"/>.
|
---|
12 | Questions are often already answered there. If your question is
|
---|
13 | not answered on this page, try to find the source of the problem. The
|
---|
14 | following hint will give you some guidance for troubleshooting: <ulink
|
---|
15 | url="&hints-root;errors.txt"/>.</para>
|
---|
16 |
|
---|
17 | <para>We also have a wonderful LFS community that is willing to offer
|
---|
18 | assistance through the mailing lists and IRC (see the <xref
|
---|
19 | linkend="ch-scatter-administrativa"/> section of this book). In order
|
---|
20 | to assist with diagnosing and solving the problem, please include
|
---|
21 | all relevant information in your request for help.</para>
|
---|
22 |
|
---|
23 | <sect2>
|
---|
24 | <title>Things to Mention</title>
|
---|
25 |
|
---|
26 | <para>Apart from a brief explanation of the problem being experienced,
|
---|
27 | the essential things to include in any request for help are:</para>
|
---|
28 |
|
---|
29 | <itemizedlist>
|
---|
30 | <listitem><para>The version of the book being used (in this case
|
---|
31 | &version;)</para></listitem>
|
---|
32 | <listitem><para>The host distribution and version being used to
|
---|
33 | create LFS</para></listitem>
|
---|
34 | <listitem><para>The package or section the problem was encountered in</para></listitem>
|
---|
35 | <listitem><para>The exact error message or symptom being received</para></listitem>
|
---|
36 | <listitem><para>Note whether you have deviated from the book at all </para></listitem>
|
---|
37 | </itemizedlist>
|
---|
38 |
|
---|
39 | <note><para>Deviating from this book does <emphasis>not</emphasis>
|
---|
40 | mean that we will not help you. After all, LFS is about personal
|
---|
41 | preference. Being upfront about any changes to the established
|
---|
42 | procedure helps us evaluate and determine possible causes of your
|
---|
43 | problem.</para></note>
|
---|
44 | </sect2>
|
---|
45 |
|
---|
46 | <sect2>
|
---|
47 | <title>Configure Script Problems</title>
|
---|
48 |
|
---|
49 | <para>If something goes wrong while running the <command>configure</command>
|
---|
50 | script, review the <filename>config.log</filename> file. This file may
|
---|
51 | contain errors encountered during <command>configure</command> which were not
|
---|
52 | printed to the screen. Include the <emphasis>relevant</emphasis> lines if you
|
---|
53 | need to ask for help.</para>
|
---|
54 | </sect2>
|
---|
55 |
|
---|
56 | <sect2>
|
---|
57 | <title>Compilation Problems</title>
|
---|
58 |
|
---|
59 | <para>Both the screen output and the contents of various files are
|
---|
60 | useful in determining the cause of compilation problems. The screen output
|
---|
61 | from the <command>configure</command> script and the
|
---|
62 | <command>make</command> run can be helpful. It
|
---|
63 | is not necessary to include the entire output, but do include enough
|
---|
64 | of the relevant information. Below is an example of the type of
|
---|
65 | information to include from the screen output from <command>make</command>:</para>
|
---|
66 |
|
---|
67 | <beginpage/>
|
---|
68 |
|
---|
69 | <screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
|
---|
70 | -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
|
---|
71 | -DLIBDIR=\"/mnt/lfs/usr/lib\"
|
---|
72 | -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
|
---|
73 | -g -O2 -c getopt1.c
|
---|
74 | gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
|
---|
75 | expand.o file.o function.o getopt.o implicit.o job.o main.o
|
---|
76 | misc.o read.o remake.o rule.o signame.o variable.o vpath.o
|
---|
77 | default.o remote-stub.o version.o opt1.o
|
---|
78 | -lutil job.o: In function `load_too_high':
|
---|
79 | /lfs/tmp/make-3.79.1/job.c:1565: undefined reference
|
---|
80 | to `getloadavg'
|
---|
81 | collect2: ld returned 1 exit status
|
---|
82 | make[2]: *** [make] Error 1
|
---|
83 | make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
84 | make[1]: *** [all-recursive] Error 1
|
---|
85 | make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
86 | make: *** [all-recursive-am] Error 2</computeroutput></screen>
|
---|
87 |
|
---|
88 | <para>In this case, many people would just include the bottom
|
---|
89 | section:</para>
|
---|
90 |
|
---|
91 | <screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
|
---|
92 |
|
---|
93 | <para>This is not enough information to properly diagnose the problem
|
---|
94 | because it only notes that something went wrong, not
|
---|
95 | <emphasis>what</emphasis> went wrong. The entire section, as in the
|
---|
96 | example above, is what should be saved because it includes the command
|
---|
97 | that was executed and the associated error message(s).</para>
|
---|
98 |
|
---|
99 | <para>An excellent article about asking for help on the Internet is
|
---|
100 | available online at <ulink
|
---|
101 | url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read and
|
---|
102 | follow the hints in this document to increase the likelihood of getting
|
---|
103 | the help you need.</para>
|
---|
104 | </sect2>
|
---|
105 |
|
---|
106 | </sect1>
|
---|
107 |
|
---|