<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../general.ent">
  %general-entities;
]>

<sect1 id="ch-intro-askforhelp">
  <?dbhtml filename="askforhelp.html"?>

  <title>如何求助</title>

  <!--para>If an issue or a question is encountered while working through
  this book, please check the FAQ page at <ulink url="&faq-root;#generalfaq"/>.
  Questions are often already answered there. If your question is not
  answered on this page, try to find the source of the problem. The
  following hint will give you some guidance for troubleshooting:
  <ulink url="&hints-root;errors.txt"/>.</para-->
  <para>如果您在按照本书工作的过程中遇到任何问题或者疑问，请先阅读位于
	  <ulink url="&faq-root;#generalfaq"/> 的常见问题列表，一般来说可以找到答案。
	  如果您的问题没有被 FAQ 解决，试着找到问题的根源。
	  这个指南指出了一些疑难问题的排查思路：<ulink url="&hints-root;errors.txt"/>。
  </para>

  <para>如果 FAQ 中没有您的问题，访问 <ulink url="&lfs-root;search.html"/>，
  在邮件列表中搜索。</para>

  <!--para>We also have a wonderful LFS community that is willing to offer
  assistance through the mailing lists and IRC (see the <xref
  linkend="ch-intro-resources"/> section of this book). However,
  we get several support questions every day and many of them can be easily
  answered by going to the FAQ and by searching the mailing lists first.
  So, for us to offer the best assistance possible, you need to do some
  research on your own first. That allows us to focus on the more unusual
  support needs. If your searches do not produce a solution, please include
  all relevant information (mentioned below) in your request for help.</para-->
  <para>我们也有一个吸引人的 LFS 社区，社区成员愿意通过邮件列表和 IRC (见
	  <xref linkend="ch-intro-resources"/>) 提供支援。然而，
	  我们每天都会得到一大堆明明在 FAQ 或者邮件列表中能找到答案的问题。
	  因此，为了使得技术支持的效能最大化，您需要自己先对问题进行一些研究。这样，
	  我们就能够集中精力解决最特殊的支援需求。如果您的研究得不到结果，
	  请您在求助时附带下面列出的全部相关信息。</para>

  <sect2>
    <title>需要提供的信息</title>

    <!--para>Apart from a brief explanation of the problem being experienced,
    the essential things to include in any request for help are:</para-->
	<para>除了简要描述您遇到的问题外，您应该在求助邮件中附带下列必要信息。</para>

    <itemizedlist>
      <listitem>
        <para>LFS 手册的版本 (这本书的版本是
              <phrase revision="sysv">&version;</phrase>
              <phrase revision="systemd">&versiond;</phrase>)</para>
      </listitem>
      <listitem>
        <para>构建 LFS 时使用的宿主发行版名称和版本</para>
      </listitem>
      <listitem>
        <para> <xref linkend='version-check'/> 脚本的输出</para>
      </listitem>
      <listitem>
        <para>出现问题的软件包或书内章节</para>
      </listitem>
      <listitem>
        <para>程序输出的原始错误消息，或者出现的症状</para>
      </listitem>
      <listitem>
        <para>您是否进行了超出本书内容的操作 </para>
      </listitem>
    </itemizedlist>

    <note>
      <!--para>Deviating from this book does <emphasis>not</emphasis> mean that
      we will not help you. After all, LFS is about personal preference.
      Being upfront about any changes to the established procedure helps us
      evaluate and determine possible causes of your problem.</para-->
      <para>有超出本书内容的操作，
      <emphasis>并不</emphasis>意味着我们就不会协助您。
      无论如何， LFS 强调个人体验。
      在求助信中说明您对本书给出构建过程的改动，
      有助于我们猜测和确定问题的可能原因。</para>
    </note>

  </sect2>

  <sect2>
    <title>配置脚本的问题</title>

    <!--para>If something goes wrong while running the <command>configure</command>
    script, review the <filename>config.log</filename> file. This file may
    contain errors encountered during <command>configure</command> which were
    not printed to the screen. Include the <emphasis>relevant</emphasis> lines
	if you need to ask for help.</para-->
	<para>如果在运行 <command>configure</command> 脚本的过程中出现问题，
		请阅读日志文件 <filename>config.log</filename>。它可能包含
		<command>configure</command> 运行时没有输出到屏幕的具体问题。
		求助时请附带日志文件中与问题 <emphasis>相关</emphasis> 的部分。</para>

  </sect2>

  <sect2>
    <title>编译错误</title>

    <!--para>Both the screen output and the contents of various files are useful
    in determining the cause of compilation problems. The screen output from
    the <command>configure</command> script and the <command>make</command>
    run can be helpful. It is not necessary to include the entire output, but
    do include enough of the relevant information. Below is an example of the
    type of information to include from the screen output from
    <command>make</command>:</para-->
	<para>屏幕上的输出和一些文件的内容对于确认编译错误的原因都很有用。
		屏幕输出来自于 <command>configure</command> 脚本和 <command>make</command>
		命令。您不用附带所有输出内容，只要包含足够相关信息即可。例如，下面是从
		<command>make</command> 的屏幕输出中截取的一段：</para>

<screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
-DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
expand.o file.o function.o getopt.o implicit.o job.o main.o
misc.o read.o remake.o rule.o signame.o variable.o vpath.o
default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/lfs/tmp/make-3.79.1/job.c:1565: undefined reference
to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</computeroutput></screen>

    <!--para>In this case, many people would just include the bottom
    section:</para-->
	<para>对于本例来说，许多人会只附带靠下的一行：</para>

<screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>

    <!--para>This is not enough information to properly diagnose the problem
    because it only notes that something went wrong, not
    <emphasis>what</emphasis> went wrong. The entire section, as in the
    example above, is what should be saved because it includes the command
    that was executed and the associated error message(s).</para-->
	<para>这一行只告诉我们某些事情出问题了，
		而完全没有说明<emphasis>哪里</emphasis>出了问题。
		而上面的一段输出包含了出现问题的命令行和相关的错误消息，
		这是我们需要的。</para>

    <!--para>An excellent article about asking for help on the Internet is
    available online at <ulink
    url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read and
    follow the hints in this document to increase the likelihood of getting
    the help you need.</para-->
	<para>网上有一篇关于如何在网络上提问的精彩文章：
		<ulink url="http://ctab.org/~esr/faqs/smart-questions.html"/>。
		在您提问时，阅读并遵从这篇文章的建议，可以增加您得到帮助的可能性。</para>

	<note><title>译注</title>
	<para><filename>smart-questions.html</filename> 的中文翻译版见
		<ulink url="https://lug.ustc.edu.cn/wiki/doc/smart-questions"/>。
	</para></note>

  </sect2>

</sect1>
