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