|
|
@@ -46,18 +46,18 @@ problem.</para></note>
|
|
|
<sect2>
|
|
|
<title>Configure Script Problems</title>
|
|
|
|
|
|
-<para>If something goes wrong during the stage where the
|
|
|
-<command>configure</command> script is run, 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 those relevant lines if you need to ask for help.</para>
|
|
|
+<para>If something goes wrong while running the <command>configure</command>
|
|
|
+script is run, 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 those <emphasis>relevant</emphasis> lines if you
|
|
|
+need to ask for help.</para>
|
|
|
</sect2>
|
|
|
|
|
|
<sect2>
|
|
|
<title>Compilation Problems</title>
|
|
|
|
|
|
<para>Both the screen output and the contents of various files are
|
|
|
-useful in determining the cause of compilation issues. The screen output
|
|
|
+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
|
Matthew Burgess