en-US/Devel-GCC.xml

[Rüdiger Landmann]

 en-US/Devel-GCC.xml |   16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

New commits:
commit 9f1413cf3a6f4e8e365815f7c324bd335249288a
Author: Ruediger Landmann <r.landmann at redhat.com>
Date:   Fri Mar 19 00:01:18 2010 +1000

    Copyedit

diff --git a/en-US/Devel-GCC.xml b/en-US/Devel-GCC.xml
index e96a2fe..fc7ee75 100644
--- a/en-US/Devel-GCC.xml
+++ b/en-US/Devel-GCC.xml
@@ -19,19 +19,19 @@
       Key points: 
       <orderedlist numeration="arabic">
 	<listitem>
-	  <para> ld will no longer automatically search in the dependencies of
+	  <para> <command>ld</command> will no longer automatically search in the dependencies of
 	    linked objects.
 	  </para>
 	</listitem>
 	<listitem>
 	  <para>
-	    If your project used both libraries A and B, it will not compile
-	    unless A and B are both explicitly linked.
+	    If your project used both libraries <replaceable>A</replaceable> and <replaceable>B</replaceable>, it will not compile
+	    unless <replaceable>A</replaceable> and <replaceable>B</replaceable> are both explicitly linked.
 	  </para>
 	</listitem>
 	<listitem>
 	  <para>
-	    There are more explanations on the Features page on the wiki: <ulink
+	    There are more explanations on the GCC features page on the Fedora wiki: <ulink
 	    url="http://fedoraproject.org/w/index.php?title=UnderstandingDSOLinkChange"
 	    />.
 	  </para>
@@ -42,12 +42,10 @@
       Under the new changes, if your package fails its build with a message
       like:
     </para>
-    <programlisting> 
-/usr/bin/ld: gpx-parser.o: undefined reference to symbol 'acos@@GLIBC_2.0'
-/usr/bin/ld: note: 'acos@@GLIBC_2.0' is defined in DSO /lib/libm.so.6 so try adding it to the linker command line
-    </programlisting>
+<screen>/usr/bin/ld: gpx-parser.o: undefined reference to symbol 'acos@@GLIBC_2.0'
+/usr/bin/ld: note: 'acos@@GLIBC_2.0' is defined in DSO /lib/libm.so.6 so try adding it to the linker command line</screen>
     <para>
-      Then the line that builds the specified .o needs to explicitly link libm.
+      Then the line that builds the specified <literal>.o</literal> needs to explicitly link <application>libm</application>.
     </para>
   </section>