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