summaryrefslogtreecommitdiffstats
path: root/doc/started_ada/buildada.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-13 18:16:03 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-13 18:16:03 +0000
commit5d7eafea3646be529fb577b0d06b73255a629d6b (patch)
treed971f87318ae642e96d8ceb3c3ee27bcfbb8dd7d /doc/started_ada/buildada.t
parentAdded a warning about positioning the INSTALL_POINT under the build (diff)
downloadrtems-5d7eafea3646be529fb577b0d06b73255a629d6b.tar.bz2
Corrected name of build script and other minor things in the list of
needed tools. Corrected path to patches. Added warning about putting the install point under the build tree.
Diffstat (limited to '')
-rw-r--r--doc/started_ada/buildada.t22
1 files changed, 13 insertions, 9 deletions
diff --git a/doc/started_ada/buildada.t b/doc/started_ada/buildada.t
index f1869ed6bb..62e86229b6 100644
--- a/doc/started_ada/buildada.t
+++ b/doc/started_ada/buildada.t
@@ -175,7 +175,7 @@ The directory tree should look something like the following figure:
@example
@group
/whatever/prefix/you/choose/
- bit
+ bit_ada
archive/
@value{GCC-TAR}
@value{GNAT-TAR}
@@ -194,15 +194,15 @@ The directory tree should look something like the following figure:
@ifset GNAT-RTEMSPATCH
@value{GNAT-RTEMSPATCH}
@end ifset
- hello_world_c.tgz
- bit
+ hello_world_ada.tgz
+ bit_ada
tools/
@value{BINUTILS-UNTAR}/
@value{GCC-UNTAR}/
@value{GNAT-UNTAR}/
@value{NEWLIB-UNTAR}/
@value{RTEMS-UNTAR}/
- bit
+ bit_ada
@end group
@end example
@@ -241,7 +241,7 @@ Apply the patch using the following command sequence:
@example
cd tools/@value{GCC-UNTAR}
-zcat archive/@value{GCC-RTEMSPATCH} | patch -p1
+zcat ../../archive/@value{GCC-RTEMSPATCH} | patch -p1
@end example
Check to see if any of these patches have been rejected using the following
@@ -273,7 +273,7 @@ Apply the patch using the following command sequence:
@example
cd tools/@value{BINUTILS-UNTAR}
-zcat archive/@value{BINUTILS-RTEMSPATCH} | patch -p1
+zcat ../../archive/@value{BINUTILS-RTEMSPATCH} | patch -p1
@end example
Check to see if any of these patches have been rejected using the following
@@ -306,7 +306,7 @@ Apply the patch using the following command sequence:
@example
cd tools/@value{NEWLIB-UNTAR}
-zcat archive/@value{NEWLIB-RTEMSPATCH} | patch -p1
+zcat ../../archive/@value{NEWLIB-RTEMSPATCH} | patch -p1
@end example
Check to see if any of these patches have been rejected using the following
@@ -339,7 +339,7 @@ Apply the patch using the following command sequence:
@example
cd tools/@value{GNAT-UNTAR}
-zcat archive/@value{GNAT-RTEMSPATCH} | patch -p1
+zcat ../../archive/@value{GNAT-RTEMSPATCH} | patch -p1
@end example
Check to see if any of these patches have been rejected using the following
@@ -368,7 +368,7 @@ tools/@value{GCC-UNTAR} directory:
@example
cd tools/@value{GNAT-UNTAR}/src
-cp -r ada ../../../@value{GCC-UNTAR}
+cp -r ada ../../@value{GCC-UNTAR}
@end example
@c
@@ -424,6 +424,10 @@ RTEMS to be built. It is recommended that the directory chosen to receive
these tools be named so that it is clear from which egcs distribution it
was generated and for which target system the tools are to produce code for.
+@b{WARNING}: The @code{INSTALL_POINT} should not be a subdirectory
+under the build directory. The build directory will be removed
+automatically upon successful completion of the build procedure.
+
@item BINUTILS
is the directory under tools that contains @value{BINUTILS-UNTAR}.
For example: