RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

Suggestions from Eric Norum

Browse Source
This commit is contained in:
Joel Sherrill
1998-04-14 13:48:33 +00:00
parent f2cd6a1a8d
commit fffe92667f
3 changed files with 141 additions and 163 deletions
Download Patch File Download Diff File Expand all files Collapse all files

144
doc/started/buildc.t
View File

@@ -13,60 +13,19 @@ source code for a GNU cross compiler toolset, apply
any required RTEMS specific patches, compile that any required RTEMS specific patches, compile that
toolset and install it. 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 Start by making the @code{archive} directory to contain the downloaded
them in an archive directory. Call this directory @code{arc}. Be sure that there source code and the @code{tools} directory to be used as a build
is sufficient space to hold all necessary information. This will amount to directory. The command sequence to do this is shown
approximately 20 megabytes. In addition, make a directory named @code{tools} below:
to build the cross-compiler in.
@subheading @value{GCC-VERSION}
@example @example
FTP Site: @value{GCC-FTPSITE} mkdir arc
Directory: @value{GCC-FTPDIR} mkdir tools
File: @value{GCC-TAR}
@end example @end example
@subheading @value{BINUTILS-VERSION} This will result in an initial directory structure similar to the
@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
@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: one shown in the following figure:
@ifset use-ascii @ifset use-ascii
@@ -107,6 +66,66 @@ one shown in the following figure:
@end html @end html
@end ifset @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 @section Unarchiving the Tools
While in the @code{tools} directory, unpack the compressed 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. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c
@@ -246,15 +256,6 @@ find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c
@@ -288,15 +289,6 @@ find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c

158
doc/started_ada/buildada.t
View File

@@ -13,13 +13,64 @@ source code for a GNU cross compiler toolset, apply
any required RTEMS specific patches, compile that any required RTEMS specific patches, compile that
toolset and install it. 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 @section Get all the Pieces
Gather the components that will be required for the installation and place This section lists the components of an RTEMS cross development system.
them in an archive directory. Call this directory @code{arc}. Be sure that there Included are the locations of each component as well as any required RTEMS
is sufficient space to hold all necessary information. This will amount to specific patches.
approximately 20 megabytes. In addition, make a directory named @code{tools}
to build the cross-compiler in.
@subheading @value{GCC-VERSION} @subheading @value{GCC-VERSION}
@example @example
@@ -55,6 +106,13 @@ to build the cross-compiler in.
Directory: @value{RTEMS-FTPDIR} Directory: @value{RTEMS-FTPDIR}
File: @value{RTEMS-TAR} File: @value{RTEMS-TAR}
File: bit_ada 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 @ifset BINUTILS-RTEMSPATCH
File: @value{BINUTILS-RTEMSPATCH} File: @value{BINUTILS-RTEMSPATCH}
@end ifset @end ifset
@@ -67,53 +125,17 @@ to build the cross-compiler in.
@ifset GNAT-RTEMSPATCH @ifset GNAT-RTEMSPATCH
File: @value{GNAT-RTEMSPATCH} File: @value{GNAT-RTEMSPATCH}
@end ifset @end ifset
File: hello_world_ada.tgz @c Just in case there are ever no patches
@end example @ifset BINUTILS-RTEMSPATCH
@ifset GCC-RTEMSPATCH
@section Create the tools Directory @ifset NEWLIB-RTEMSPATCH
@ifset GNAT-RTEMSPATCH
Create a directory called tools that will serve as a working directory to No RTEMS specific patches are required.
perform the build of the cross compiler tools. Since we previously @end ifset
created a directory named @code{arc} to place the files we downloaded @end ifset
into, this will result in a starting directory structure similar the @end ifset
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 @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 @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
@section Unarchiving the Tools @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. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c
@@ -257,15 +270,6 @@ find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c
@@ -299,15 +303,6 @@ find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c
@@ -341,15 +336,6 @@ find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. If any files are found with the .rej extension, a patch has been rejected.
This should not happen with a good patch file. 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 @end ifset
@c @c

2
doc/started_ada/versions.texi
View File

@@ -56,7 +56,7 @@
@c @set BINUTILS-TAR gas-980314.tgz @c @set BINUTILS-TAR gas-980314.tgz
@c @set BINUTILS-UNTAR gas-980314 @c @set BINUTILS-UNTAR gas-980314
@c @set BINUTILS-FTPSITE ftp.OARcorp.com @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 @set BINUTILS-RTEMSPATCH binutils-2.8.1-rtems-diff-980321.gz
@c @c