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-28 Ralf Corsepius <corsepiu@faw.uni-ulm.de>

Browse Source 
* tversions.texi: Remove.
	* tversions.texi.in: New (dynamically created).
	* Makefile.am: Reflect changes above.
	* binaries.t, buildc.t, buildrt.t, intro.t, nextstep.t, nt.t:
	Various changes (actual tool versions, rtems.com, fixes).
This commit is contained in:
Ralf Corsepius
2003-08-28 13:38:49 +00:00
parent b3d0923a09
commit 23a973b405
11 changed files with 208 additions and 188 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/started/.cvsignore
View File

@@ -30,3 +30,5 @@ started.toc
started.tp
started.vr
version.texi
tversions.texi
tversions.sed

8
doc/started/ChangeLog
View File

@@ -1,3 +1,11 @@
2003-08-28 Ralf Corsepius <corsepiu@faw.uni-ulm.de>
* tversions.texi: Remove.
* tversions.texi.in: New (dynamically created).
* Makefile.am: Reflect changes above.
* binaries.t, buildc.t, buildrt.t, intro.t, nextstep.t, nt.t:
Various changes (actual tool versions, rtems.com, fixes).
2003-08-27 Ralf Corsepius <corsepiu@faw.uni-ulm.de>
* intro.t, nextstep.t: Fix mailing list addresses.

7
doc/started/Makefile.am
View File

@@ -19,7 +19,7 @@ GENERATED_FILES = binaries.texi buildc.texi buildrt.texi intro.texi \
COMMON_FILES = $(top_srcdir)/common/setup.texi \
$(top_srcdir)/common/cpright.texi
FILES = tversions.texi
FILES =
info_TEXINFOS = started.texi
started_TEXINFOS = $(FILES) $(COMMON_FILES) $(GENERATED_FILES)
@@ -81,3 +81,8 @@ PICTURES = pictures/bit_ada.jpg pictures/bit_ada.vsd pictures/bit_c.jpg pictures
pictures/sfile12c.jpg pictures/sfile12c.vsd
EXTRA_DIST += $(PICTURES)
tversions.texi: tversions.texi.in tversions.sed
sed -f tversions.sed $(srcdir)/tversions.texi.in > tversions.texi
CLEANFILES += tversions.texi
DISTCLEANFILES = tversions.sed

36
doc/started/binaries.t
View File

@@ -58,12 +58,12 @@ The following is a sample session illustrating the installation
of a C/C++ toolset targeting the SPARC architecture.
@example
rpm -i rtems-base-binutils-2.9.5.0.24-1.i386.rpm
rpm -i sparc-rtems-binutils-2.9.5.0.24-1.i386.rpm
rpm -i rtems-base-gcc-gcc2.95.2newlib1.8.2-7.i386.rpm
rpm -i sparc-rtems-gcc-gcc2.95.2newlib1.8.2-7.i386.rpm
rpm -i rtems-base-gdb-4.18-4.i386.rpm
rpm -i sparc-rtems-gdb-4.18-4.i386.rpm
rpm -i rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -i rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -i rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -i sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
@end example
Upon successful completion of the above command sequence, a
@@ -90,12 +90,12 @@ The following is a sample session illustrating the removal
of a C/C++ toolset targeting the SPARC architecture.
@example
rpm -e sparc-rtems-gdb-4.18-2.i386.rpm
rpm -e rtems-base-gdb-4.18-2.i386.rpm
rpm -e sparc-rtems-gcc-gcc2.95.2newlib1.8.2-4.i386.rpm
rpm -e rtems-base-gcc-gcc2.95.2newlib1.8.2-4.i386.rpm
rpm -e sparc-rtems-binutils-2.9.5.0.24-1.i386.rpm
rpm -e rtems-base-binutils-2.9.5.0.24-1.i386.rpm
rpm -e sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -e rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
rpm -e sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -e rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rpm -e sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -e rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
@end example
NOTE: If you have installed any RTEMS BSPs, then it is likely that
@@ -114,12 +114,12 @@ that GNU tar is installed as @code{tar}:
@example
cd /
tar xzf rtems-base-binutils-2.9.5.0.24-1.tgz
tar xzf sparc-rtems-binutils-2.9.5.0.24-1.tgz
tar xzf rtems-base-gcc-gcc2.95.2newlib1.8.2-4.tgz
tar xzf sparc-rtems-gcc-gcc2.95.2newlib1.8.2-4.tgz
tar xzf rtems-base-gdb-4.18-2.tgz
tar xzf sparc-rtems-gdb-4.18-2.tgz
tar xzf rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.tgz
tar xzf sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.tgz
tar xzf rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.tgz
tar xzf sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.tgz
tar xzf rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.tgz
tar xzf sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.tgz
@end example
Upon successful completion of the above command sequence, a

161
doc/started/buildc.t
View File

@@ -53,39 +53,39 @@ 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{GCCVERSION}
@subheading @value{GCCUNTAR}
@example
FTP Site: @value{GCCFTPSITE}
Directory: @value{GCCFTPDIR}
File: @value{GCCTAR}
@ifset use-html
@c URL: @uref{Download @value{GCCVERSION}, ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}}
URL: ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}
@end ifset
@c @ifset use-html
URL: @uref{ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}/@value{GCCTAR},,ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}/@value{GCCTAR}}
@c URL: ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}
@c @end ifset
@end example
@need 1000
@subheading @value{BINUTILSVERSION}
@subheading @value{BINUTILSUNTAR}
@example
FTP Site: @value{BINUTILSFTPSITE}
Directory: @value{BINUTILSFTPDIR}
File: @value{BINUTILSTAR}
@ifset use-html
@c URL: @uref{ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR},Download @value{BINUTILSVERSION}}
URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}
@end ifset
@c @ifset use-html
URL: @uref{ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR},,ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}}
@c URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}
@c @end ifset
@end example
@need 1000
@subheading @value{NEWLIBVERSION}
@subheading @value{NEWLIBUNTAR}
@example
FTP Site: @value{NEWLIBFTPSITE}
Directory: @value{NEWLIBFTPDIR}
File: @value{NEWLIBTAR}
@ifset use-html
@c URL: @uref{ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}, Download @value{NEWLIBVERSION}}
URL: ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}
@end ifset
@c @ifset use-html
URL: @uref{ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR},,ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}}
@c URL: ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}
@c @end ifset
@end example
@need 1000
@@ -93,16 +93,13 @@ of each component as well as any required RTEMS specific patches.
@example
FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMSFTPDIR}/c_tools/source
@ifset BUILDTOOLSTAR
File: @value{BUILDTOOLSTAR}
@end ifset
@ifset BINUTILSRTEMSPATCH
@ifset BINUTILSPATCHVERSION
File: @value{BINUTILSRTEMSPATCH}
@end ifset
@ifset NEWLIBRTEMSPATCH
@ifset NEWLIBPATCHVERSION
File: @value{NEWLIBRTEMSPATCH}
@end ifset
@ifset GCCRTEMSPATCH
@ifset GCCPATCHVERSION
File: @value{GCCRTEMSPATCH}
@end ifset
@ifset use-html
@@ -155,13 +152,13 @@ The tree should look something like the following figure:
@value{GCCTAR}
@value{BINUTILSTAR}
@value{NEWLIBTAR}
@ifset GCCRTEMSPATCH
@ifset GCCPATCHVERSION
@value{GCCRTEMSPATCH}
@end ifset
@ifset BINUTILSRTEMSPATCH
@ifset BINUTILSPATCHVERSION
@value{BINUTILSRTEMSPATCH}
@end ifset
@ifset NEWLIBRTEMSPATCH
@ifset NEWLIBPATCHVERSION
@value{NEWLIBRTEMSPATCH}
@end ifset
tools/
@@ -191,12 +188,12 @@ to GCC, NEWLIB, and BINUTILS.
@subheading Apply RTEMS Patch to GCC
@ifclear GCCRTEMSPATCH
No RTEMS specific patches are required for @value{GCCVERSION} to
@ifclear GCCPATCHVERSION
No RTEMS specific patches are required for @value{GCCUNTAR} to
support @value{RTEMSVERSION}.
@end ifclear
@ifset GCCRTEMSPATCH
@ifset GCCPATCHVERSION
Apply the patch using the following command sequence:
@@ -231,12 +228,12 @@ This should not happen with a good patch file which is properly applied.
@subheading Apply RTEMS Patch to binutils
@ifclear BINUTILSRTEMSPATCH
No RTEMS specific patches are required for @value{BINUTILSVERSION} to
@ifclear BINUTILSPATCHVERSION
No RTEMS specific patches are required for @value{BINUTILSUNTAR} to
support @value{RTEMSVERSION}.
@end ifclear
@ifset BINUTILSRTEMSPATCH
@ifset BINUTILSPATCHVERSION
Apply the patch using the following command sequence:
@example
@@ -270,12 +267,12 @@ This should not happen with a good patch file which is properly applied.
@subheading Apply RTEMS Patch to newlib
@ifclear NEWLIBRTEMSPATCH
No RTEMS specific patches are required for @value{NEWLIBVERSION} to
@ifclear NEWLIBPATCHVERSION
No RTEMS specific patches are required for @value{NEWLIBUNTAR} to
support @value{RTEMSVERSION}.
@end ifclear
@ifset NEWLIBRTEMSPATCH
@ifset NEWLIBPATCHVERSION
Apply the patch using the following command sequence:
@@ -352,14 +349,14 @@ starts by installing the source RPMs as shown in the following
example:
@example
rpm -i i386-rtems-binutils-collection-2.9.5.0.24-1.nosrc.rpm
rpm -i i386-rtems-gcc-newlib-gcc2.95.2newlib1.8.2-7.nosrc.rpm
rpm -i i386-rtems-binutils-collection-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.nosrc.rpm
rpm -i i386-rtems-gcc-newlib-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.nosrc.rpm
@end example
Because RTEMS tool RPMS are called "nosrc" to indicate that one or
The RTEMS tool source RPMS are called "nosrc" to indicate that one or
more source files required to produce the RPMs are not present.
The RTEMS source RPMs do not include the large @code{.tar.gz} or
@code{.tgz} files for
The RTEMS source RPMs typically include all required patches, but do not
include the large @code{.tar.gz} or @code{.tgz} files for
each component such as BINUTILS, GCC, or NEWLIB. These are shared
by all RTEMS RPMs regardless of target CPU and there was no reason
to duplicate them. You will have to get the required source
@@ -370,16 +367,21 @@ included or referenced by a particular RPM, use a command like the
following:
@example
$ rpm -q -l -p i386-rtems-binutils-collection-2.9.5.0.24-1.nosrc.rpm
binutils-2.9.5.0.24-rtems-20000207.diff
binutils-2.9.5.0.24.tar.gz
i386-rtems-binutils-2.9.5.0.24.spec
@c Don't use @value{GCC*} below. This is an example
$ rpm -q -l -p i386-rtems-gcc-newlib-gcc3.2.3newlib1.11.0-1.nosrc.rpm
gcc-3.2.3-rtems-20030507a.diff
i386-rtems-gcc-3.2.3-newlib-1.11.0.spec
newlib-1.11.0-rtems-20030507.diff
@end example
Notice that there is a patch file (the @code{.diff} file), a source archive
file (the @code{.tar.gz}), and a file describing the build procedure and
files produced (the @code{.spec} file). The @code{.spec} file is placed
in the @code{SPECS} directory under the RPM root directory.
Notice that there are patch files (the @code{.diff} files) and a file
describing the build procedure and files produced (the @code{.spec} file),
but no source archives (the @code{*tar.*} files).
When installing this source RPM
(@code{rpm -U i386-rtems-gcc-newlib-gcc3.2.3newlib1.11.0-1.nosrc.rpm}),
the @code{.spec} file is placed in the @code{SPECS} directory under the RPM root
directory, while the @code{*.diff} files are placed into the @code{SOURCES}
directory.
@c
@c Configuring and Building BINUTILS using RPM
@@ -393,7 +395,7 @@ RPM. This example assumes that all of the required source is installed.
@example
cd <RPM_ROOT_DIRECTORY>/SPECS
rpm -bb i386-rtems-binutils-2.9.5.0.24.spec
rpm -bb i386-rtems-binutils-@value{BINUTILSVERSION}.spec
@end example
If the build completes successfully, RPMS like the following will
@@ -401,8 +403,8 @@ be generated in a build-host architecture specific subdirectory
of the RPMS directory under the RPM root directory.
@example
rtems-base-binutils-2.9.5.0.24-1.i386.rpm
i386-rtems-binutils-2.9.5.0.24-1.i386.rpm
rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
i386-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
@end example
NOTE: It may be necessary to remove the build tree in the
@@ -422,11 +424,11 @@ the required source is installed.
@example
cd <RPM_ROOT_DIRECTORY>/RPMS/i386
rpm -i rtems-base-binutils-2.9.5.0.24-1.i386.rpm
rpm -i i386-rtems-binutils-2.9.5.0.24-1.i386.rpm
rpm -i rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
rpm -i i386-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
export PATH=/opt/rtems/bin:$PATH
cd <RPM_ROOT_DIRECTORY>/SPECS
rpm -bb i386-rtems-gcc-2.95.2-newlib-1.8.2.spec
rpm -bb i386-rtems-gcc-@value{GCCVERSION}-newlib-@value{NEWLIBVERSION}.spec
@end example
If the build completes successfully, a set of RPMS like the following will
@@ -434,15 +436,15 @@ be generated in a build-host architecture specific subdirectory
of the RPMS directory under the RPM root directory.
@example
rtems-base-gcc-gcc2.95.2newlib1.8.2-7.i386.rpm
rtems-base-chill-gcc2.95.2newlib1.8.2-7.i386.rpm
rtems-base-g77-gcc2.95.2newlib1.8.2-7.i386.rpm
rtems-base-gcj-gcc2.95.2newlib1.8.2-7.i386.rpm
i386-rtems-gcc-gcc2.95.2newlib1.8.2-7.i386.rpm
i386-rtems-chill-gcc2.95.2newlib1.8.2-7.i386.rpm
i386-rtems-g77-gcc2.95.2newlib1.8.2-7.i386.rpm
i386-rtems-gcj-gcc2.95.2newlib1.8.2-7.i386.rpm
i386-rtems-objc-gcc2.95.2newlib1.8.2-7.i386.rpm
rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rtems-base-chill-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rtems-base-g77-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
rtems-base-gcj-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
i386-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
i386-rtems-chill-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
i386-rtems-g77-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
i386-rtems-gcj-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
i386-rtems-objc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
@end example
NOTE: Some targets do not support building all languages.
@@ -606,15 +608,12 @@ 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{GDBVERSION}
@subheading @value{GDBUNTAR}
@example
FTP Site: @value{GDBFTPSITE}
Directory: @value{GDBFTPDIR}
File: @value{GDBTAR}
@ifset use-html
@c URL: @uref{Download @value{GDBVERSION}, ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}}
URL: ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}
@end ifset
URL: @uref{@value{GDBFTPURL},,@value{GDBFTPURL}}
@end example
@need 1000
@@ -622,15 +621,9 @@ of each component as well as any required RTEMS specific patches.
@example
FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMSFTPDIR}/c_tools/source
@ifset BUILDTOOLSTAR
File: @value{BUILDTOOLSTAR}
@end ifset
@ifset GDBRTEMSPATCH
@ifset GDBPATCHVERSION
File: @value{GDBRTEMSPATCH}
@end ifset
@ifset use-html
@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
URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source/@value{GDBRTEMSPATCH},,ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source/@value{GDBRTEMSPATCH}}
@end ifset
@end example
@@ -654,12 +647,12 @@ The directory @value{GDBUNTAR} is created under the tools directory.
@subsection Applying RTEMS Patch to GDB
@ifclear GDBRTEMSPATCH
@ifclear GDBPATCHVERSION
No RTEMS specific patches are required for @value{GDBVERSION} to
support @value{RTEMSVERSION}.
@end ifclear
@ifset GDBRTEMSPATCH
@ifset GDBPATCHVERSION
Apply the patch using the following command sequence:
@@ -722,7 +715,7 @@ starts by installing the source RPMs as shown in the following
example:
@example
rpm -i i386-rtems-gdb-collection-4.18-4.nosrc.rpm
rpm -i i386-rtems-gdb-collection-@value{GDBVERSION}-@value{GDBRPMRELEASE}.nosrc.rpm
@end example
Because RTEMS tool RPMS are called "nosrc" to indicate that one or
@@ -738,10 +731,10 @@ included or referenced by a particular RPM, use a command like the
following:
@example
$ rpm -q -l -p i386-rtems-gdb-collection-4.18-4.nosrc.rpm
gdb-4.18-rtems-20000524.diff
gdb-4.18.tar.gz
i386-rtems-gdb-4.18.spec
$ rpm -q -l -p i386-rtems-gdb-collection-@value{GDBVERSION}-@value{GDBRPMRELEASE}.nosrc.rpm
gdb-@value{GDBVERSION}-rtems-@value{GDBPATCHVERSION}.diff
gdb-@value{GDBVERSION}.tar.gz
i386-rtems-gdb-@value{GDBVERSION}.spec
@end example
Notice that there is a patch file (the @code{.diff} file), a source archive
@@ -761,7 +754,7 @@ RPM. This example assumes that all of the required source is installed.
@example
cd <RPM_ROOT_DIRECTORY>/SPECS
rpm -bb i386-rtems-gdb-4.18.spec
rpm -bb i386-rtems-gdb-@value{GDBVERSION}.spec
@end example
If the build completes successfully, RPMS like the following will
@@ -769,8 +762,8 @@ be generated in a build-host architecture specific subdirectory
of the RPMS directory under the RPM root directory.
@example
rtems-base-gdb-4.18-4.i386.rpm
i386-rtems-gdb-4.18-4.i386.rpm
rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
i386-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
@end example
NOTE: It may be necessary to remove the build tree in the

5
doc/started/buildrt.t
View File

@@ -31,10 +31,7 @@ placed in your @code{archive} directory.
FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMSFTPDIR}
File: hello_world_c.tgz
@ifset use-html
@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
URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz,,ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/hello_world_c.tgz}
@end example
@c

6
doc/started/intro.t
View File

@@ -157,14 +157,14 @@ the GNU manuals:
@subsection RTEMS Mailing List
@uref{mailto:rtems-users@@rtems.com,rtems-users@@rtems.com}
@uref{mailto:@value{RTEMSUSERS},@value{RTEMSUSERS}}
This mailing list is dedicated to the discussion of issues related
to RTEMS, including GNAT/RTEMS. If you have questions about RTEMS,
wish to make suggestions, or just want to pick up hints, this is a
good list to monitor. Subscribe by sending an empty mail message to
@uref{mailto:rtems-users-subscribe@@rtems.com,rtems-users-subscribe@@rtems.com}. Messages sent
to @uref{mailto:rtems-users@@rtems.com,rtems-users@@rtems.com}
@uref{mailto:@value{RTEMSUSERSSUBSCRIBE},@value{RTEMSUSERSSUBSCRIBE}}. Messages sent
to @uref{mailto:@value{RTEMSUSERS},@value{RTEMSUSERS}}
are posted to the list.
@subsection CrossGCC Mailing List

2
doc/started/nextstep.t
View File

@@ -75,7 +75,7 @@ that is not clear or missing, bring it to our attention.
Also, some of the RTEMS documentation is still under
construction. If you would like to contribute to this
effort, please contact the RTEMS Team at
@uref{mailto:rtems-users@@rtems.com, rtems-users@@rtems.com}.
@uref{mailto:@value{RTEMSUSERS}, @value{RTEMSUSERS}}.
If you are interested in sponsoring the development of a new
feature, BSP, device driver, port of an existing library, etc.,
please contact @uref{mailto:sales@@OARcorp.com, sales@@OARcorp.com}.

2
doc/started/nt.t
View File

@@ -270,7 +270,7 @@ 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{BINUTILSVERSION}:
command to configure binutils @value{BINUTILSVERSION}:
@example
/source/@value{BINUTILSUNTAR}/configure \

76
doc/started/tversions.texi
View File

@@ -1,76 +0,0 @@
@c
@c COPYRIGHT (c) 1988-2002.
@c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
@c $Id$
@c
@c
@c This file contains all toolset version dependent information
@c
@c
@c Comment out setting the "XYZ-RTEMSPATCH" variable if there is no
@c patch required. The documentation will detect this and print
@c an appropriate message in a short section.
@c
@c
@c GCC Version
@c
@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 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 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 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 RTEMSVERSION RTEMS 4.6.0
@set RTEMSTAR rtems-4.6.0.tar.bz2
@set RTEMSUNTAR rtems-4.6.0
@set RTEMSFTPSITE ftp.rtems.com
@set RTEMSFTPDIR /pub/rtems/releases/4.6.0

91
doc/started/tversions.texi.in Normal file
View File

@@ -0,0 +1,91 @@
@c
@c COPYRIGHT (c) 1988-2002.
@c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
@c $Id$
@c
@c
@c This file contains all toolset version dependent information
@c
@c
@c Comment out setting the "XYZ-RTEMSPATCH" variable if there is no
@c patch required. The documentation will detect this and print
@c an appropriate message in a short section.
@c
@c
@c GCC Version
@c
@set GCCVERSION @GCCVERSION@
@set GCCUNTAR gcc-@value{GCCVERSION}
@set GCCTAR @value{GCCUNTAR}.tar.bz2
@set GCCFTPSITE ftp.gnu.org
@set GCCFTPDIR /pub/gnu/gcc/@value{GCCUNTAR}
@set GCCHTTPDIR /pub/gcc/releases/index.html
@SETGCCPATCHVERSION@
@ifset GCCPATCHVERSION
@set GCCRTEMSPATCH @value{GCCUNTAR}-rtems-@value{GCCPATCHVERSION}.diff
@end ifset
@set GCCRPMRELEASE @GCCRPMRELEASE@
@c
@c BINUTILS Version
@c
@c The "official" binutils
@set BINUTILSVERSION @BINUTILSVERSION@
@set BINUTILSUNTAR binutils-@value{BINUTILSVERSION}
@set BINUTILSTAR @value{BINUTILSUNTAR}.tar.gz
@set BINUTILSFTPSITE ftp.gnu.org
@set BINUTILSFTPDIR /pub/gnu/binutils
@SETBINUTILSPATCHVERSION@
@ifset BINUTILSPATCHVERSION
@set BINUTILSRTEMSPATCH @value{BINUTILSUNTAR}-rtems-@value{BINUTILSPATCHVERSION}.diff
@end ifset
@set BINUTILSRPMRELEASE @BINUTILSRPMRELEASE@
@c
@c NEWLIB Version
@c
@set NEWLIBVERSION @NEWLIBVERSION@
@set NEWLIBUNTAR newlib-@value{NEWLIBVERSION}
@set NEWLIBTAR @value{NEWLIBUNTAR}.tar.gz
@set NEWLIBFTPSITE sources.redhat.com
@set NEWLIBFTPDIR /pub/newlib
@SETNEWLIBPATCHVERSION@
@ifset NEWLIBPATCHVERSION
@set NEWLIBRTEMSPATCH @value{NEWLIBUNTAR}-rtems-@value{NEWLIBPATCHVERSION}.diff
@end ifset
@c
@c GDB Version
@c
@set GDBVERSION @GDBVERSION@
@set GDBUNTAR gdb-@value{GDBVERSION}
@set GDBTAR @value{GDBUNTAR}.tar.gz
@set GDBFTPSITE ftp.gnu.org
@set GDBFTPDIR /pub/gnu/gdb
@SETGDBPATCHVERSION@
@ifset GDBPATCHVERSION
@set GDBRTEMSPATCH @value{GDBUNTAR}-rtems-@value{GDBPATCHVERSION}.diff
@end ifset
@set GDBRPMRELEASE @GDBRPMRELEASE@
@set GDBFTPURL ftp://@value{GDBFTPSITE}@value{GDBFTPDIR}/@value{GDBTAR}
@c
@c RTEMS Version
@c
@set RTEMSVERSION RTEMS 4.6.0
@set RTEMSUNTAR rtems-4.6.0
@set RTEMSTAR @value{RTEMSUNTAR}.tar.bz2
@set RTEMSFTPSITE ftp.rtems.com
@set RTEMSFTPDIR /pub/rtems/releases/4.6.0