Imagelibrary/rtems
1
0
Fork 1
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2025-11-16 12:34:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

2003-08-27 Ralf Corsepius <corsepiu@faw.uni-ulm.de>

Browse Source 
* buildc.t, buildrt.t, started/nt.t, sample.t, tversions.texi:
	Don't use VARIABLEs containing '-' in @set and @value (violates
	texi-syntax).
This commit is contained in:
Ralf Corsepius
2003-08-27 14:04:44 +00:00
parent 8556003657
commit 6e1f8693bf
6 changed files with 177 additions and 171 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/started/ChangeLog
View File

@@ -1,3 +1,9 @@
2003-08-27 Ralf Corsepius <corsepiu@faw.uni-ulm.de>
* buildc.t, buildrt.t, started/nt.t, sample.t, tversions.texi:
Don't use VARIABLEs containing '-' in @set and @value (violates
texi-syntax).
2003-08-22 Joel Sherrill <joel@OARcorp.com> 2003-08-22 Joel Sherrill <joel@OARcorp.com>
PR 469/doc PR 469/doc

224
doc/started/buildc.t
View File

@@ -53,61 +53,61 @@ placed in your @code{archive} directory. Included are the locations
of each component as well as any required RTEMS specific patches. of each component as well as any required RTEMS specific patches.
@need 1000 @need 1000
@subheading @value{GCC-VERSION} @subheading @value{GCCVERSION}
@example @example
FTP Site: @value{GCC-FTPSITE} FTP Site: @value{GCCFTPSITE}
Directory: @value{GCC-FTPDIR} Directory: @value{GCCFTPDIR}
File: @value{GCC-TAR} File: @value{GCCTAR}
@ifset use-html @ifset use-html
@c URL: @uref{Download @value{GCC-VERSION}, ftp://@value{GCC-FTPSITE}@value{GCC-FTPDIR}} @c URL: @uref{Download @value{GCCVERSION}, ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}}
URL: ftp://@value{GCC-FTPSITE}@value{GCC-FTPDIR} URL: ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}
@end ifset @end ifset
@end example @end example
@need 1000 @need 1000
@subheading @value{BINUTILS-VERSION} @subheading @value{BINUTILSVERSION}
@example @example
FTP Site: @value{BINUTILS-FTPSITE} FTP Site: @value{BINUTILSFTPSITE}
Directory: @value{BINUTILS-FTPDIR} Directory: @value{BINUTILSFTPDIR}
File: @value{BINUTILS-TAR} File: @value{BINUTILSTAR}
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{BINUTILS-FTPSITE}@value{BINUTILS-FTPDIR}/@value{BINUTILS-TAR},Download @value{BINUTILS-VERSION}} @c URL: @uref{ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR},Download @value{BINUTILSVERSION}}
URL: ftp://@value{BINUTILS-FTPSITE}@value{BINUTILS-FTPDIR}/@value{BINUTILS-TAR} URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}
@end ifset @end ifset
@end example @end example
@need 1000 @need 1000
@subheading @value{NEWLIB-VERSION} @subheading @value{NEWLIBVERSION}
@example @example
FTP Site: @value{NEWLIB-FTPSITE} FTP Site: @value{NEWLIBFTPSITE}
Directory: @value{NEWLIB-FTPDIR} Directory: @value{NEWLIBFTPDIR}
File: @value{NEWLIB-TAR} File: @value{NEWLIBTAR}
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{NEWLIB-FTPSITE}@value{NEWLIB-FTPDIR}/@value{NEWLIB-TAR}, Download @value{NEWLIB-VERSION}} @c URL: @uref{ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}, Download @value{NEWLIBVERSION}}
URL: ftp://@value{NEWLIB-FTPSITE}@value{NEWLIB-FTPDIR}/@value{NEWLIB-TAR} URL: ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}
@end ifset @end ifset
@end example @end example
@need 1000 @need 1000
@subheading RTEMS Specific Tool Patches and Scripts @subheading RTEMS Specific Tool Patches and Scripts
@example @example
FTP Site: @value{RTEMS-FTPSITE} FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMS-FTPDIR}/c_tools/source Directory: @value{RTEMSFTPDIR}/c_tools/source
@ifset BUILDTOOLS-TAR @ifset BUILDTOOLSTAR
File: @value{BUILDTOOLS-TAR} File: @value{BUILDTOOLSTAR}
@end ifset @end ifset
@ifset BINUTILS-RTEMSPATCH @ifset BINUTILSRTEMSPATCH
File: @value{BINUTILS-RTEMSPATCH} File: @value{BINUTILSRTEMSPATCH}
@end ifset @end ifset
@ifset NEWLIB-RTEMSPATCH @ifset NEWLIBRTEMSPATCH
File: @value{NEWLIB-RTEMSPATCH} File: @value{NEWLIBRTEMSPATCH}
@end ifset @end ifset
@ifset GCC-RTEMSPATCH @ifset GCCRTEMSPATCH
File: @value{GCC-RTEMSPATCH} File: @value{GCCRTEMSPATCH}
@end ifset @end ifset
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} @c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source,Download RTEMS Patches and Scripts}
URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source
@end ifset @end ifset
@end example @end example
@@ -141,9 +141,9 @@ the appropriate commands, the following
directories will have been created under tools. directories will have been created under tools.
@itemize @bullet @itemize @bullet
@item @value{BINUTILS-UNTAR} @item @value{BINUTILSUNTAR}
@item @value{GCC-UNTAR} @item @value{GCCUNTAR}
@item @value{NEWLIB-UNTAR} @item @value{NEWLIBUNTAR}
@end itemize @end itemize
The tree should look something like the following figure: The tree should look something like the following figure:
@@ -152,22 +152,22 @@ The tree should look something like the following figure:
@group @group
/whatever/prefix/you/choose/ /whatever/prefix/you/choose/
archive/ archive/
@value{GCC-TAR} @value{GCCTAR}
@value{BINUTILS-TAR} @value{BINUTILSTAR}
@value{NEWLIB-TAR} @value{NEWLIBTAR}
@ifset GCC-RTEMSPATCH @ifset GCCRTEMSPATCH
@value{GCC-RTEMSPATCH} @value{GCCRTEMSPATCH}
@end ifset @end ifset
@ifset BINUTILS-RTEMSPATCH @ifset BINUTILSRTEMSPATCH
@value{BINUTILS-RTEMSPATCH} @value{BINUTILSRTEMSPATCH}
@end ifset @end ifset
@ifset NEWLIB-RTEMSPATCH @ifset NEWLIBRTEMSPATCH
@value{NEWLIB-RTEMSPATCH} @value{NEWLIBRTEMSPATCH}
@end ifset @end ifset
tools/ tools/
@value{BINUTILS-UNTAR}/ @value{BINUTILSUNTAR}/
@value{GCC-UNTAR}/ @value{GCCUNTAR}/
@value{NEWLIB-UNTAR}/ @value{NEWLIBUNTAR}/
@end group @end group
@end example @end example
@@ -191,18 +191,18 @@ to GCC, NEWLIB, and BINUTILS.
@subheading Apply RTEMS Patch to GCC @subheading Apply RTEMS Patch to GCC
@ifclear GCC-RTEMSPATCH @ifclear GCCRTEMSPATCH
No RTEMS specific patches are required for @value{GCC-VERSION} to No RTEMS specific patches are required for @value{GCCVERSION} to
support @value{RTEMS-VERSION}. support @value{RTEMSVERSION}.
@end ifclear @end ifclear
@ifset GCC-RTEMSPATCH @ifset GCCRTEMSPATCH
Apply the patch using the following command sequence: Apply the patch using the following command sequence:
@example @example
cd tools/@value{GCC-UNTAR} cd tools/@value{GCCUNTAR}
cat ../../archive/@value{GCC-RTEMSPATCH} | \ cat ../../archive/@value{GCCRTEMSPATCH} | \
patch -p1 patch -p1
@end example @end example
@@ -216,7 +216,7 @@ Check to see if any of these patches have been rejected using the following
sequence: sequence:
@example @example
cd tools/@value{GCC-UNTAR} cd tools/@value{GCCUNTAR}
find . -name "*.rej" -print find . -name "*.rej" -print
@end example @end example
@@ -231,17 +231,17 @@ This should not happen with a good patch file which is properly applied.
@subheading Apply RTEMS Patch to binutils @subheading Apply RTEMS Patch to binutils
@ifclear BINUTILS-RTEMSPATCH @ifclear BINUTILSRTEMSPATCH
No RTEMS specific patches are required for @value{BINUTILS-VERSION} to No RTEMS specific patches are required for @value{BINUTILSVERSION} to
support @value{RTEMS-VERSION}. support @value{RTEMSVERSION}.
@end ifclear @end ifclear
@ifset BINUTILS-RTEMSPATCH @ifset BINUTILSRTEMSPATCH
Apply the patch using the following command sequence: Apply the patch using the following command sequence:
@example @example
cd tools/@value{BINUTILS-UNTAR} cd tools/@value{BINUTILSUNTAR}
cat ../../archive/@value{BINUTILS-RTEMSPATCH} | \ cat ../../archive/@value{BINUTILSRTEMSPATCH} | \
patch -p1 patch -p1
@end example @end example
@@ -255,7 +255,7 @@ Check to see if any of these patches have been rejected using the following
sequence: sequence:
@example @example
cd tools/@value{BINUTILS-UNTAR} cd tools/@value{BINUTILSUNTAR}
find . -name "*.rej" -print find . -name "*.rej" -print
@end example @end example
@@ -270,18 +270,18 @@ This should not happen with a good patch file which is properly applied.
@subheading Apply RTEMS Patch to newlib @subheading Apply RTEMS Patch to newlib
@ifclear NEWLIB-RTEMSPATCH @ifclear NEWLIBRTEMSPATCH
No RTEMS specific patches are required for @value{NEWLIB-VERSION} to No RTEMS specific patches are required for @value{NEWLIBVERSION} to
support @value{RTEMS-VERSION}. support @value{RTEMSVERSION}.
@end ifclear @end ifclear
@ifset NEWLIB-RTEMSPATCH @ifset NEWLIBRTEMSPATCH
Apply the patch using the following command sequence: Apply the patch using the following command sequence:
@example @example
cd tools/@value{NEWLIB-UNTAR} cd tools/@value{NEWLIBUNTAR}
cat ../../archive/@value{NEWLIB-RTEMSPATCH} | \ cat ../../archive/@value{NEWLIBRTEMSPATCH} | \
patch -p1 patch -p1
@end example @end example
@@ -295,7 +295,7 @@ Check to see if any of these patches have been rejected using the following
sequence: sequence:
@example @example
cd tools/@value{NEWLIB-UNTAR} cd tools/@value{NEWLIBUNTAR}
find . -name "*.rej" -print find . -name "*.rej" -print
@end example @end example
@@ -476,25 +476,25 @@ newlib manually using @code{configure} and @code{make} directly.
The following example illustrates the invocation of The following example illustrates the invocation of
@code{configure} and @code{make} @code{configure} and @code{make}
to build and install @value{BINUTILS-UNTAR} for the to build and install @value{BINUTILSUNTAR} for the
sparc-rtems target: sparc-rtems target:
@example @example
mkdir b-binutils mkdir b-binutils
cd b-binutils cd b-binutils
../@value{BINUTILS-UNTAR}/configure --target=sparc-rtems \ ../@value{BINUTILSUNTAR}/configure --target=sparc-rtems \
--prefix=/opt/rtems --prefix=/opt/rtems
make all make all
make info make info
make install make install
@end example @end example
After @value{BINUTILS-UNTAR} is built and installed the After @value{BINUTILSUNTAR} is built and installed the
build directory @code{b-binutils} may be removed. build directory @code{b-binutils} may be removed.
For more information on the invocation of @code{configure}, please For more information on the invocation of @code{configure}, please
refer to the documentation for @value{BINUTILS-UNTAR} or refer to the documentation for @value{BINUTILSUNTAR} or
invoke the @value{BINUTILS-UNTAR} @code{configure} command with the invoke the @value{BINUTILSUNTAR} @code{configure} command with the
@code{--help} option. @code{--help} option.
NOTE: The shell PATH variable needs to be updated to include the path NOTE: The shell PATH variable needs to be updated to include the path
@@ -518,30 +518,30 @@ sparc-rtems-ar: command not found
@subheading Configuring and Building GCC and NEWLIB @subheading Configuring and Building GCC and NEWLIB
Before building @value{GCC-UNTAR} and @value{NEWLIB-UNTAR}, Before building @value{GCCUNTAR} and @value{NEWLIBUNTAR},
@value{BINUTILS-UNTAR} must be installed and the directory @value{BINUTILSUNTAR} must be installed and the directory
containing those executables must be in your PATH. containing those executables must be in your PATH.
The C Library is built as a subordinate component of The C Library is built as a subordinate component of
@value{GCC-UNTAR}. Because of this, the @value{NEWLIB-UNTAR} @value{GCCUNTAR}. Because of this, the @value{NEWLIBUNTAR}
directory source must be available inside the @value{GCC-UNTAR} directory source must be available inside the @value{GCCUNTAR}
source tree. This is normally accomplished using a symbolic source tree. This is normally accomplished using a symbolic
link as shown in this example: link as shown in this example:
@example @example
cd @value{GCC-UNTAR} cd @value{GCCUNTAR}
ln -s ../@value{NEWLIB-UNTAR}/newlib . ln -s ../@value{NEWLIBUNTAR}/newlib .
@end example @end example
The following example illustrates the invocation of The following example illustrates the invocation of
@code{configure} and @code{make} @code{configure} and @code{make}
to build and install @value{BINUTILS-UNTAR} for the to build and install @value{BINUTILSUNTAR} for the
sparc-rtems target: sparc-rtems target:
@example @example
mkdir b-gcc mkdir b-gcc
cd b-gcc cd b-gcc
../@value{GCC-UNTAR}/configure --target=sparc-rtems \ ../@value{GCCUNTAR}/configure --target=sparc-rtems \
--with-gnu-as --with-gnu-ld --with-newlib --verbose \ --with-gnu-as --with-gnu-ld --with-newlib --verbose \
--enable-threads --prefix=/opt/rtems --enable-threads --prefix=/opt/rtems
make all make all
@@ -549,12 +549,12 @@ make info
make install make install
@end example @end example
After @value{GCC-UNTAR} is built and installed the After @value{GCCUNTAR} is built and installed the
build directory @code{b-gcc} may be removed. build directory @code{b-gcc} may be removed.
For more information on the invocation of @code{configure}, please For more information on the invocation of @code{configure}, please
refer to the documentation for @value{GCC-UNTAR} or refer to the documentation for @value{GCCUNTAR} or
invoke the @value{GCC-UNTAR} @code{configure} command with the invoke the @value{GCCUNTAR} @code{configure} command with the
@code{--help} option. @code{--help} option.
@c @c
@@ -606,31 +606,31 @@ placed in your @code{archive} directory. Included are the locations
of each component as well as any required RTEMS specific patches. of each component as well as any required RTEMS specific patches.
@need 1000 @need 1000
@subheading @value{GDB-VERSION} @subheading @value{GDBVERSION}
@example @example
FTP Site: @value{GDB-FTPSITE} FTP Site: @value{GDBFTPSITE}
Directory: @value{GDB-FTPDIR} Directory: @value{GDBFTPDIR}
File: @value{GDB-TAR} File: @value{GDBTAR}
@ifset use-html @ifset use-html
@c URL: @uref{Download @value{GDB-VERSION}, ftp://@value{GDB-FTPSITE}@value{GDB-FTPDIR}} @c URL: @uref{Download @value{GDBVERSION}, ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}}
URL: ftp://@value{GDB-FTPSITE}@value{GDB-FTPDIR} URL: ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}
@end ifset @end ifset
@end example @end example
@need 1000 @need 1000
@subheading RTEMS Specific Tool Patches and Scripts @subheading RTEMS Specific Tool Patches and Scripts
@example @example
FTP Site: @value{RTEMS-FTPSITE} FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMS-FTPDIR}/c_tools/source Directory: @value{RTEMSFTPDIR}/c_tools/source
@ifset BUILDTOOLS-TAR @ifset BUILDTOOLSTAR
File: @value{BUILDTOOLS-TAR} File: @value{BUILDTOOLSTAR}
@end ifset @end ifset
@ifset GDB-RTEMSPATCH @ifset GDBRTEMSPATCH
File: @value{GDB-RTEMSPATCH} File: @value{GDBRTEMSPATCH}
@end ifset @end ifset
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} @c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source,Download RTEMS Patches and Scripts}
URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source
@end ifset @end ifset
@end example @end example
@@ -643,10 +643,10 @@ Use the following commands to unarchive the GDB distribution:
@example @example
cd tools cd tools
tar xzf ../archive/@value{GDB-TAR} tar xzf ../archive/@value{GDBTAR}
@end example @end example
The directory @value{GDB-UNTAR} is created under the tools directory. The directory @value{GDBUNTAR} is created under the tools directory.
@c @c
@c Applying RTEMS Patch to GDB @c Applying RTEMS Patch to GDB
@@ -654,18 +654,18 @@ The directory @value{GDB-UNTAR} is created under the tools directory.
@subsection Applying RTEMS Patch to GDB @subsection Applying RTEMS Patch to GDB
@ifclear GDB-RTEMSPATCH @ifclear GDBRTEMSPATCH
No RTEMS specific patches are required for @value{GDB-VERSION} to No RTEMS specific patches are required for @value{GDBVERSION} to
support @value{RTEMS-VERSION}. support @value{RTEMSVERSION}.
@end ifclear @end ifclear
@ifset GDB-RTEMSPATCH @ifset GDBRTEMSPATCH
Apply the patch using the following command sequence: Apply the patch using the following command sequence:
@example @example
cd tools/@value{GDB-UNTAR} cd tools/@value{GDBUNTAR}
cat archive/@value{GDB-RTEMSPATCH} | \ cat archive/@value{GDBRTEMSPATCH} | \
patch -p1 patch -p1
@end example @end example
@@ -679,7 +679,7 @@ Check to see if any of these patches have been rejected using the following
sequence: sequence:
@example @example
cd tools/@value{GDB-UNTAR} cd tools/@value{GDBUNTAR}
find . -name "*.rej" -print find . -name "*.rej" -print
@end example @end example
@@ -785,13 +785,13 @@ NOTE: It may be necessary to remove the build tree in the
This section describes how to configure the GNU debugger for This section describes how to configure the GNU debugger for
RTEMS targets using @code{configure} and @code{make} directly. RTEMS targets using @code{configure} and @code{make} directly.
The following example illustrates the invocation of @code{configure} The following example illustrates the invocation of @code{configure}
and @code{make} to build and install @value{GDB-UNTAR} for the and @code{make} to build and install @value{GDBUNTAR} for the
m68k-rtems target: m68k-rtems target:
@example @example
mkdir b-gdb mkdir b-gdb
cd b-gdb cd b-gdb
../@value{GDB-UNTAR}/configure --target=m68k-rtems \ ../@value{GDBUNTAR}/configure --target=m68k-rtems \
--prefix=/opt/rtems --prefix=/opt/rtems
make all make all
make info make info
@@ -815,12 +815,12 @@ configurations for which there are extra options:
@end table @end table
After @value{GDB-UNTAR} is built and installed the After @value{GDBUNTAR} is built and installed the
build directory @code{b-gdb} may be removed. build directory @code{b-gdb} may be removed.
For more information on the invocation of @code{configure}, please For more information on the invocation of @code{configure}, please
refer to the documentation for @value{GDB-UNTAR} or refer to the documentation for @value{GDBUNTAR} or
invoke the @value{GDB-UNTAR} @code{configure} command with the invoke the @value{GDBUNTAR} @code{configure} command with the
@code{--help} option. @code{--help} option.
@c @c
@@ -886,7 +886,7 @@ in the various tool source trees. The following command
does this for the binutils source: does this for the binutils source:
@example @example
find @value{BINUTILS-UNTAR} -name config.status -print find @value{BINUTILSUNTAR} -name config.status -print
@end example @end example
The solution for this is to execute the command The solution for this is to execute the command
@@ -903,7 +903,7 @@ configuration. The include path used is something like
this: this:
@example @example
-I../../@value{BINUTILS-UNTAR}/gcc -I/@value{BINUTILS-UNTAR}/gcc/include -I. -I../../@value{BINUTILSUNTAR}/gcc -I/@value{BINUTILSUNTAR}/gcc/include -I.
@end example @end example
Note that the tool source directory is searched before the Note that the tool source directory is searched before the

34
doc/started/buildrt.t
View File

@@ -15,25 +15,25 @@ This section provides pointers to the RTEMS source code and
Hello World example program. These files should be Hello World example program. These files should be
placed in your @code{archive} directory. placed in your @code{archive} directory.
@subheading @value{RTEMS-VERSION} @subheading @value{RTEMSVERSION}
@example @example
FTP Site: @value{RTEMS-FTPSITE} FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMS-FTPDIR} Directory: @value{RTEMSFTPDIR}
File: @value{RTEMS-TAR} File: @value{RTEMSTAR}
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}, Download RTEMS components} @c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}, Download RTEMS components}
URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR} URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}
@end ifset @end ifset
@end example @end example
@subheading RTEMS Hello World @subheading RTEMS Hello World
@example @example
FTP Site: @value{RTEMS-FTPSITE} FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMS-FTPDIR} Directory: @value{RTEMSFTPDIR}
File: hello_world_c.tgz File: hello_world_c.tgz
@ifset use-html @ifset use-html
@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/hello_world_c.tgz, Download RTEMS Hello World} @c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz, Download RTEMS Hello World}
URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/hello_world_c.tgz URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz
@end ifset @end ifset
@end example @end example
@@ -48,10 +48,10 @@ tools directory:
@example @example
cd tools cd tools
tar xzf ../archive/@value{RTEMS-TAR} tar xzf ../archive/@value{RTEMSTAR}
@end example @end example
This creates the directory @value{RTEMS-UNTAR}. This creates the directory @value{RTEMSUNTAR}.
@section Add <INSTALL_POINT>/bin to Executable PATH @section Add <INSTALL_POINT>/bin to Executable PATH
@@ -134,13 +134,13 @@ This section describes how to build RTEMS.
@subsection Using the RTEMS configure Script Directly @subsection Using the RTEMS configure Script Directly
Make a build directory under tools and build the RTEMS product in this Make a build directory under tools and build the RTEMS product in this
directory. The ../@value{RTEMS-UNTAR}/configure directory. The ../@value{RTEMSUNTAR}/configure
command has numerous command line command has numerous command line
arguments. These arguments are discussed in detail in documentation that arguments. These arguments are discussed in detail in documentation that
comes with the RTEMS distribution. If you followed the procedure comes with the RTEMS distribution. If you followed the procedure
described in the section @ref{Unarchive the RTEMS Source}, these described in the section @ref{Unarchive the RTEMS Source}, these
configuration options can be found in the file configuration options can be found in the file
tools/@value{RTEMS-UNTAR}/README.configure. tools/@value{RTEMSUNTAR}/README.configure.
@b{NOTE}: The GNAT/RTEMS run-time implementation is based on the POSIX @b{NOTE}: The GNAT/RTEMS run-time implementation is based on the POSIX
API. Thus the RTEMS configuration for a GNAT/RTEMS environment MUST API. Thus the RTEMS configuration for a GNAT/RTEMS environment MUST
@@ -154,7 +154,7 @@ the @code{BOARD_SUPPORT_PACKAGE} board.
@example @example
mkdir build-rtems mkdir build-rtems
cd build-rtems cd build-rtems
../@value{RTEMS-UNTAR}/configure --target=<TARGET_CONFIGURATION> \ ../@value{RTEMSUNTAR}/configure --target=<TARGET_CONFIGURATION> \
--disable-posix --disable-tcpip --disable-cxx \ --disable-posix --disable-tcpip --disable-cxx \
--enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\ --enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
--prefix=<INSTALL_POINT> --prefix=<INSTALL_POINT>
@@ -163,14 +163,14 @@ make all install
Where the list of currently supported <TARGET_CONFIGURATION>'s and Where the list of currently supported <TARGET_CONFIGURATION>'s and
<BOARD_SUPPORT_PACKAGE>'s can be found in <BOARD_SUPPORT_PACKAGE>'s can be found in
tools/@value{RTEMS-UNTAR}/README.configure. tools/@value{RTEMSUNTAR}/README.configure.
<INSTALL_POINT> is typically the installation point for the <INSTALL_POINT> is typically the installation point for the
tools and is @code{/opt/rtems} when using prebuilt toolset executables. tools and is @code{/opt/rtems} when using prebuilt toolset executables.
BSP is a supported BSP for the selected CPU family. The list of BSP is a supported BSP for the selected CPU family. The list of
supported BSPs may be found in the file supported BSPs may be found in the file
tools/@value{RTEMS-UNTAR}/README.configure tools/@value{RTEMSUNTAR}/README.configure
in the RTEMS source tree. If the BSP parameter is not specified, in the RTEMS source tree. If the BSP parameter is not specified,
then all supported BSPs for the selected CPU family will be built. then all supported BSPs for the selected CPU family will be built.

22
doc/started/nt.t
View File

@@ -264,16 +264,16 @@ are ready to proceed to building a cross-compiler.
@enumerate @enumerate
@item Unarchive @value{BINUTILS-TAR} following the @item Unarchive @value{BINUTILSTAR} following the
instructions in @ref{Unarchiving the Tools} into the /source directory. instructions in @ref{Unarchiving the Tools} into the /source directory.
Apply the appropriate RTEMS specific patch as detailed in Apply the appropriate RTEMS specific patch as detailed in
@ref{Applying RTEMS Patches}. @ref{Applying RTEMS Patches}.
@item In the @code{/build/binutils} directory, execute the following @item In the @code{/build/binutils} directory, execute the following
command to configure @value{BINUTILS-VERSION}: command to configure @value{BINUTILSVERSION}:
@example @example
/source/@value{BINUTILS-UNTAR}/configure \ /source/@value{BINUTILSUNTAR}/configure \
--verbose --target=m68k-rtems \ --verbose --target=m68k-rtems \
--prefix=/gcc-m68k-rtems --with-gnu-as --with-gnu-ld --prefix=/gcc-m68k-rtems --with-gnu-as --with-gnu-ld
@end example @end example
@@ -321,7 +321,7 @@ the Cygwin32 environment with the new path.
@subsection Installing GCC AND NEWLIB @subsection Installing GCC AND NEWLIB
@enumerate @enumerate
@item Unarchive and patch @value{GCC-TAR} and @value{NEWLIB-TAR} @item Unarchive and patch @value{GCCTAR} and @value{NEWLIBTAR}
following the instructions in @ref{Unarchiving the Tools}. following the instructions in @ref{Unarchiving the Tools}.
Apply the appropriate RTEMS specific patches as detailed in Apply the appropriate RTEMS specific patches as detailed in
@ref{Applying RTEMS Patches}. @ref{Applying RTEMS Patches}.
@@ -332,25 +332,25 @@ Apply the appropriate RTEMS specific patches as detailed in
or Objective-C as Cygwin32 cross-compilers): or Objective-C as Cygwin32 cross-compilers):
@example @example
/source/@value{GCC-UNTAR}/libf2c /source/@value{GCCUNTAR}/libf2c
/source/@value{GCC-UNTAR}/gcc/objc /source/@value{GCCUNTAR}/gcc/objc
/source/@value{GCC-UNTAR}/gcc/f /source/@value{GCCUNTAR}/gcc/f
@end example @end example
@b{NOTE}: See @ref{Bug in Patch Utility}. @b{NOTE}: See @ref{Bug in Patch Utility}.
@item Link the following directories from Newlib to the main GCC directory, @item Link the following directories from Newlib to the main GCC directory,
/source/@value{GCC-UNTAR}/ : /source/@value{GCCUNTAR}/ :
@itemize @bullet @itemize @bullet
@item ln -s ../@value{NEWLIB-UNTAR}/newlib newlib @item ln -s ../@value{NEWLIBUNTAR}/newlib newlib
@item ln -s ../@value{NEWLIB-UNTAR}/libgloss libgloss @item ln -s ../@value{NEWLIBUNTAR}/libgloss libgloss
@end itemize @end itemize
@item Change to the /build/gcc directory to configure the compiler: @item Change to the /build/gcc directory to configure the compiler:
@example @example
/source/@value{GCC-UNTAR}/configure \ /source/@value{GCCUNTAR}/configure \
--verbose --target=m68k-rtems \ --verbose --target=m68k-rtems \
--prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \ --prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \
--with-newlib --with-newlib

2
doc/started/sample.t
View File

@@ -64,7 +64,7 @@ How this executable is downloaded to the target board is very dependent
on the BOARD_SUPPORT_PACKAGE selected. The following is a list of on the BOARD_SUPPORT_PACKAGE selected. The following is a list of
commonly used BSPs classified by their RTEMS CPU family and pointers commonly used BSPs classified by their RTEMS CPU family and pointers
to instructions on how to use them. [NOTE: All file names should be to instructions on how to use them. [NOTE: All file names should be
prepended with @value{RTEMS-UNTAR}/c/src/lib/libbsp.] prepended with @value{RTEMSUNTAR}/c/src/lib/libbsp.]
@need 1000 @need 1000
@table @b @table @b

60
doc/started/tversions.texi
View File

@@ -21,56 +21,56 @@
@c GCC Version @c GCC Version
@c @c
@set GCC-VERSION gcc 3.2.3 @set GCCVERSION gcc 3.2.3
@set GCC-TAR gcc-3.2.3.tar.bz2 @set GCCTAR gcc-3.2.3.tar.bz2
@set GCC-UNTAR gcc-3.2.3 @set GCCUNTAR gcc-3.2.3
@set GCC-FTPSITE gcc.gnu.org @set GCCFTPSITE gcc.gnu.org
@set GCC-FTPDIR /pub/gnu/gcc/ @set GCCFTPDIR /pub/gnu/gcc/
@set GCC-HTTPDIR /pub/gcc/releases/index.html @set GCCHTTPDIR /pub/gcc/releases/index.html
@set GCC-RTEMSPATCH gcc-3.2.3-rtems-20030507a.diff @set GCCRTEMSPATCH gcc-3.2.3-rtems-20030507a.diff
@c @c
@c BINUTILS Version @c BINUTILS Version
@c @c
@c The "official" binutils @c The "official" binutils
@set BINUTILS-VERSION binutils 2.13.2.1 @set BINUTILSVERSION binutils 2.13.2.1
@set BINUTILS-TAR binutils-2.13.2.1.tar.gz @set BINUTILSTAR binutils-2.13.2.1.tar.gz
@set BINUTILS-UNTAR binutils-2.13.2.1 @set BINUTILSUNTAR binutils-2.13.2.1
@set BINUTILS-FTPSITE ftp.gnu.org @set BINUTILSFTPSITE ftp.gnu.org
@set BINUTILS-FTPDIR /pub/gnu/binutils @set BINUTILSFTPDIR /pub/gnu/binutils
@c @set BINUTILS-RTEMSPATCH binutils-2.10-rtems-diff-20001107.gz @c @set BINUTILSRTEMSPATCH binutils-2.10-rtems-diff-20001107.gz
@c @c
@c NEWLIB Version @c NEWLIB Version
@c @c
@set NEWLIB-VERSION newlib 1.11.0 @set NEWLIBVERSION newlib 1.11.0
@set NEWLIB-TAR newlib-1.11.0.tar.gz @set NEWLIBTAR newlib-1.11.0.tar.gz
@set NEWLIB-UNTAR newlib-1.11.0 @set NEWLIBUNTAR newlib-1.11.0
@set NEWLIB-FTPSITE sources.redhat.com @set NEWLIBFTPSITE sources.redhat.com
@set NEWLIB-FTPDIR /pub/newlib @set NEWLIBFTPDIR /pub/newlib
@set NEWLIB-RTEMSPATCH newlib-1.11.0-rtems-20030605.diff.gz @set NEWLIBRTEMSPATCH newlib-1.11.0-rtems-20030605.diff.gz
@c @c
@c GDB Version @c GDB Version
@c @c
@set GDB-VERSION gdb 5.2 @set GDBVERSION gdb 5.2
@set GDB-TAR gdb-5.2.tar.gz @set GDBTAR gdb-5.2.tar.gz
@set GDB-UNTAR gdb-5.2 @set GDBUNTAR gdb-5.2
@set GDB-FTPSITE ftp.gnu.org @set GDBFTPSITE ftp.gnu.org
@set GDB-FTPDIR /pub/gnu/gdb @set GDBFTPDIR /pub/gnu/gdb
@set GDB-RTEMSPATCH gdb-5.2-rtems-20030211.diff.gz @set GDBRTEMSPATCH gdb-5.2-rtems-20030211.diff.gz
@c @c
@c RTEMS Version @c RTEMS Version
@c @c
@set RTEMS-VERSION RTEMS 4.6.0 @set RTEMSVERSION RTEMS 4.6.0
@set RTEMS-TAR rtems-4.6.0.tar.bz2 @set RTEMSTAR rtems-4.6.0.tar.bz2
@set RTEMS-UNTAR rtems-4.6.0 @set RTEMSUNTAR rtems-4.6.0
@set RTEMS-FTPSITE ftp.rtems.com @set RTEMSFTPSITE ftp.rtems.com
@set RTEMS-FTPDIR /pub/rtems/releases/4.6.0 @set RTEMSFTPDIR /pub/rtems/releases/4.6.0