1 | <sect1 id="ch02-askforhelp">
|
---|
2 | <title>How to ask for help</title>
|
---|
3 |
|
---|
4 | <para>If you have a problem while using this book, you'll find that most
|
---|
5 | of the people on Internet Relay Chat (IRC) and the mailing lists will be
|
---|
6 | willing to help you. You can find a list of the LFS mailing lists in
|
---|
7 | <xref linkend="ch01-maillists"/>. To assist us in helping though, you should
|
---|
8 | make sure that you have as much relevant information as you can
|
---|
9 | available. This will assist in diagnosing and solving your problem.
|
---|
10 | This part of the book will guide you as to which sort of information
|
---|
11 | will be useful.</para>
|
---|
12 |
|
---|
13 | <sect2>
|
---|
14 | <title>Basic Information</title>
|
---|
15 |
|
---|
16 | <para>First of all we need a brief explanation of the problem.
|
---|
17 | Essential things to include are:</para>
|
---|
18 |
|
---|
19 | <itemizedlist>
|
---|
20 | <listitem><para>The version of the book you are using, which is &version;</para></listitem>
|
---|
21 | <listitem><para>Which package or section you are having problems with</para></listitem>
|
---|
22 | <listitem><para>What the exact error message or symptom you are recieving is</para></listitem>
|
---|
23 | <listitem><para>If you have deviated from the book at all</para></listitem>
|
---|
24 | </itemizedlist>
|
---|
25 |
|
---|
26 | <para>Note that saying that you've deviated from the book doesn't mean
|
---|
27 | that we won't help you, after all, LFS is all about choice. It'll just
|
---|
28 | help us to see the possible other causes of your problem.</para>
|
---|
29 |
|
---|
30 | </sect2>
|
---|
31 |
|
---|
32 | <sect2>
|
---|
33 | <title>Configure problems</title>
|
---|
34 |
|
---|
35 | <para>When something goes wrong during the stage where the configure
|
---|
36 | script is run, look at the last lines of the
|
---|
37 | <filename>config.log</filename>. This file contains possible errors
|
---|
38 | encoutered during configure which aren't always printed to the screen.
|
---|
39 | Include those relevant lines if you decide to ask for help.</para>
|
---|
40 |
|
---|
41 | </sect2>
|
---|
42 |
|
---|
43 | <sect2>
|
---|
44 | <title>Compile problems</title>
|
---|
45 |
|
---|
46 | <para>To help us find the cause of the problem, both screen output and
|
---|
47 | the contents of various files are useful. The screen output from both
|
---|
48 | the ./configure script and when make is run can be useful. Don't
|
---|
49 | blindly include the whole thing but on the other hand, don't include too
|
---|
50 | little. As an example, here is some screen output from make:</para>
|
---|
51 |
|
---|
52 | <para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
|
---|
53 | -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
|
---|
54 | -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
|
---|
55 | -g -O2 -c getopt1.c
|
---|
56 | gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
|
---|
57 | function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
|
---|
58 | signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
|
---|
59 | -lutil job.o: In function `load_too_high':
|
---|
60 | /lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
|
---|
61 | collect2: ld returned 1 exit status
|
---|
62 | make[2]: *** [make] Error 1
|
---|
63 | make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
64 | make[1]: *** [all-recursive] Error 1
|
---|
65 | make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
|
---|
66 | make: *** [all-recursive-am] Error 2</screen></para>
|
---|
67 |
|
---|
68 | <para>In this case, many people just include the bottom section where it
|
---|
69 | says <screen>make [2]: *** [make] Error 1</screen> and onwards. This
|
---|
70 | isn't enough for us to diagnose the problem because it only tells us
|
---|
71 | that <emphasis>something</emphasis> went wrong, not
|
---|
72 | <emphasis>what</emphasis> went wrong. The whole section as
|
---|
73 | quoted above is what should be included to be helpful, because it
|
---|
74 | includes the command that was executed and the command's error
|
---|
75 | message(s).</para>
|
---|
76 |
|
---|
77 | </sect2>
|
---|
78 |
|
---|
79 | </sect1>
|
---|
80 |
|
---|