Ignore:
Timestamp:
01/30/2005 10:21:16 AM (19 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
d7ea6f24
Parents:
a460953
Message:

Removed obsolete commented text, chapter01. Added bootcd.xml.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4593 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter01/askforhelp.xml

    ra460953 r9c10139  
    55]>
    66<sect1 id="prepare-askforhelp">
    7 <title>How to ask for help</title>
     7<title>Help</title>
    88<?dbhtml filename="askforhelp.html"?>
    99
    1010<para>See testing</para>
    1111
    12 <!--
    13 <para>If you run into a problem while working through this book, you should
    14 first check the FAQ at <ulink url="&faq-root;"/> - often your question
    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>
    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
    33 LFS,</para></listitem>
    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 
    39 <note><para>Saying that you've deviated from the book doesn't mean
    40 that we won't help you. After all, LFS is about choice. It'll just
    41 help us to see other possible causes of your problem.</para></note>
    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
    62 include the whole thing but, on the other hand, don't include too little.
    63 As an example, here is some screen output from make:</para>
    64 
    65 <screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
    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'
    79 make: *** [all-recursive-am] Error 2</computeroutput></screen>
    80 
    81 <para>In this case, many people just include the bottom section where it
    82 says:</para>
    83 
    84 <screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
    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
    93 has been written by Eric S. Raymond. It is available online at
    94 <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>.
    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>
    112 -->
    113 
    11412</sect1>
Note: See TracChangeset for help on using the changeset viewer.