From 6e8d424a281b73676504518f4925e25dc54eb4de Mon Sep 17 00:00:00 2001 From: Ralf Corsepius Date: Wed, 27 Aug 2003 16:14:26 +0000 Subject: 2003-08-27 Ralf Corsepius * buildc.t, buildrt.t, nt.t, sample.t, tversions.texi: Don't use VARIABLEs containing '-' in @set and @value (violates texi-syntax). --- doc/started/ChangeLog | 6 ++ doc/started/buildc.t | 224 ++++++++++++++++++++++----------------------- doc/started/buildrt.t | 34 +++---- doc/started/nt.t | 22 ++--- doc/started/sample.t | 2 +- doc/started/tversions.texi | 60 ++++++------ 6 files changed, 177 insertions(+), 171 deletions(-) (limited to 'doc') diff --git a/doc/started/ChangeLog b/doc/started/ChangeLog index 4e84928408..65d2738ab5 100644 --- a/doc/started/ChangeLog +++ b/doc/started/ChangeLog @@ -1,3 +1,9 @@ +2003-08-27 Ralf Corsepius + + * buildc.t, buildrt.t, nt.t, sample.t, tversions.texi: + Don't use VARIABLEs containing '-' in @set and @value (violates + texi-syntax). + 2003-08-22 Joel Sherrill PR 469/doc diff --git a/doc/started/buildc.t b/doc/started/buildc.t index c0042b0b25..f32f0eacca 100644 --- a/doc/started/buildc.t +++ b/doc/started/buildc.t @@ -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. @need 1000 -@subheading @value{GCC-VERSION} +@subheading @value{GCCVERSION} @example - FTP Site: @value{GCC-FTPSITE} - Directory: @value{GCC-FTPDIR} - File: @value{GCC-TAR} + FTP Site: @value{GCCFTPSITE} + Directory: @value{GCCFTPDIR} + File: @value{GCCTAR} @ifset use-html -@c URL: @uref{Download @value{GCC-VERSION}, ftp://@value{GCC-FTPSITE}@value{GCC-FTPDIR}} - URL: ftp://@value{GCC-FTPSITE}@value{GCC-FTPDIR} +@c URL: @uref{Download @value{GCCVERSION}, ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}} + URL: ftp://@value{GCCFTPSITE}@value{GCCFTPDIR} @end ifset @end example @need 1000 -@subheading @value{BINUTILS-VERSION} +@subheading @value{BINUTILSVERSION} @example - FTP Site: @value{BINUTILS-FTPSITE} - Directory: @value{BINUTILS-FTPDIR} - File: @value{BINUTILS-TAR} + FTP Site: @value{BINUTILSFTPSITE} + Directory: @value{BINUTILSFTPDIR} + File: @value{BINUTILSTAR} @ifset use-html -@c URL: @uref{ftp://@value{BINUTILS-FTPSITE}@value{BINUTILS-FTPDIR}/@value{BINUTILS-TAR},Download @value{BINUTILS-VERSION}} - URL: ftp://@value{BINUTILS-FTPSITE}@value{BINUTILS-FTPDIR}/@value{BINUTILS-TAR} +@c URL: @uref{ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR},Download @value{BINUTILSVERSION}} + URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR} @end ifset @end example @need 1000 -@subheading @value{NEWLIB-VERSION} +@subheading @value{NEWLIBVERSION} @example - FTP Site: @value{NEWLIB-FTPSITE} - Directory: @value{NEWLIB-FTPDIR} - File: @value{NEWLIB-TAR} + FTP Site: @value{NEWLIBFTPSITE} + Directory: @value{NEWLIBFTPDIR} + File: @value{NEWLIBTAR} @ifset use-html -@c URL: @uref{ftp://@value{NEWLIB-FTPSITE}@value{NEWLIB-FTPDIR}/@value{NEWLIB-TAR}, Download @value{NEWLIB-VERSION}} - URL: ftp://@value{NEWLIB-FTPSITE}@value{NEWLIB-FTPDIR}/@value{NEWLIB-TAR} +@c URL: @uref{ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}, Download @value{NEWLIBVERSION}} + URL: ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR} @end ifset @end example @need 1000 @subheading RTEMS Specific Tool Patches and Scripts @example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR}/c_tools/source -@ifset BUILDTOOLS-TAR - File: @value{BUILDTOOLS-TAR} + FTP Site: @value{RTEMSFTPSITE} + Directory: @value{RTEMSFTPDIR}/c_tools/source +@ifset BUILDTOOLSTAR + File: @value{BUILDTOOLSTAR} @end ifset -@ifset BINUTILS-RTEMSPATCH - File: @value{BINUTILS-RTEMSPATCH} +@ifset BINUTILSRTEMSPATCH + File: @value{BINUTILSRTEMSPATCH} @end ifset -@ifset NEWLIB-RTEMSPATCH - File: @value{NEWLIB-RTEMSPATCH} +@ifset NEWLIBRTEMSPATCH + File: @value{NEWLIBRTEMSPATCH} @end ifset -@ifset GCC-RTEMSPATCH - File: @value{GCC-RTEMSPATCH} +@ifset GCCRTEMSPATCH + File: @value{GCCRTEMSPATCH} @end ifset @ifset use-html -@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} - URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source +@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} + URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source @end ifset @end example @@ -141,9 +141,9 @@ the appropriate commands, the following directories will have been created under tools. @itemize @bullet -@item @value{BINUTILS-UNTAR} -@item @value{GCC-UNTAR} -@item @value{NEWLIB-UNTAR} +@item @value{BINUTILSUNTAR} +@item @value{GCCUNTAR} +@item @value{NEWLIBUNTAR} @end itemize The tree should look something like the following figure: @@ -152,22 +152,22 @@ The tree should look something like the following figure: @group /whatever/prefix/you/choose/ archive/ - @value{GCC-TAR} - @value{BINUTILS-TAR} - @value{NEWLIB-TAR} -@ifset GCC-RTEMSPATCH - @value{GCC-RTEMSPATCH} + @value{GCCTAR} + @value{BINUTILSTAR} + @value{NEWLIBTAR} +@ifset GCCRTEMSPATCH + @value{GCCRTEMSPATCH} @end ifset -@ifset BINUTILS-RTEMSPATCH - @value{BINUTILS-RTEMSPATCH} +@ifset BINUTILSRTEMSPATCH + @value{BINUTILSRTEMSPATCH} @end ifset -@ifset NEWLIB-RTEMSPATCH - @value{NEWLIB-RTEMSPATCH} +@ifset NEWLIBRTEMSPATCH + @value{NEWLIBRTEMSPATCH} @end ifset tools/ - @value{BINUTILS-UNTAR}/ - @value{GCC-UNTAR}/ - @value{NEWLIB-UNTAR}/ + @value{BINUTILSUNTAR}/ + @value{GCCUNTAR}/ + @value{NEWLIBUNTAR}/ @end group @end example @@ -191,18 +191,18 @@ to GCC, NEWLIB, and BINUTILS. @subheading Apply RTEMS Patch to GCC -@ifclear GCC-RTEMSPATCH -No RTEMS specific patches are required for @value{GCC-VERSION} to -support @value{RTEMS-VERSION}. +@ifclear GCCRTEMSPATCH +No RTEMS specific patches are required for @value{GCCVERSION} to +support @value{RTEMSVERSION}. @end ifclear -@ifset GCC-RTEMSPATCH +@ifset GCCRTEMSPATCH Apply the patch using the following command sequence: @example -cd tools/@value{GCC-UNTAR} -cat ../../archive/@value{GCC-RTEMSPATCH} | \ +cd tools/@value{GCCUNTAR} +cat ../../archive/@value{GCCRTEMSPATCH} | \ patch -p1 @end example @@ -216,7 +216,7 @@ Check to see if any of these patches have been rejected using the following sequence: @example -cd tools/@value{GCC-UNTAR} +cd tools/@value{GCCUNTAR} find . -name "*.rej" -print @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 -@ifclear BINUTILS-RTEMSPATCH -No RTEMS specific patches are required for @value{BINUTILS-VERSION} to -support @value{RTEMS-VERSION}. +@ifclear BINUTILSRTEMSPATCH +No RTEMS specific patches are required for @value{BINUTILSVERSION} to +support @value{RTEMSVERSION}. @end ifclear -@ifset BINUTILS-RTEMSPATCH +@ifset BINUTILSRTEMSPATCH Apply the patch using the following command sequence: @example -cd tools/@value{BINUTILS-UNTAR} -cat ../../archive/@value{BINUTILS-RTEMSPATCH} | \ +cd tools/@value{BINUTILSUNTAR} +cat ../../archive/@value{BINUTILSRTEMSPATCH} | \ patch -p1 @end example @@ -255,7 +255,7 @@ Check to see if any of these patches have been rejected using the following sequence: @example -cd tools/@value{BINUTILS-UNTAR} +cd tools/@value{BINUTILSUNTAR} find . -name "*.rej" -print @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 -@ifclear NEWLIB-RTEMSPATCH -No RTEMS specific patches are required for @value{NEWLIB-VERSION} to -support @value{RTEMS-VERSION}. +@ifclear NEWLIBRTEMSPATCH +No RTEMS specific patches are required for @value{NEWLIBVERSION} to +support @value{RTEMSVERSION}. @end ifclear -@ifset NEWLIB-RTEMSPATCH +@ifset NEWLIBRTEMSPATCH Apply the patch using the following command sequence: @example -cd tools/@value{NEWLIB-UNTAR} -cat ../../archive/@value{NEWLIB-RTEMSPATCH} | \ +cd tools/@value{NEWLIBUNTAR} +cat ../../archive/@value{NEWLIBRTEMSPATCH} | \ patch -p1 @end example @@ -295,7 +295,7 @@ Check to see if any of these patches have been rejected using the following sequence: @example -cd tools/@value{NEWLIB-UNTAR} +cd tools/@value{NEWLIBUNTAR} find . -name "*.rej" -print @end example @@ -476,25 +476,25 @@ newlib manually using @code{configure} and @code{make} directly. The following example illustrates the invocation of @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: @example mkdir b-binutils cd b-binutils -../@value{BINUTILS-UNTAR}/configure --target=sparc-rtems \ +../@value{BINUTILSUNTAR}/configure --target=sparc-rtems \ --prefix=/opt/rtems make all make info make install @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. For more information on the invocation of @code{configure}, please -refer to the documentation for @value{BINUTILS-UNTAR} or -invoke the @value{BINUTILS-UNTAR} @code{configure} command with the +refer to the documentation for @value{BINUTILSUNTAR} or +invoke the @value{BINUTILSUNTAR} @code{configure} command with the @code{--help} option. 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 -Before building @value{GCC-UNTAR} and @value{NEWLIB-UNTAR}, -@value{BINUTILS-UNTAR} must be installed and the directory +Before building @value{GCCUNTAR} and @value{NEWLIBUNTAR}, +@value{BINUTILSUNTAR} must be installed and the directory containing those executables must be in your PATH. The C Library is built as a subordinate component of -@value{GCC-UNTAR}. Because of this, the @value{NEWLIB-UNTAR} -directory source must be available inside the @value{GCC-UNTAR} +@value{GCCUNTAR}. Because of this, the @value{NEWLIBUNTAR} +directory source must be available inside the @value{GCCUNTAR} source tree. This is normally accomplished using a symbolic link as shown in this example: @example -cd @value{GCC-UNTAR} -ln -s ../@value{NEWLIB-UNTAR}/newlib . +cd @value{GCCUNTAR} +ln -s ../@value{NEWLIBUNTAR}/newlib . @end example The following example illustrates the invocation of @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: @example mkdir 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 \ --enable-threads --prefix=/opt/rtems make all @@ -549,12 +549,12 @@ make info make install @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. For more information on the invocation of @code{configure}, please -refer to the documentation for @value{GCC-UNTAR} or -invoke the @value{GCC-UNTAR} @code{configure} command with the +refer to the documentation for @value{GCCUNTAR} or +invoke the @value{GCCUNTAR} @code{configure} command with the @code{--help} option. @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. @need 1000 -@subheading @value{GDB-VERSION} +@subheading @value{GDBVERSION} @example - FTP Site: @value{GDB-FTPSITE} - Directory: @value{GDB-FTPDIR} - File: @value{GDB-TAR} + FTP Site: @value{GDBFTPSITE} + Directory: @value{GDBFTPDIR} + File: @value{GDBTAR} @ifset use-html -@c URL: @uref{Download @value{GDB-VERSION}, ftp://@value{GDB-FTPSITE}@value{GDB-FTPDIR}} - URL: ftp://@value{GDB-FTPSITE}@value{GDB-FTPDIR} +@c URL: @uref{Download @value{GDBVERSION}, ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}} + URL: ftp://@value{GDBFTPSITE}@value{GDBFTPDIR} @end ifset @end example @need 1000 @subheading RTEMS Specific Tool Patches and Scripts @example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR}/c_tools/source -@ifset BUILDTOOLS-TAR - File: @value{BUILDTOOLS-TAR} + FTP Site: @value{RTEMSFTPSITE} + Directory: @value{RTEMSFTPDIR}/c_tools/source +@ifset BUILDTOOLSTAR + File: @value{BUILDTOOLSTAR} @end ifset -@ifset GDB-RTEMSPATCH - File: @value{GDB-RTEMSPATCH} +@ifset GDBRTEMSPATCH + File: @value{GDBRTEMSPATCH} @end ifset @ifset use-html -@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} - URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools/source +@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} + URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source @end ifset @end example @@ -643,10 +643,10 @@ Use the following commands to unarchive the GDB distribution: @example cd tools -tar xzf ../archive/@value{GDB-TAR} +tar xzf ../archive/@value{GDBTAR} @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 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 -@ifclear GDB-RTEMSPATCH -No RTEMS specific patches are required for @value{GDB-VERSION} to -support @value{RTEMS-VERSION}. +@ifclear GDBRTEMSPATCH +No RTEMS specific patches are required for @value{GDBVERSION} to +support @value{RTEMSVERSION}. @end ifclear -@ifset GDB-RTEMSPATCH +@ifset GDBRTEMSPATCH Apply the patch using the following command sequence: @example -cd tools/@value{GDB-UNTAR} -cat archive/@value{GDB-RTEMSPATCH} | \ +cd tools/@value{GDBUNTAR} +cat archive/@value{GDBRTEMSPATCH} | \ patch -p1 @end example @@ -679,7 +679,7 @@ Check to see if any of these patches have been rejected using the following sequence: @example -cd tools/@value{GDB-UNTAR} +cd tools/@value{GDBUNTAR} find . -name "*.rej" -print @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 RTEMS targets using @code{configure} and @code{make} directly. 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: @example mkdir b-gdb cd b-gdb -../@value{GDB-UNTAR}/configure --target=m68k-rtems \ +../@value{GDBUNTAR}/configure --target=m68k-rtems \ --prefix=/opt/rtems make all make info @@ -815,12 +815,12 @@ configurations for which there are extra options: @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. For more information on the invocation of @code{configure}, please -refer to the documentation for @value{GDB-UNTAR} or -invoke the @value{GDB-UNTAR} @code{configure} command with the +refer to the documentation for @value{GDBUNTAR} or +invoke the @value{GDBUNTAR} @code{configure} command with the @code{--help} option. @c @@ -886,7 +886,7 @@ in the various tool source trees. The following command does this for the binutils source: @example -find @value{BINUTILS-UNTAR} -name config.status -print +find @value{BINUTILSUNTAR} -name config.status -print @end example The solution for this is to execute the command @@ -903,7 +903,7 @@ configuration. The include path used is something like this: @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 Note that the tool source directory is searched before the diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t index 2e31b12154..20f7af512d 100644 --- a/doc/started/buildrt.t +++ b/doc/started/buildrt.t @@ -15,25 +15,25 @@ This section provides pointers to the RTEMS source code and Hello World example program. These files should be placed in your @code{archive} directory. -@subheading @value{RTEMS-VERSION} +@subheading @value{RTEMSVERSION} @example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR} - File: @value{RTEMS-TAR} + FTP Site: @value{RTEMSFTPSITE} + Directory: @value{RTEMSFTPDIR} + File: @value{RTEMSTAR} @ifset use-html -@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}, Download RTEMS components} - URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR} +@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}, Download RTEMS components} + URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR} @end ifset @end example @subheading RTEMS Hello World @example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR} + FTP Site: @value{RTEMSFTPSITE} + Directory: @value{RTEMSFTPDIR} File: hello_world_c.tgz @ifset use-html -@c URL: @uref{ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/hello_world_c.tgz, Download RTEMS Hello World} - URL: ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/hello_world_c.tgz +@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz, Download RTEMS Hello World} + URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz @end ifset @end example @@ -48,10 +48,10 @@ tools directory: @example cd tools -tar xzf ../archive/@value{RTEMS-TAR} +tar xzf ../archive/@value{RTEMSTAR} @end example -This creates the directory @value{RTEMS-UNTAR}. +This creates the directory @value{RTEMSUNTAR}. @section Add /bin to Executable PATH @@ -134,13 +134,13 @@ This section describes how to build RTEMS. @subsection Using the RTEMS configure Script Directly 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 arguments. These arguments are discussed in detail in documentation that comes with the RTEMS distribution. If you followed the procedure described in the section @ref{Unarchive the RTEMS Source}, these 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 API. Thus the RTEMS configuration for a GNAT/RTEMS environment MUST @@ -154,7 +154,7 @@ the @code{BOARD_SUPPORT_PACKAGE} board. @example mkdir build-rtems cd build-rtems -../@value{RTEMS-UNTAR}/configure --target= \ +../@value{RTEMSUNTAR}/configure --target= \ --disable-posix --disable-tcpip --disable-cxx \ --enable-rtemsbsp=\ --prefix= @@ -163,14 +163,14 @@ make all install Where the list of currently supported 's and 's can be found in -tools/@value{RTEMS-UNTAR}/README.configure. +tools/@value{RTEMSUNTAR}/README.configure. is typically the installation point for the tools and is @code{/opt/rtems} when using prebuilt toolset executables. BSP is a supported BSP for the selected CPU family. The list of 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, then all supported BSPs for the selected CPU family will be built. diff --git a/doc/started/nt.t b/doc/started/nt.t index 448eb10b30..c2561df41d 100644 --- a/doc/started/nt.t +++ b/doc/started/nt.t @@ -264,16 +264,16 @@ are ready to proceed to building a cross-compiler. @enumerate -@item Unarchive @value{BINUTILS-TAR} following the +@item Unarchive @value{BINUTILSTAR} following the instructions in @ref{Unarchiving the Tools} into the /source directory. Apply the appropriate RTEMS specific patch as detailed in @ref{Applying RTEMS Patches}. @item In the @code{/build/binutils} directory, execute the following -command to configure @value{BINUTILS-VERSION}: +command to configure @value{BINUTILSVERSION}: @example -/source/@value{BINUTILS-UNTAR}/configure \ +/source/@value{BINUTILSUNTAR}/configure \ --verbose --target=m68k-rtems \ --prefix=/gcc-m68k-rtems --with-gnu-as --with-gnu-ld @end example @@ -321,7 +321,7 @@ the Cygwin32 environment with the new path. @subsection Installing GCC AND NEWLIB @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}. Apply the appropriate RTEMS specific patches as detailed in @ref{Applying RTEMS Patches}. @@ -332,25 +332,25 @@ Apply the appropriate RTEMS specific patches as detailed in or Objective-C as Cygwin32 cross-compilers): @example -/source/@value{GCC-UNTAR}/libf2c -/source/@value{GCC-UNTAR}/gcc/objc -/source/@value{GCC-UNTAR}/gcc/f +/source/@value{GCCUNTAR}/libf2c +/source/@value{GCCUNTAR}/gcc/objc +/source/@value{GCCUNTAR}/gcc/f @end example @b{NOTE}: See @ref{Bug in Patch Utility}. @item Link the following directories from Newlib to the main GCC directory, -/source/@value{GCC-UNTAR}/ : +/source/@value{GCCUNTAR}/ : @itemize @bullet -@item ln -s ../@value{NEWLIB-UNTAR}/newlib newlib -@item ln -s ../@value{NEWLIB-UNTAR}/libgloss libgloss +@item ln -s ../@value{NEWLIBUNTAR}/newlib newlib +@item ln -s ../@value{NEWLIBUNTAR}/libgloss libgloss @end itemize @item Change to the /build/gcc directory to configure the compiler: @example -/source/@value{GCC-UNTAR}/configure \ +/source/@value{GCCUNTAR}/configure \ --verbose --target=m68k-rtems \ --prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \ --with-newlib diff --git a/doc/started/sample.t b/doc/started/sample.t index fafb6024a9..b474f6483a 100644 --- a/doc/started/sample.t +++ b/doc/started/sample.t @@ -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 commonly used BSPs classified by their RTEMS CPU family and pointers 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 @table @b diff --git a/doc/started/tversions.texi b/doc/started/tversions.texi index e572a253e3..68ade84fb3 100644 --- a/doc/started/tversions.texi +++ b/doc/started/tversions.texi @@ -21,56 +21,56 @@ @c GCC Version @c -@set GCC-VERSION gcc 3.2.3 -@set GCC-TAR gcc-3.2.3.tar.bz2 -@set GCC-UNTAR gcc-3.2.3 -@set GCC-FTPSITE gcc.gnu.org -@set GCC-FTPDIR /pub/gnu/gcc/ -@set GCC-HTTPDIR /pub/gcc/releases/index.html -@set GCC-RTEMSPATCH gcc-3.2.3-rtems-20030507a.diff +@set GCCVERSION gcc 3.2.3 +@set GCCTAR gcc-3.2.3.tar.bz2 +@set GCCUNTAR gcc-3.2.3 +@set GCCFTPSITE gcc.gnu.org +@set GCCFTPDIR /pub/gnu/gcc/ +@set GCCHTTPDIR /pub/gcc/releases/index.html +@set GCCRTEMSPATCH gcc-3.2.3-rtems-20030507a.diff @c @c BINUTILS Version @c @c The "official" binutils -@set BINUTILS-VERSION binutils 2.13.2.1 -@set BINUTILS-TAR binutils-2.13.2.1.tar.gz -@set BINUTILS-UNTAR binutils-2.13.2.1 -@set BINUTILS-FTPSITE ftp.gnu.org -@set BINUTILS-FTPDIR /pub/gnu/binutils -@c @set BINUTILS-RTEMSPATCH binutils-2.10-rtems-diff-20001107.gz +@set BINUTILSVERSION binutils 2.13.2.1 +@set BINUTILSTAR binutils-2.13.2.1.tar.gz +@set BINUTILSUNTAR binutils-2.13.2.1 +@set BINUTILSFTPSITE ftp.gnu.org +@set BINUTILSFTPDIR /pub/gnu/binutils +@c @set BINUTILSRTEMSPATCH binutils-2.10-rtems-diff-20001107.gz @c @c NEWLIB Version @c -@set NEWLIB-VERSION newlib 1.11.0 -@set NEWLIB-TAR newlib-1.11.0.tar.gz -@set NEWLIB-UNTAR newlib-1.11.0 -@set NEWLIB-FTPSITE sources.redhat.com -@set NEWLIB-FTPDIR /pub/newlib -@set NEWLIB-RTEMSPATCH newlib-1.11.0-rtems-20030605.diff.gz +@set NEWLIBVERSION newlib 1.11.0 +@set NEWLIBTAR newlib-1.11.0.tar.gz +@set NEWLIBUNTAR newlib-1.11.0 +@set NEWLIBFTPSITE sources.redhat.com +@set NEWLIBFTPDIR /pub/newlib +@set NEWLIBRTEMSPATCH newlib-1.11.0-rtems-20030605.diff.gz @c @c GDB Version @c -@set GDB-VERSION gdb 5.2 -@set GDB-TAR gdb-5.2.tar.gz -@set GDB-UNTAR gdb-5.2 -@set GDB-FTPSITE ftp.gnu.org -@set GDB-FTPDIR /pub/gnu/gdb -@set GDB-RTEMSPATCH gdb-5.2-rtems-20030211.diff.gz +@set GDBVERSION gdb 5.2 +@set GDBTAR gdb-5.2.tar.gz +@set GDBUNTAR gdb-5.2 +@set GDBFTPSITE ftp.gnu.org +@set GDBFTPDIR /pub/gnu/gdb +@set GDBRTEMSPATCH gdb-5.2-rtems-20030211.diff.gz @c @c RTEMS Version @c -@set RTEMS-VERSION RTEMS SS-20030417 -@set RTEMS-TAR rtems-ss-20030417.tar.bz2 -@set RTEMS-UNTAR rtems-ss-20030417 -@set RTEMS-FTPSITE ftp.OARcorp.com -@set RTEMS-FTPDIR /pub/rtems/snapshots/rtems +@set RTEMSVERSION RTEMS SS-20030417 +@set RTEMSTAR rtems-ss-20030417.tar.bz2 +@set RTEMSUNTAR rtems-ss-20030417 +@set RTEMSFTPSITE ftp.OARcorp.com +@set RTEMSFTPDIR /pub/rtems/snapshots/rtems -- cgit v1.2.3