Changeset 1e6acd6 for chapter02/askforhelp.xml
- Timestamp:
- 09/22/2002 03:01:40 AM (22 years ago)
- 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, 12.2, 12.2-rc1, 6.0, 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, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- b4a5535
- Parents:
- f8decc78
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/askforhelp.xml
rf8decc78 r1e6acd6 5 5 <para>If you encounter a problem while using this book, and your problem 6 6 is not listed in the FAQ, you will find that most of the people on Internet 7 Relay Chat (IRC) and on the mailing lists are willing to help you. (An7 Relay Chat (IRC) and on the mailing lists are willing to help you. An 8 8 overview of the LFS mailing lists can be found in 9 <xref linkend="ch01-maillists"/>. )To assist us in diagnosing and solving9 <xref linkend="ch01-maillists"/>. To assist us in diagnosing and solving 10 10 your problem, include as much relevant information as possible in your 11 11 request for help.</para> … … 19 19 <itemizedlist> 20 20 <listitem><para>the version of the book you are using (being &version;),</para></listitem> 21 <listitem><para>the package or section you are having problems with,</para></listitem>21 <listitem><para>the package or section giving you problems,</para></listitem> 22 22 <listitem><para>the exact error message or symptom you are receiving,</para></listitem> 23 23 <listitem><para>whether you have deviated from the book at all.</para></listitem> … … 35 35 <para>When something goes wrong during the stage where the configure 36 36 script is run, look at the last lines of the 37 <filename>config.log</filename>. This file contains possibleerrors38 encountered during configure which aren't alwaysprinted to the screen.37 <filename>config.log</filename>. This file may contain errors 38 encountered during configure which weren't printed to the screen. 39 39 Include those relevant lines if you decide to ask for help.</para> 40 40 … … 46 46 <para>To help us find the cause of the problem, both screen output and 47 47 the contents of various files are useful. The screen output from both 48 the ./configure script and when make is run can be useful. Don't49 blindly include the whole thing but on the other hand, don't include too 50 little.As an example, here is some screen output from make:</para>48 the ./configure script and the make run can be useful. Don't blindly 49 include the whole thing but on the other hand, don't include too little. 50 As an example, here is some screen output from make:</para> 51 51 52 52 <para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" … … 70 70 isn't enough for us to diagnose the problem because it only tells us 71 71 that <emphasis>something</emphasis> went wrong, not 72 <emphasis>what</emphasis> went wrong. The whole section as73 quoted aboveis what should be included to be helpful, because it72 <emphasis>what</emphasis> went wrong. The whole section, as 73 in the example above, is what should be included to be helpful, because it 74 74 includes the command that was executed and the command's error 75 75 message(s).</para> … … 78 78 has been written by Eric S. Raymond. It is available online at <ulink 79 79 url="http://www.tuxedo.org/~esr/faqs/smart-questions.html"/>. 80 Read and follow the hints in th isdocument and you are much more likely80 Read and follow the hints in that document and you are much more likely 81 81 to get a response to start with and also to get the help you actually 82 82 need.</para>
Note:
See TracChangeset
for help on using the changeset viewer.