Now builds for all formats.

Updated to include Steve's figures for the first time.

3 files changed, 88 insertions, 21 deletions

diff --git a/doc/started/Makefile b/doc/started/Makefile
index bbd72810c9..39b0b0d1f6 100644
--- a/doc/started/Makefile
+++ b/doc/started/Makefile
@@ -50,7 +50,7 @@ intro.texi: intro.t versions.texi
 	    -n "Requirements" ${*}.t
 
 require.texi: require.t versions.texi
-	$(BMENU) -c -p "Resources on the Internet" \
+	$(BMENU) -c -p "EGCS Mailing List" \
 	    -u "Top" \
 	    -n "Building the GNU C/C++ Cross Compiler Toolset" ${*}.t
 
@@ -81,6 +81,8 @@ nt.texi: nt.t versions.texi
 
 html: dirs $(FILES)
 	-mkdir -p $(WWW_INSTALL)/$(PROJECT)
+	-cp pictures/sfile12c.jpg $(WWW_INSTALL)/$(PROJECT)
+	-cp pictures/bit_c.jpg $(WWW_INSTALL)/$(PROJECT)
 	$(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \
  	    $(PROJECT).texi
 
diff --git a/doc/started/buildc.t b/doc/started/buildc.t
index 747e5db1af..7a4a165cc6 100644
--- a/doc/started/buildc.t
+++ b/doc/started/buildc.t
@@ -13,19 +13,14 @@ source code for a GNU cross compiler toolset, apply
 any required RTEMS specific patches, compile that 
 toolset and install it.
 
-@section Directory Organization
-
-The tree structure in the figure below is assumed to be present in the
-following discussions: 
-
-@center @b{XXX directory tree figure goes here}
-
 @section Get All the Pieces 
 
 Gather the components that will be required for the installation and place
-them in an archive directory. Call this directory arc. Be sure that there
+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. 
+approximately 20 megabytes.  In addition, make a directory named @code{tools} 
+to build the cross-compiler in. 
+
 
 @subheading @value{GCC-VERSION}
 @example
@@ -69,11 +64,53 @@ approximately 20 megabytes.
 @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.
+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
+one shown in the following figure:
+
+@ifset use-ascii
+@example
+@group
+                parent directory common to the 
+               tools and archive subdirectories
+                             |
+      +----------------------+----------------------+
+      |                                             |  
+   tools                                           arc
+@end group
+@end example
+@end ifset
+
 
-@section Unarchiving the Tools
+@ifset use-tex
+@c for now use the ascii version
+@example 
+@group
+                parent directory common to the 
+               tools and archive subdirectories
+                             |
+      +----------------------+----------------------+
+      |                                             |
+   tools                                           arc
+@end group
+@end example
+@tex
+@end tex
+@end ifset
+
+
+@ifset use-html
+@html
+<IMG SRC="sfile12c.jpg" WIDTH=417 HEIGHT=178 
+    ALT="Starting Directory Organization">
+@end html
+@end ifset
 
-Unpack the compressed tar files using the following command sequence: 
+@section Unarchiving the Sources
+
+While in the @code{tools} directory, unpack the compressed
+tar files using the following command sequence: 
 
 @example
 cd tools
@@ -91,6 +128,34 @@ directories will have been created under tools.
 @item @value{NEWLIB-UNTAR}
 @end itemize
 
+Graphically, this will look something like the following figure:
+
+@ifset use-ascii
+@example
+@group
+Not currently available in ASCII.
+@end group
+@end example
+@end ifset
+
+
+@ifset use-tex
+@c for now use the ascii version
+@example
+@group
+Not currently available in printed document.
+@end group
+@end example
+@tex
+@end tex
+@end ifset
+
+@ifset use-html
+@html
+<IMG SRC="bit_c.jpg" WIDTH=816 HEIGHT=267 ALT="Directory Organization">
+@end html
+@end ifset
+
 @c
 @c  EGCS patches
 @c
diff --git a/doc/started/nt.t b/doc/started/nt.t
index 87da96da09..8f6305df24 100644
--- a/doc/started/nt.t
+++ b/doc/started/nt.t
@@ -258,24 +258,24 @@ Apply the appropriate RTEMS specific patches as detailed in
 or Objective-C):
 
 @example
-· /build/@value{EGCS-UNTAR}/libf2c
-· /build/@value{EGCS-UNTAR}/gcc/objc
-· /build/@value{EGCS-UNTAR}/gcc/f
+· /build/@value{GCC-UNTAR}/libf2c
+· /build/@value{GCC-UNTAR}/gcc/objc
+· /build/@value{GCC-UNTAR}/gcc/f
 @end example
 
 @b{NOTE}: See @ref{Bug in Patch Utility}.
 
-@item Copy to /build/@value{EGCS-UNTAR}/ the following directories:
+@item Copy to /build/@value{GCC-UNTAR}/ the following directories:
 
 @itemize @bullet
-@item /build/newlib-1.0.8/newlib
-@item /build/newlib-1.0.8/libgloss
+@item /build/@value{NEWLIB-UNTAR}/newlib
+@item /build/@value{NEWLIB-UNTAR}/libgloss
 @end itemize
 
 @item Go under /build directory and run:
 
 @example
-../@value{EGCS-UNTAR}/configure --verbose --target=m68k-rtems \
+../@value{GCC-UNTAR}/configure --verbose --target=m68k-rtems \
     --prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \
     --with-targets=all --with-newlib
 @end example
@@ -285,7 +285,7 @@ of your choice.  See @ref{Running the bit Script} for a
 list of the targets available.
 
 @item Then run your favourite Unix format compaatible file editor,
-and edit @code{/build/@value{EGCS-UNTAR}/gcc/Makefile}
+and edit /build/@value{GCC-UNTAR}/gcc/Makefile
 Search for the section:
 
 @example