Author: manuel
Date: 2007-05-06 02:36:44 -0600 (Sun, 06 May 2007)
New Revision: 8119

Modified:
   trunk/BOOK/chapter06/gcc.xml
   trunk/BOOK/chapter06/readjusting.xml
Log:
Removed nodump attributes from chapter06 readjusting and GCC sanity checks.

Modified: trunk/BOOK/chapter06/gcc.xml
===================================================================
--- trunk/BOOK/chapter06/gcc.xml        2007-05-06 08:31:14 UTC (rev 8118)
+++ trunk/BOOK/chapter06/gcc.xml        2007-05-06 08:36:44 UTC (rev 8119)
@@ -161,7 +161,7 @@
     href="readjusting.xml"
     xpointer="xpointer(//[EMAIL PROTECTED]'g'])"/>
 
-<screen role="nodump"><userinput>grep -B2 '^ /usr/include' 
dummy.log</userinput></screen>
+<screen><userinput>grep -B2 '^ /usr/include' dummy.log</userinput></screen>
 
     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude";
     href="readjusting.xml"

Modified: trunk/BOOK/chapter06/readjusting.xml
===================================================================
--- trunk/BOOK/chapter06/readjusting.xml        2007-05-06 08:31:14 UTC (rev 
8118)
+++ trunk/BOOK/chapter06/readjusting.xml        2007-05-06 08:36:44 UTC (rev 
8119)
@@ -58,7 +58,7 @@
   functions (compiling and linking) of the adjusted toolchain are working
   as expected. To do this, perform the following sanity checks:</para>
 
-<screen role="nodump" os="a"><userinput>echo 'main(){}' &gt; dummy.c
+<screen os="a"><userinput>echo 'main(){}' &gt; dummy.c
 cc dummy.c -v -Wl,--verbose &amp;&gt; dummy.log
 readelf -l a.out | grep ': /lib'</userinput></screen>
 
@@ -73,7 +73,7 @@
 
   <para os="d">Now make sure that we're setup to use the correct 
startfiles:</para>
 
-<screen role="nodump" os="e"><userinput>grep -o '/usr/lib.*/crt[1in].* .*' 
dummy.log</userinput></screen>
+<screen os="e"><userinput>grep -o '/usr/lib.*/crt[1in].* .*' 
dummy.log</userinput></screen>
 
   <para os="f">If everything is working correctly, there should be no errors,
     and the output of the last command will be:</para>
@@ -85,7 +85,7 @@
   <para os="g">Verify that the compiler is searching for the correct header
   files:</para>
 
-<screen role="nodump"><userinput>grep -B1 '^ /usr/include' 
dummy.log</userinput></screen>
+<screen><userinput>grep -B1 '^ /usr/include' dummy.log</userinput></screen>
 
   <para os="h">This command should return successfully with the following 
output:</para>
 
@@ -94,7 +94,7 @@
 
   <para os="i">Next, verify that the new linker is being used with the correct 
search paths:</para>
 
-<screen role="nodump" os="j"><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 
's|; |\n|g'</userinput></screen>
+<screen os="j"><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; 
|\n|g'</userinput></screen>
 
   <para os="k">If everything is working correctly, there should be no errors,
   and the output of the last command will be:</para>
@@ -105,7 +105,7 @@
 
   <para os="l">Next make sure that we're using the correct libc:</para>
 
-<screen role="nodump" os="m"><userinput>grep "/lib/libc.so.6 " 
dummy.log</userinput></screen>
+<screen os="m"><userinput>grep "/lib/libc.so.6 " dummy.log</userinput></screen>
 
   <para os="n">If everything is working correctly, there should be no errors,
   and the output of the last command will be:</para>
@@ -114,7 +114,7 @@
 
   <para os="p">Lastly, make sure GCC is using the correct dynamic 
linker:</para>
 
-<screen role="nodump" os="q"><userinput>grep found 
dummy.log</userinput></screen>
+<screen os="q"><userinput>grep found dummy.log</userinput></screen>
 
   <para os="r">If everything is working correctly, there should be no errors,
   and the output of the last command will be (allowing for
@@ -130,6 +130,6 @@
 
   <para os="u">Once everything is working correctly, clean up the test 
files:</para>
 
-<screen role="nodump" os="v"><userinput>rm -v dummy.c a.out 
dummy.log</userinput></screen>
+<screen os="v"><userinput>rm -v dummy.c a.out dummy.log</userinput></screen>
 
 </sect1>

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to