summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-04-14 13:48:33 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-04-14 13:48:33 +0000
commitfffe92667f3263b28daa8d1ed0da3606dc5435ad (patch)
tree42b8cc84413ae6d10e676ac52242b834c69301f1 /doc
parentf2cd6a1a8d6402e8ffce00ba8c9b2de0d7c5e9d7 (diff)
downloadrtems-fffe92667f3263b28daa8d1ed0da3606dc5435ad.tar.bz2
Suggestions from Eric Norum
Diffstat (limited to '')
-rw-r--r--doc/started/buildc.t144
-rw-r--r--doc/started_ada/buildada.t156
-rw-r--r--doc/started_ada/versions.texi2
3 files changed, 140 insertions, 162 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
diff --git a/doc/started_ada/buildada.t b/doc/started_ada/buildada.t
index cf68b638d9..f1a6c65685 100644
--- a/doc/started_ada/buildada.t
+++ b/doc/started_ada/buildada.t
@@ -13,13 +13,64 @@ source code for a GNU cross compiler toolset, apply
any required RTEMS specific patches, compile that
toolset and install it.
+@section Create the Archive and Build Directories
+
+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:
+
+@example
+mkdir arc
+mkdir tools
+@end example
+
+This will result in an initial directory structure similar to 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
+
+
+@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
+
@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 @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.
+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
@@ -55,6 +106,13 @@ to build the cross-compiler in.
Directory: @value{RTEMS-FTPDIR}
File: @value{RTEMS-TAR}
File: bit_ada
+ File: hello_world_ada.tgz
+@end example
+
+@subheading RTEMS Specific Tool Patches
+@example
+ FTP Site: @value{RTEMS-FTPSITE}
+ Directory: @value{RTEMS-FTPDIR}/ada_tools
@ifset BINUTILS-RTEMSPATCH
File: @value{BINUTILS-RTEMSPATCH}
@end ifset
@@ -67,53 +125,17 @@ to build the cross-compiler in.
@ifset GNAT-RTEMSPATCH
File: @value{GNAT-RTEMSPATCH}
@end ifset
- File: hello_world_ada.tgz
-@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
-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
+@c Just in case there are ever no patches
+@ifset BINUTILS-RTEMSPATCH
+@ifset GCC-RTEMSPATCH
+@ifset NEWLIB-RTEMSPATCH
+@ifset GNAT-RTEMSPATCH
+ No RTEMS specific patches are required.
@end ifset
-
-
-@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="Base Directory Organization">
-@end html
@end ifset
+@end ifset
+@end example
@section Unarchiving the Tools
@@ -216,15 +238,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
@@ -257,15 +270,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
@@ -299,15 +303,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
@@ -341,15 +336,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{GNAT-UNTAR}
-find . -name "*.orig" -print
-@end example
-
-The files that are found, have been modified by the patch file.
-
@end ifset
@c
diff --git a/doc/started_ada/versions.texi b/doc/started_ada/versions.texi
index e64ebeb1b4..46552de968 100644
--- a/doc/started_ada/versions.texi
+++ b/doc/started_ada/versions.texi
@@ -56,7 +56,7 @@
@c @set BINUTILS-TAR gas-980314.tgz
@c @set BINUTILS-UNTAR gas-980314
@c @set BINUTILS-FTPSITE ftp.OARcorp.com
-@c @set BINUTILS-FTPDIR /OARcorp/private/beta2/c_tools
+@c @set BINUTILS-FTPDIR /oarcorp/private/beta2/ada_tools
@c @set BINUTILS-RTEMSPATCH binutils-2.8.1-rtems-diff-980321.gz
@c