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