1
0

askforhelp.xml 5.2 KB

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