1 | <sect1 id="prepare-askforhelp">
|
---|
2 | <title>How to ask for help</title>
|
---|
3 |
|
---|
4 | <para>If you encounter a problem while using this book, and your problem
|
---|
5 | is not listed in the FAQ (<ulink url="&faq-root;"/>), you will find that
|
---|
6 | most of the people on Internet Relay Chat (IRC) and on the mailing lists
|
---|
7 | are willing to help you. An overview of the LFS mailing lists can be
|
---|
8 | found via <xref linkend="ch-scatter-maillists"/>. To assist us in
|
---|
9 | diagnosing and solving your problem, include as much relevant
|
---|
10 | information as possible in your request for help.</para>
|
---|
11 |
|
---|
12 | <sect2>
|
---|
13 | <title>Things to mention</title>
|
---|
14 |
|
---|
15 | <para>Apart from a brief explanation of the problem you're having, the
|
---|
16 | essential things to include in your request are:</para>
|
---|
17 |
|
---|
18 | <itemizedlist>
|
---|
19 | <listitem><para>the version of the book you are using (being &version;),</para></listitem>
|
---|
20 | <listitem><para>the host distribution and version you are using to create
|
---|
21 | LFS from,</para></listitem>
|
---|
22 | <listitem><para>the package or section giving you problems,</para></listitem>
|
---|
23 | <listitem><para>the exact error message or symptom you are receiving,</para></listitem>
|
---|
24 | <listitem><para>whether you have deviated from the book at all.</para></listitem>
|
---|
25 | </itemizedlist>
|
---|
26 |
|
---|
27 | <para>(Note that saying that you've deviated from the book doesn't mean
|
---|
28 | that we won't help you. After all, LFS is about choice. It'll just
|
---|
29 | help us to see other possible causes of your problem.)</para>
|
---|
30 |
|
---|
31 | </sect2>
|
---|
32 |
|
---|
33 | <sect2>
|
---|
34 | <title>Configure problems</title>
|
---|
35 |
|
---|
36 | <para>When something goes wrong during the stage where the configure script
|
---|
37 | is run, look through the <filename>config.log</filename> file. This file
|
---|
38 | may contain errors encountered during configure which weren't printed to
|
---|
39 | the screen. Include those relevant lines if you decide to ask for
|
---|
40 | help.</para>
|
---|
41 |
|
---|
42 | </sect2>
|
---|
43 |
|
---|
44 | <sect2>
|
---|
45 | <title>Compile problems</title>
|
---|
46 |
|
---|
47 | <para>To help us find the cause of the problem, both screen output and
|
---|
48 | the contents of various files are useful. The screen output from both
|
---|
49 | the ./configure script and the make run can be useful. Don't blindly
|
---|
50 | include the whole thing but on the other hand, don't include too little.
|
---|
51 | As an example, here is some screen output from make:</para>
|
---|
52 |
|
---|
53 | <screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
|
---|
54 | -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
|
---|
55 | -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
|
---|
56 | -g -O2 -c getopt1.c
|
---|
57 | gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
|
---|
58 | function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
|
---|
59 | signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
|
---|
60 | -lutil job.o: In function `load_too_high':
|
---|
61 | /lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
|
---|
62 | collect2: ld returned 1 exit status
|
---|
63 | make[2]: *** [make] Error 1
|
---|
64 | make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
65 | make[1]: *** [all-recursive] Error 1
|
---|
66 | make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
67 | make: *** [all-recursive-am] Error 2</screen>
|
---|
68 |
|
---|
69 | <para>In this case, many people just include the bottom section where it
|
---|
70 | says:</para>
|
---|
71 |
|
---|
72 | <screen>make [2]: *** [make] Error 1</screen>
|
---|
73 |
|
---|
74 | <para>and onwards. This isn't enough for us to diagnose the problem because it
|
---|
75 | only tells us that <emphasis>something</emphasis> went wrong, not
|
---|
76 | <emphasis>what</emphasis> went wrong. The whole section, as in the example
|
---|
77 | above, is what should be included to be helpful, because it includes the
|
---|
78 | command that was executed and the command's error message(s).</para>
|
---|
79 |
|
---|
80 | <para>An excellent article on asking for help on the Internet in general
|
---|
81 | has been written by Eric S. Raymond. It is available online at <ulink
|
---|
82 | url="http://catb.org/~esr/faqs/smart-questions.html"/>.
|
---|
83 | Read and follow the hints in that document and you are much more likely
|
---|
84 | to get a response to start with and also to get the help you actually
|
---|
85 | need.</para>
|
---|
86 |
|
---|
87 | </sect2>
|
---|
88 |
|
---|
89 | <sect2>
|
---|
90 | <title>Test suite problems</title>
|
---|
91 |
|
---|
92 | <para>Many packages provide a test suite which, depending on the importance
|
---|
93 | of the package, we may encourage you to run. Sometimes packages will
|
---|
94 | generate false or expected failures. If you encounter these, you can check
|
---|
95 | the LFS Wiki page at <ulink url="&wiki-root;"/> to see whether we have
|
---|
96 | already noted and investigated them. If we already know
|
---|
97 | about them, then usually there is no need to be concerned.</para>
|
---|
98 |
|
---|
99 | </sect2>
|
---|
100 |
|
---|
101 |
|
---|
102 | </sect1>
|
---|
103 |
|
---|