Suggestions from Eric Norum

1 files changed, 68 insertions, 76 deletions

diff --git a/doc/started/buildc.t b/doc/started/buildc.t
index f49e37f86f..5b498a7656 100644
--- a/doc/started/buildc.t
+++ b/doc/started/buildc.t
@@ -13,60 +13,19 @@ source code for a GNU cross compiler toolset, apply
 any required RTEMS specific patches, compile that 
 toolset and install it.
 
-@section Get All the Pieces 
+@section Create the Archive and Build Directories
 
-Gather the components that will be required for the installation and place
-them in an archive directory. Call this directory @code{arc}. Be sure that there
-is sufficient space to hold all necessary information. This will amount to
-approximately 20 megabytes.  In addition, make a directory named @code{tools} 
-to build the cross-compiler in. 
+Start by making the @code{archive} directory to contain the downloaded 
+source code and the @code{tools} directory to be used as a build
+directory.  The command sequence to do this is shown
+below:
 
-
-@subheading @value{GCC-VERSION}
-@example
-    FTP Site:    @value{GCC-FTPSITE}
-    Directory:   @value{GCC-FTPDIR}
-    File:        @value{GCC-TAR}
-@end example
-
-@subheading @value{BINUTILS-VERSION}
 @example
-    FTP Site:    @value{BINUTILS-FTPSITE}
-    Directory:   @value{BINUTILS-FTPDIR}
-    File:        @value{BINUTILS-TAR}
-@end example
-
-@subheading @value{NEWLIB-VERSION}
-@example
-    FTP Site:    @value{NEWLIB-FTPSITE}
-    Directory:   @value{NEWLIB-FTPDIR}
-    File:        @value{NEWLIB-TAR}
-@end example
-
-@subheading @value{RTEMS-VERSION}
-@example
-    FTP Site:    @value{RTEMS-FTPSITE}
-    Directory:   @value{RTEMS-FTPDIR}
-    File:        @value{RTEMS-TAR}
-    File:        bit
-@ifset BINUTILS-RTEMSPATCH
-    File:        @value{BINUTILS-RTEMSPATCH}
-@end ifset
-@ifset NEWLIB-RTEMSPATCH
-    File:        @value{NEWLIB-RTEMSPATCH}
-@end ifset
-@ifset GCC-RTEMSPATCH
-    File:        @value{GCC-RTEMSPATCH}
-@end ifset
-    File:        hello_world_c.tgz
+mkdir arc
+mkdir tools
 @end example
 
-@section Create the tools Directory
-
-Create a directory called tools that will serve as a working directory to
-perform the build of the cross compiler tools.  Since we previously
-created a directory named @code{arc} to place the files we downloaded
-into, this will result in a starting directory structure similar the
+This will result in an initial directory structure similar to the
 one shown in the following figure:
 
 @ifset use-ascii
@@ -107,6 +66,66 @@ one shown in the following figure:
 @end html
 @end ifset
 
+@section Get all the Pieces 
+
+This section lists the components of an RTEMS cross development system.  
+Included are the locations of each component as well as any required RTEMS
+specific patches.
+
+@subheading @value{GCC-VERSION}
+@example
+    FTP Site:    @value{GCC-FTPSITE}
+    Directory:   @value{GCC-FTPDIR}
+    File:        @value{GCC-TAR}
+@end example
+
+@subheading @value{BINUTILS-VERSION}
+@example
+    FTP Site:    @value{BINUTILS-FTPSITE}
+    Directory:   @value{BINUTILS-FTPDIR}
+    File:        @value{BINUTILS-TAR}
+@end example
+
+@subheading @value{NEWLIB-VERSION}
+@example
+    FTP Site:    @value{NEWLIB-FTPSITE}
+    Directory:   @value{NEWLIB-FTPDIR}
+    File:        @value{NEWLIB-TAR}
+@end example
+
+@subheading @value{RTEMS-VERSION}
+@example
+    FTP Site:    @value{RTEMS-FTPSITE}
+    Directory:   @value{RTEMS-FTPDIR}
+    File:        @value{RTEMS-TAR}
+    File:        hello_world_c.tgz
+    File:        bit
+@end example
+
+@subheading RTEMS Specific Tool Patches
+@example
+    FTP Site:    @value{RTEMS-FTPSITE}
+    Directory:   @value{RTEMS-FTPDIR}/c_tools
+@ifset BINUTILS-RTEMSPATCH
+    File:        @value{BINUTILS-RTEMSPATCH}
+@end ifset
+@ifset NEWLIB-RTEMSPATCH
+    File:        @value{NEWLIB-RTEMSPATCH}
+@end ifset
+@ifset GCC-RTEMSPATCH
+    File:        @value{GCC-RTEMSPATCH}
+@end ifset
+@c Just in case there are ever no patches
+@ifset BINUTILS-RTEMSPATCH
+@ifset GCC-RTEMSPATCH
+@ifset NEWLIB-RTEMSPATCH
+    No RTEMS specific patches are required.
+@end ifset
+@end ifset
+@end ifset
+
+@end example
+
 @section Unarchiving the Tools
 
 While in the @code{tools} directory, unpack the compressed
@@ -205,15 +224,6 @@ find . -name "*.rej" -print
 If any files are found with the .rej extension, a patch has been rejected.
 This should not happen with a good patch file.
 
-To see the files that have been modified use the sequence:
-
-@example
-cd tools/@value{GCC-UNTAR}
-find . -name "*.orig" -print
-@end example
-
-The files that are found, have been modified by the patch file.
-
 @end ifset
 
 @c
@@ -246,15 +256,6 @@ find . -name "*.rej" -print
 If any files are found with the .rej extension, a patch has been rejected.
 This should not happen with a good patch file. 
 
-To see the files that have been modified use the sequence:
-
-@example
-cd tools/@value{BINUTILS-UNTAR}
-find . -name "*.orig" -print
-@end example
-
-The files that are found, have been modified by the patch file. 
-
 @end ifset
 
 @c
@@ -288,15 +289,6 @@ find . -name "*.rej" -print
 If any files are found with the .rej extension, a patch has been rejected.
 This should not happen with a good patch file. 
 
-To see the files that have been modified use the sequence:
-
-@example
-cd tools/@value{NEWLIB-UNTAR}
-find . -name "*.orig" -print
-@end example
-
-The files that are found, have been modified by the patch file. 
-
 @end ifset
 
 @c