<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>change log for rtems (2011-01-02)</title>
</head>
<body text='#000000' bgcolor='#ffffff'>
<a name='cs1'></a>
<table border='0' cellspacing='0' cellpadding='5' width='100%' bgcolor='#eeeeee'>
<tr><td colspan='3' bgcolor='#dddddd'>
<font color='#bb2222'><strong>joel</strong></font>
<font color='#225522'><em>(on branch rtems-4-10-branch)</em></font>
</td></tr>
<tr><td colspan='3' bgcolor='#dddddd'><pre>2011-01-02 Danila Bespalov <danila DOT bespalov AT gmail DOT com>
* started/buildc.t, started/buildrt.t, started/nt.t, started/require.t,
started/sample.t: Review and improve.
</pre></td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/ChangeLog.diff?r1=text&tr1=1.293&r2=text&tr2=1.294&diff_format=h">M</a></td><td width='1%'>1.294</td><td width='100%'>doc/ChangeLog</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/ChangeLog.diff?r1=text&tr1=1.274.2.9&r2=text&tr2=1.274.2.10&diff_format=h">M</a></td><td width='1%'>1.274.2.10</td><td width='100%'>doc/ChangeLog</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/buildc.t.diff?r1=text&tr1=1.49&r2=text&tr2=1.50&diff_format=h">M</a></td><td width='1%'>1.50</td><td width='100%'>doc/started/buildc.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/buildc.t.diff?r1=text&tr1=1.48&r2=text&tr2=1.48.2.1&diff_format=h">M</a></td><td width='1%'>1.48.2.1</td><td width='100%'>doc/started/buildc.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/buildrt.t.diff?r1=text&tr1=1.22&r2=text&tr2=1.23&diff_format=h">M</a></td><td width='1%'>1.23</td><td width='100%'>doc/started/buildrt.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/buildrt.t.diff?r1=text&tr1=1.21&r2=text&tr2=1.21.8.1&diff_format=h">M</a></td><td width='1%'>1.21.8.1</td><td width='100%'>doc/started/buildrt.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/nt.t.diff?r1=text&tr1=1.21&r2=text&tr2=1.22&diff_format=h">M</a></td><td width='1%'>1.22</td><td width='100%'>doc/started/nt.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/nt.t.diff?r1=text&tr1=1.20&r2=text&tr2=1.20.8.1&diff_format=h">M</a></td><td width='1%'>1.20.8.1</td><td width='100%'>doc/started/nt.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/require.t.diff?r1=text&tr1=1.14&r2=text&tr2=1.15&diff_format=h">M</a></td><td width='1%'>1.15</td><td width='100%'>doc/started/require.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/require.t.diff?r1=text&tr1=1.13&r2=text&tr2=1.13.8.1&diff_format=h">M</a></td><td width='1%'>1.13.8.1</td><td width='100%'>doc/started/require.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/sample.t.diff?r1=text&tr1=1.16&r2=text&tr2=1.17&diff_format=h">M</a></td><td width='1%'>1.17</td><td width='100%'>doc/started/sample.t</td></tr>
<tr><td width='1%'><a href="http://www.rtems.com/cgi-bin/viewcvs.cgi//rtems/doc/started/sample.t.diff?r1=text&tr1=1.15&r2=text&tr2=1.15.8.1&diff_format=h">M</a></td><td width='1%'>1.15.8.1</td><td width='100%'>doc/started/sample.t</td></tr>
</table>
<pre>
<font color='#006600'>diff -u rtems/doc/ChangeLog:1.293 rtems/doc/ChangeLog:1.294
--- rtems/doc/ChangeLog:1.293 Thu Dec 16 14:42:52 2010
+++ rtems/doc/ChangeLog Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -1,3 +1,8 @@
</font><font color='#000088'>+2011-01-02 Danila Bespalov <danila DOT bespalov AT gmail DOT com>
+
+ * started/buildc.t, started/buildrt.t, started/nt.t, started/require.t,
+ started/sample.t: Review and improve.
+
</font> 2010-12-16 Joel Sherrill <joel.sherrilL@OARcorp.com>
* develenv/direct.t: Remove Getting Started with GNAT/RTEMS.
<font color='#006600'>diff -u rtems/doc/ChangeLog:1.274.2.9 rtems/doc/ChangeLog:1.274.2.10
--- rtems/doc/ChangeLog:1.274.2.9 Wed Nov 24 12:01:48 2010
+++ rtems/doc/ChangeLog Sun Jan 2 10:12:04 2011
</font><font color='#997700'>@@ -1,3 +1,8 @@
</font><font color='#000088'>+2011-01-02 Danila Bespalov <danila DOT bespalov AT gmail DOT com>
+
+ * started/buildc.t, started/buildrt.t, started/nt.t, started/require.t,
+ started/sample.t: Review and improve.
+
</font> 2010-11-24 Joel Sherrill <joel.sherrilL@OARcorp.com>
PR 1674/doc
<font color='#006600'>diff -u rtems/doc/started/buildc.t:1.49 rtems/doc/started/buildc.t:1.50
--- rtems/doc/started/buildc.t:1.49 Tue Dec 14 10:51:17 2010
+++ rtems/doc/started/buildc.t Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -8,12 +8,13 @@
</font>
@chapter Building the GNU Cross Compiler Toolset
<font color='#880000'>-NOTE: This chapter does @b{NOT} apply if you installed prebuilt toolset
-executables for BINUTILS, GCC, NEWLIB, and GDB. If you installed
-prebuilt executables for all of those, proceed to @ref{Building RTEMS}.
-If you require a GDB with a special configuration to connect to your
-target board, then proceed to @ref{Installing GDB Without RPM}
-for some advice.
</font><font color='#000088'>+@b{NOTE}: This chapter describes the steps required to build cross-compilation
+toolset on Linux (and possibly Windows using Cygwin) systems. This chapter
+does @b{NOT} apply if you installed prebuilt toolset executables for BINUTILS,
+GCC, NEWLIB, and GDB. If you installed prebuilt executables for all of those,
+proceed to @ref{Building RTEMS}. If you require a GDB with a special
+configuration to connect to your target board, then proceed to
+@ref{Installing GDB Without RPM} for some advice.
</font>
This chapter describes the steps required to acquire the source code for
a GNU cross compiler toolset, apply any required RTEMS specific patches,
<font color='#997700'>@@ -52,9 +53,14 @@
</font> All patches and RPM specification files are kept in CVS. They are
not included in release tarballs. You will have to access the
CVS branch for RTEMS @value{RTEMSAPI}. For details on this,
<font color='#880000'>-visit @uref{http://www.rtems.org, http://www.rtems.org} and look for
-instructions on accessing the RTEMS Source Code Repository in read-only
-mode.
</font><font color='#000088'>+visit @uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository} and look for
+instructions on accessing the RTEMS Source Code Repository in read-only mode.
+You can either do a complete checkout of the source tree or use a web
+interface. A typical checkout command would look like this:
+@c TODO: pointing the user to the wiki entry might be enough.
+@example
+cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P rtems
+@end example
</font>
In the checked out source code, you will need to look in the subdirectory
@code{contrib/crossrpms/autotools} to determine the versions of AUTOCONF
<font color='#997700'>@@ -62,9 +68,10 @@
</font> a few files you will need to look at. The first is @code{Makefile.am}
which defines the versions of AUTOCONF and AUTOMAKE required for this
RTEMS Release Series. Make a note of the version numbers required for
<font color='#880000'>-AUTOCONF and AUTOMAKE. Then examine the following files to determine
-the master location for the source tarballs and to determine if a patch
-is required for each tool version cited in the @code{Makefile.am}.
</font><font color='#000088'>+AUTOCONF and AUTOMAKE (AUTOCONF_VERS and AUTOMAKE_VERS respectively). Then
+examine the following files to determine the master location for the source
+tarballs and to determine if a patch is required for each tool version cited in
+the @code{Makefile.am}.
</font>
@example
autoconf-sources.add
<font color='#997700'>@@ -75,6 +82,10 @@
</font> @code{contrib/crossrpms/patches} subdirectory of your checked out RTEMS
source tree.
<font color='#000088'>+If no patches are required, you can use a package manager provided by your
+Linux distribution to install AUTOMAKE and AUTOCONF to avoid building them from
+source.
+
</font> In the checked out source code, you will need to look in the subdirectory
@code{contrib/crossrpms/rtems@value{RTEMSAPI}} to determine the target
specific tool versions and patches required. In this directory, you
<font color='#997700'>@@ -101,12 +112,6 @@
</font> toolset targeting the selected architecture. In many cases, this will be
the same versions required by other targets on this RTEMS Release Series.
<font color='#880000'>-Depending on the build method chosen, you may have to download source
-and patches or only patches. Also the destination directory for the
-downloaded source is dependent on the build method followed. But the
-versions required are the same. Specific information on what to download
-and where to place it is in subsequent sections.
-
</font> @c
@c Obtain Source and Patches
@c
<font color='#997700'>@@ -171,13 +176,13 @@
</font> @c
@subsection Unarchiving the Tools
<font color='#880000'>-NOTE: This step is required if building any of the tools without using RPM.
</font><font color='#000088'>+@b{NOTE}: This step is required if building any of the tools without using RPM.
</font> It is @b{NOT} required if using the procedure described in @ref{Using RPM
to Build Tools}. This section describes the process of unarchiving the
tools that comprise an RTEMS toolset.
GNU source distributions are archived using @code{tar} and
<font color='#880000'>-compressed using either @code{gzip} or @code{bzip}.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+compressed using either @code{gzip} or @code{bzip}.
</font> If compressed with @code{gzip}, the extension @code{.gz} is used.
If compressed with @code{bzip}, the extension @code{.bz2} is used.
<font color='#997700'>@@ -199,7 +204,7 @@
</font> @item automake-<VERSION>
@item binutils-<VERSION>
@item gcc-<VERSION>
<font color='#880000'>-@item binutils-<VERSION>
</font><font color='#000088'>+@item newlib-<VERSION>
</font> @item gdb-<VERSION>
@end itemize
<font color='#997700'>@@ -222,23 +227,25 @@
</font>
@subsection Applying RTEMS Project Tool Patches
<font color='#880000'>-NOTE: This step is required if building any of the tools IF they have a
</font><font color='#000088'>+@b{NOTE}: This step is required if building any of the tools IF they have a
</font> patch currently required and you are building the tools without using RPM.
is @b{NOT} required if using the procedure described in @ref{Using RPM
to Build Tools}. This section describes the process of applying the
RTEMS patches to any of the tools.
<font color='#880000'>-If a patch is required for a particular tool source tree, then you will
-perform a command similar to the following to apply the patch. In this
-example, <TOOL> should be replaced by the appropriate tool directory
-and <TOOL_PATCH> with the appropriate patch file.
</font><font color='#000088'>+If a patch is required for a particular tool source tree, it is placed in the
+@code{contrib/crossrpms/patches} directory in the CVS tree. Make sure the
+patch version is the same as of the tool you are building. You will perform a
+command similar to the following to apply the patch. In this example, <TOOL>
+should be replaced by the appropriate tool directory and <TOOL_PATCH> with the
+appropriate patch file.
</font>
@example
cd tools/<TOOL>
cat ../../archive/<TOOL_PATCH> | patch -p1
@end example
<font color='#880000'>-NOTE: If you add the @code{--dry-run} option to the @code{patch} command
</font><font color='#000088'>+@b{NOTE}: If you add the @code{--dry-run} option to the @code{patch} command
</font> in the above commands, it will attempt to apply the patch and report
any issues without actually modifying any files.
<font color='#997700'>@@ -260,21 +267,25 @@
</font> This should not happen with a good patch file which is properly applied.
@c
<font color='#880000'>-@c Installing AUTOCONF Without RPM
</font><font color='#000088'>+@c Installing AUTOCONF From Source
</font> @c
<font color='#880000'>-@subsection Installing AUTOCONF Without RPM
</font><font color='#000088'>+@subsection Installing AUTOCONF From Source
</font>
The following example illustrates the invocation of @code{configure}
<font color='#880000'>-and @code{make} to build and install autoconf-<version>. This tool is<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and @code{make} to build and install autoconf-<version>. This tool is
</font> installed as a native utility and is independent of any RTEMS target.
<font color='#000088'>+@b{NOTE}: If no patch is required for Autoconf and Automake, you can use the
+standard package manager provided by your Linux distribution to install them.
+Of course, the versions provided by your package manager should be the same
+that specified in Makefile.am or better.
+
</font> @example
mkdir b-autoconf
cd b-autoconf
../autoconf-<VERSION>/configure --prefix=@value{RTEMSPREFIX}
<font color='#880000'>-make all
-make info
</font><font color='#000088'>+make
</font> make install
@end example
<font color='#997700'>@@ -286,13 +297,13 @@
</font> autoconf-VERSION> @code{configure} command with the @code{--help} option.
@c
<font color='#880000'>-@c Installing AUTOMAKE Without RPM
</font><font color='#000088'>+@c Installing AUTOMAKE From Source
</font> @c
<font color='#880000'>-@subsection Installing AUTOMAKE Without RPM
</font><font color='#000088'>+@subsection Installing AUTOMAKE From Source
</font>
The following example illustrates the invocation of @code{configure}
<font color='#880000'>-and @code{make} to build and install automake-<version>. This tool is<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and @code{make} to build and install automake-<version>. This tool is
</font> installed as a native utility and is independent of any RTEMS target.
@example
<font color='#997700'>@@ -312,9 +323,9 @@
</font> automake-VERSION> @code{configure} command with the @code{--help} option.
@c
<font color='#880000'>-@c Installing BINUTILS Without RPM
</font><font color='#000088'>+@c Installing BINUTILS From Source
</font> @c
<font color='#880000'>-@subsection Installing BINUTILS Without RPM
</font><font color='#000088'>+@subsection Installing BINUTILS From Source
</font>
The following example illustrates the invocation of @code{configure}
and @code{make} to build and install binutils-<version>
<font color='#997700'>@@ -346,6 +357,14 @@
</font> export PATH=@value{RTEMSPREFIX}/bin:$@{PATH@}
@end example
<font color='#000088'>+As you will need to frequently run various commands in the
+@value{RTEMSPREFIX}/bin, you can update your @code{~/.bashrc} to include this
+line. After doing that, don't forget to run
+@example
+source ~/.bashrc
+@end example
+for the changes to take place.
+
</font> Failure to have the binutils in the path will cause the GCC and NEWLIB
build to fail with an error message similar to:
<font color='#997700'>@@ -358,11 +377,11 @@
</font> @c
@subsection Installing GCC and NEWLIB Without RPM
<font color='#880000'>-Before building gcc-<VERSION> and newlib-<VERSION>,<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Before building gcc-<VERSION> and newlib-<VERSION>,
</font> binutils-<VERSION> must be installed and the directory
containing those executables must be in your PATH.
<font color='#880000'>-The C Library is built as a subordinate component of<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The C Library is built as a subordinate component of
</font> gcc-<VERSION>. Because of this, the newlib-<VERSION>
directory source must be available inside the gcc-<VERSION>
source tree. This is normally accomplished using a symbolic
<font color='#997700'>@@ -390,7 +409,7 @@
</font> make install
@end example
<font color='#880000'>-After gcc-<VERSION> is built and installed the<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+After gcc-<VERSION> is built and installed the
</font> build directory @code{b-gcc} may be removed.
For more information on the invocation of @code{configure}, please
<font color='#997700'>@@ -408,11 +427,11 @@
</font> the host environment and additional build steps to perform.
It is critical that you use the same version of GCC/GNAT as
the native compiler. GNAT must be compiled with an Ada compiler
<font color='#880000'>-and when building a GNAT cross-compiler, it should be<span style="background-color: #FF0000"> </span>
-the same version of GNAT itself.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and when building a GNAT cross-compiler, it should be
+the same version of GNAT itself.
</font>
It is also important to verify whether there is an RTEMS specific
<font color='#880000'>-Ada patch required for GCC. These can be found in<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Ada patch required for GCC. These can be found in
</font> @uref{http://www.rtems.org/ftp/pub/rtems/people/joel/ada,
http://www.rtems.org/ftp/pub/rtems/people/joel/ada}. The patch is
often a minor version or two behind GCC but will usually apply cleanly.
<font color='#997700'>@@ -458,7 +477,7 @@
</font> @c
@subsection Installing GDB Without RPM
<font color='#880000'>-NOTE: This step is NOT required if prebuilt executables for the
</font><font color='#000088'>+@b{NOTE}: This step is NOT required if prebuilt executables for the
</font> GDB were installed and they meet your target interface
requirements.
<font color='#997700'>@@ -538,7 +557,7 @@
</font> well as to capture the procedure and source code used to produce those
binary files. For RPM, it is assumed that the following subdirectories
are under a root directory such as @code{/usr/src/redhat} or
<font color='#880000'>-@code{/usr/local/src/redhat}) on your machine.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@code{/usr/local/src/redhat}) on your machine.
</font>
@example
BUILD
<font color='#997700'>@@ -551,7 +570,7 @@
</font> For the purposes of this document, the RPM @code{SOURCES} directory is the
directory into which all tool source and patches are assumed to reside.
The @code{BUILD} directory is where the actual build is performed when
<font color='#880000'>-building binaries from a source RPM.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+building binaries from a source RPM.
</font>
RPM automatically unarchives the source and applies any needed patches
so you do @b{NOT} have to manually perform the procedures described
<font color='#997700'>@@ -581,7 +600,7 @@
</font> compiled, AUTOCONF binary RPM that matches the installed source RPM.
This example assumes that all of the required source is installed.
<font color='#880000'>-@example<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@example
</font> rpm -U @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-autoconf-<VERSION>-<RPM_RELEASE>.src.rpm
@end example
<font color='#997700'>@@ -598,7 +617,7 @@
</font> @value{RTEMSRPMPREFIX}rtems@value{RTEMSAPI}-autoconf-<VERSION>-<RPM_RELEASE>.<ARCH>.rpm
@end example
<font color='#880000'>-NOTE: It may be necessary to remove the build tree in the @code{BUILD}
</font><font color='#000088'>+@b{NOTE}: It may be necessary to remove the build tree in the @code{BUILD}
</font> directory under the RPM root directory.
@c
<font color='#997700'>@@ -610,7 +629,7 @@
</font> compiled, AUTOMAKE binary RPM that matches the installed source RPM.
This example assumes that all of the required source is installed.
<font color='#880000'>-@example<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@example
</font> rpm -U @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-automake-<VERSION>-<RPM_RELEASE>.src.rpm
@end example
<font color='#997700'>@@ -627,7 +646,7 @@
</font> @value{RTEMSRPMPREFIX}rtems@value{RTEMSAPI}-automake-<VERSION>-<RPM_RELEASE>.<ARCH>.rpm
@end example
<font color='#880000'>-NOTE: It may be necessary to remove the build tree in the @code{BUILD}
</font><font color='#000088'>+@b{NOTE}: It may be necessary to remove the build tree in the @code{BUILD}
</font> directory under the RPM root directory.
<font color='#997700'>@@ -640,7 +659,7 @@
</font> compiled, binutils binary RPM that matches the installed source RPM.
This example assumes that all of the required source is installed.
<font color='#880000'>-@example<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@example
</font> rpm -U @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-binutils-<VERSION>-<RPM_RELEASE>.src.rpm
@end example
<font color='#997700'>@@ -691,9 +710,9 @@
</font> @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-libstd++-<VERSION>-<RPM>.<ARCH>.rpm
@end example
<font color='#880000'>-NOTE: Some targets do not support building all languages.
</font><font color='#000088'>+@b{NOTE}: Some targets do not support building all languages.
</font>
<font color='#880000'>-NOTE: It may be necessary to remove the build tree in the
</font><font color='#000088'>+@b{NOTE}: It may be necessary to remove the build tree in the
</font> @code{BUILD} directory under the RPM root directory.
@c
<font color='#997700'>@@ -724,7 +743,7 @@
</font> @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-gdb-<VERSION>-<RPM_RELEASE>.<ARCH>.rpm
@end example
<font color='#880000'>-NOTE: It may be necessary to remove the build tree in the
</font><font color='#000088'>+@b{NOTE}: It may be necessary to remove the build tree in the
</font> @code{BUILD} directory under the RPM root directory.
@c
<font color='#997700'>@@ -749,13 +768,13 @@
</font> @end itemize
If you are using binutils 2.9.1 or newer with certain older versions of
<font color='#880000'>-gcc, they do not agree on what the name of the newly<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+gcc, they do not agree on what the name of the newly
</font> generated cross assembler is. Older binutils called it @code{as.new}
which became @code{as.new.exe} under Windows. This is not a valid
file name, so @code{as.new} is now called @code{as-new}. By using the latest
released tool versions and RTEMS patches, this problem will be avoided.
<font color='#880000'>-If binutils did not successfully build the cross assembler, then<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+If binutils did not successfully build the cross assembler, then
</font> the new cross gcc (@code{xgcc}) used to build the libraries can not
find it. Make sure the build of the binutils succeeded.
<font color='#997700'>@@ -767,7 +786,7 @@
</font> is a security risk and should be avoided. Remove "." from
your PATH.
<font color='#880000'>-NOTE: In some environments, it may be difficult to remove "."
</font><font color='#000088'>+@b{NOTE}: In some environments, it may be difficult to remove "."
</font> completely from your PATH. In this case, make sure that "."
is after the system directories containing "as" and "ld".
<font color='#997700'>@@ -783,7 +802,7 @@
</font>
@end itemize
<font color='#880000'>-Then it is likely that one or more of your gnu tools is<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Then it is likely that one or more of your gnu tools is
</font> already configured locally in its source tree. You can check
for this by searching for the @code{config.status} file
in the various tool source trees. The following command
<font color='#997700'>@@ -793,7 +812,7 @@
</font> find binutils-<VERSION> -name config.status -print
@end example
<font color='#880000'>-The solution for this is to execute the command<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The solution for this is to execute the command
</font> @code{make distclean} in each of the GNU tools
root source directory. This should remove all
generated files including Makefiles.
<font color='#997700'>@@ -810,9 +829,8 @@
</font> -I../../binutils-<VERSION>/gcc -I/binutils-<VERSION>/gcc/include -I.
@end example
<font color='#880000'>-Note that the tool source directory is searched before the<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Note that the tool source directory is searched before the
</font> build directory.
<font color='#880000'>-This situation can be avoided entirely by never using<span style="background-color: #FF0000"> </span>
-the source tree as the build directory -- even for
-
</font><font color='#000088'>+This situation can be avoided entirely by never using
+the source tree as the build directory.
</font>
<font color='#006600'>diff -u rtems/doc/started/buildc.t:1.48 rtems/doc/started/buildc.t:1.48.2.1
--- rtems/doc/started/buildc.t:1.48 Thu Sep 25 14:34:41 2008
+++ rtems/doc/started/buildc.t Sun Jan 2 10:12:04 2011
</font><font color='#997700'>@@ -75,6 +75,10 @@
</font> @c URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}
@c @end ifset
@end example
<font color='#000088'>+If no patches are required, you can use a package manager provided by your
+Linux distribution to install AUTOMAKE and AUTOCONF to avoid building them from
+source.
+
</font>
@need 1000
@subheading @value{NEWLIBUNTAR}
<font color='#997700'>@@ -132,7 +136,7 @@
</font> described in @ref{Using RPM to Build BINUTILS GCC and NEWLIB}.
GNU source distributions are archived using @code{tar} and
<font color='#880000'>-compressed using either @code{gzip} or @code{bzip}.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+compressed using either @code{gzip} or @code{bzip}.
</font> If compressed with @code{gzip}, the extension @code{.gz} is used.
If compressed with @code{bzip}, the extension @code{.bz2} is used.
<font color='#997700'>@@ -224,6 +228,11 @@
</font>
Check to see if any of these patches have been rejected using the following
sequence:
<font color='#000088'>+@b{NOTE}: If no patch is required for Autoconf and Automake, you can use the
+standard package manager provided by your Linux distribution to install them.
+Of course, the versions provided by your package manager should be the same
+that specified in Makefile.am or better.
+
</font>
@example
cd tools/@value{GCCUNTAR}
<font color='#997700'>@@ -494,8 +503,7 @@
</font> cd b-binutils
../@value{BINUTILSUNTAR}/configure --target=sparc-rtems@value{RTEMSAPI} \
--prefix=@value{RTEMSPREFIX}
<font color='#880000'>-make all
-make info
</font><font color='#000088'>+make
</font> make install
@end example
<font color='#997700'>@@ -567,6 +575,14 @@
</font> For more information on the invocation of @code{configure}, please
refer to the documentation for @value{GCCUNTAR} or
invoke the @value{GCCUNTAR} @code{configure} command with the
<font color='#000088'>+As you will need to frequently run various commands in the
+@value{RTEMSPREFIX}/bin, you can update your @code{~/.bashrc} to include this
+line. After doing that, don't forget to run
+@example
+source ~/.bashrc
+@end example
+for the changes to take place.
+
</font> @code{--help} option.
@c
<font color='#997700'>@@ -579,8 +595,8 @@
</font> the host environment and additional build steps to perform.
It is critical that you use the same version of GCC/GNAT as
the native compiler. GNAT must be compiled with an Ada compiler
<font color='#880000'>-and when building a GNAT cross-compiler, it should be<span style="background-color: #FF0000"> </span>
-the same version of GNAT itself.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and when building a GNAT cross-compiler, it should be
+the same version of GNAT itself.
</font>
The build procedure is the same until the configure step.<span style="background-color: #FF0000"> </span>
A GCC toolset with GNAT enabled requires that @code{ada}
<font color='#997700'>@@ -822,7 +838,7 @@
</font> @value{RTEMSRPMPREFIX}i386-rtems@value{RTEMSAPI}-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
@end example
<font color='#880000'>-NOTE: It may be necessary to remove the build tree in the
</font><font color='#000088'>+@b{NOTE}: It may be necessary to remove the build tree in the
</font> @code{BUILD} directory under the RPM root directory.
@c
<font color='#997700'>@@ -891,13 +907,13 @@
</font> @end itemize
If you are using binutils 2.9.1 or newer with certain older versions of
<font color='#880000'>-gcc, they do not agree on what the name of the newly<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+gcc, they do not agree on what the name of the newly
</font> generated cross assembler is. Older binutils called it @code{as.new}
which became @code{as.new.exe} under Windows. This is not a valid
file name, so @code{as.new} is now called @code{as-new}. By using the latest
released tool versions and RTEMS patches, this problem will be avoided.
<font color='#880000'>-If binutils did not successfully build the cross assembler, then<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+If binutils did not successfully build the cross assembler, then
</font> the new cross gcc (@code{xgcc}) used to build the libraries can not
find it. Make sure the build of the binutils succeeded.
<font color='#997700'>@@ -909,7 +925,7 @@
</font> is a security risk and should be avoided. Remove "." from
your PATH.
<font color='#880000'>-NOTE: In some environments, it may be difficult to remove "."
</font><font color='#000088'>+@b{NOTE}: In some environments, it may be difficult to remove "."
</font> completely from your PATH. In this case, make sure that "."
is after the system directories containing "as" and "ld".
<font color='#997700'>@@ -925,7 +941,7 @@
</font>
@end itemize
<font color='#880000'>-Then it is likely that one or more of your gnu tools is<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Then it is likely that one or more of your gnu tools is
</font> already configured locally in its source tree. You can check
for this by searching for the @code{config.status} file
in the various tool source trees. The following command
<font color='#997700'>@@ -935,7 +951,7 @@
</font> find @value{BINUTILSUNTAR} -name config.status -print
@end example
<font color='#880000'>-The solution for this is to execute the command<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The solution for this is to execute the command
</font> @code{make distclean} in each of the GNU tools
root source directory. This should remove all
generated files including Makefiles.
<font color='#997700'>@@ -952,9 +968,8 @@
</font> -I../../@value{BINUTILSUNTAR}/gcc -I/@value{BINUTILSUNTAR}/gcc/include -I.
@end example
<font color='#880000'>-Note that the tool source directory is searched before the<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Note that the tool source directory is searched before the
</font> build directory.
<font color='#880000'>-This situation can be avoided entirely by never using<span style="background-color: #FF0000"> </span>
-the source tree as the build directory -- even for
-
</font><font color='#000088'>+This situation can be avoided entirely by never using
+the source tree as the build directory.
</font>
<font color='#006600'>diff -u rtems/doc/started/buildrt.t:1.22 rtems/doc/started/buildrt.t:1.23
--- rtems/doc/started/buildrt.t:1.22 Tue Dec 14 10:51:17 2010
+++ rtems/doc/started/buildrt.t Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -13,9 +13,9 @@
</font> This section provides pointers to the RTEMS source code and example
programs. These files should be placed in your @code{archive} directory.
The set of tarballs which comprise an RTEMS release is placed in a
<font color='#880000'>-directory whose name if the release on the ftp site. The RTEMS ftp site
</font><font color='#000088'>+directory whose name is the release on the ftp site. The RTEMS ftp site
</font> is accessible via both the ftp and http protocols at the following URLs:
<font color='#880000'>-<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+
</font> @itemize @bullet
@item @uref{http://www.rtems.org/ftp/pub/rtems,http://www.rtems.org/ftp/pub/rtems}
@item @uref{ftp://www.rtems.org/pub/rtems,ftp://www.rtems.org/pub/rtems}
<font color='#997700'>@@ -35,7 +35,7 @@
</font> @section Unarchive the RTEMS Source
Use the following command sequence to unpack the RTEMS source into the
<font color='#880000'>-tools directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+tools directory:
</font>
@example
cd tools
<font color='#997700'>@@ -44,6 +44,20 @@
</font>
This creates the directory rtems-@value{RTEMSAPI}.<VERSION>
<font color='#000088'>+@section Obtaining the RTEMS Source from CVS
+
+Instead of downloading release tarballs you may choose to check out the current
+RTEMS source from CVS. For details on accessing RTEMS CVS repository consult
+@uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository}. The steps required
+to obtain the source code from CVS are usually like the following:
+@example
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS login
+Logging in to :pserver:anoncvs@@www.rtems.com:2401/usr1/CVS
+CVS password:
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P rtems # for the main RTEMS source
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P examples-v2 # for examples
+@end example
+
</font> @section Add <INSTALL_POINT>/bin to Executable PATH
In order to compile RTEMS, you must have the cross compilation toolset
<font color='#997700'>@@ -65,9 +79,9 @@
</font>
@section Verifying the Operation of the Cross Toolset
<font color='#880000'>-In order to insure that the cross-compiler is invoking the correct
</font><font color='#000088'>+In order to ensure that the cross-compiler is invoking the correct
</font> subprograms (like @code{as} and @code{ld}), one can test assemble
<font color='#880000'>-a small program. When in verbose mode, @code{gcc} prints out information<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+a small program. When in verbose mode, @code{gcc} prints out information
</font> showing where it found the subprograms it invokes. In a temporary
working directory, place the following function in a file named @code{f.c}:
<font color='#997700'>@@ -110,9 +124,9 @@
</font>
@section Building RTEMS for a Specific Target and BSP
<font color='#880000'>-This section describes how to configure and build RTEMS<span style="background-color: #FF0000"> </span>
-so that it is specifically tailored for your BSP and the
-CPU model it uses. There is currently only one supported
</font><font color='#000088'>+This section describes how to configure and build RTEMS
+so that it is specifically tailored for your BSP (Board Support Package)
+and the CPU model it uses. There is currently only one supported
</font> method to compile and install RTEMS:
@itemize @bullet
<font color='#997700'>@@ -120,7 +134,7 @@
</font> @end itemize
Direct invocation of @code{configure} and @code{make} provides more control
<font color='#880000'>-and easier recovery from problems when building.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and easier recovery from problems when building.
</font>
This section describes how to build RTEMS.
<font color='#997700'>@@ -133,8 +147,8 @@
</font> distribution. A full list of these arguments can be obtained by running
@code{../rtems-@value{RTEMSAPI}.<VERSION>/configure --help} If you
followed the procedure described in the section @ref{Unarchive the
<font color='#880000'>-RTEMS Source}, these configuration options can be found in the file
-tools/rtems-@value{RTEMSAPI}.<VERSION>/README.configure.
</font><font color='#000088'>+RTEMS Source} or @ref{Obtaining the RTEMS Source from CVS}, these configuration options can be found in the file
+rtems-@value{RTEMSAPI}.<VERSION>/README.configure.
</font>
@b{NOTE}: The GNAT/RTEMS run-time implementation is based on the POSIX
API and the GNAT/RTEMS run-time cannot be compiled with networking
<font color='#997700'>@@ -144,7 +158,7 @@
</font>
The following shows the command sequence required to configure,
compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP,
<font color='#880000'>-and C++ support disabled. RTEMS will be built to target<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and C++ support disabled. RTEMS will be built to target
</font> the @code{BOARD_SUPPORT_PACKAGE} board.
@example
<font color='#997700'>@@ -154,7 +168,8 @@
</font> --disable-posix --disable-networking --disable-cxx \
--enable-rtemsbsp=<BSP>\
--prefix=<INSTALL_POINT>
<font color='#880000'>-make all install
</font><font color='#000088'>+make all
+make install
</font> @end example
<TARGET> is of the form <CPU>-rtems@value{RTEMSAPI} and the list of
<font color='#006600'>diff -u rtems/doc/started/buildrt.t:1.21 rtems/doc/started/buildrt.t:1.21.8.1
--- rtems/doc/started/buildrt.t:1.21 Fri Sep 2 11:25:51 2005
+++ rtems/doc/started/buildrt.t Sun Jan 2 10:12:04 2011
</font><font color='#997700'>@@ -38,7 +38,7 @@
</font> @section Unarchive the RTEMS Source
Use the following command sequence to unpack the RTEMS source into the
<font color='#880000'>-tools directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+tools directory:
</font>
@example
cd tools
<font color='#997700'>@@ -47,6 +47,20 @@
</font>
This creates the directory @value{RTEMSUNTAR}.
<font color='#000088'>+@section Obtaining the RTEMS Source from CVS
+
+Instead of downloading release tarballs you may choose to check out the current
+RTEMS source from CVS. For details on accessing RTEMS CVS repository consult
+@uref{http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository, http://www.rtems.org/wiki/index.php/RTEMS_CVS_Repository}. The steps required
+to obtain the source code from CVS are usually like the following:
+@example
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS login
+Logging in to :pserver:anoncvs@@www.rtems.com:2401/usr1/CVS
+CVS password:
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P rtems # for the main RTEMS source
+$ cvs -d :pserver:anoncvs@@www.rtems.com:/usr1/CVS -z 9 co -P examples-v2 # for examples
+@end example
+
</font>
@section Add <INSTALL_POINT>/bin to Executable PATH
<font color='#997700'>@@ -67,9 +81,9 @@
</font>
@section Verifying the Operation of the Cross Toolset
<font color='#880000'>-In order to insure that the cross-compiler is invoking the correct
</font><font color='#000088'>+In order to ensure that the cross-compiler is invoking the correct
</font> subprograms (like @code{as} and @code{ld}), one can test assemble
<font color='#880000'>-a small program. When in verbose mode, @code{gcc} prints out information<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+a small program. When in verbose mode, @code{gcc} prints out information
</font> showing where it found the subprograms it invokes. In a temporary
working directory, place the following function in a file named @code{f.c}:
<font color='#997700'>@@ -113,9 +127,9 @@
</font>
@section Building RTEMS for a Specific Target and BSP
<font color='#880000'>-This section describes how to configure and build RTEMS<span style="background-color: #FF0000"> </span>
-so that it is specifically tailored for your BSP and the
-CPU model it uses. There is currently only one supported
</font><font color='#000088'>+This section describes how to configure and build RTEMS
+so that it is specifically tailored for your BSP (Board Support Package)
+and the CPU model it uses. There is currently only one supported
</font> method to compile and install RTEMS:
@itemize @bullet
<font color='#997700'>@@ -123,7 +137,7 @@
</font> @end itemize
Direct invocation of @code{configure} and @code{make} provides more control
<font color='#880000'>-and easier recovery from problems when building.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and easier recovery from problems when building.
</font>
This section describes how to build RTEMS.
<font color='#997700'>@@ -146,7 +160,7 @@
</font>
The following shows the command sequence required to configure,
compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP,
<font color='#880000'>-and C++ support disabled. RTEMS will be built to target<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+and C++ support disabled. RTEMS will be built to target
</font> the @code{BOARD_SUPPORT_PACKAGE} board.
@example
<font color='#997700'>@@ -156,7 +170,8 @@
</font> --disable-posix --disable-networking --disable-cxx \
--enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\
--prefix=<INSTALL_POINT>
<font color='#880000'>-make all install
</font><font color='#000088'>+make all
+make install
</font> @end example
Where the list of currently supported <TARGET_CONFIGURATION>'s and
<font color='#006600'>diff -u rtems/doc/started/nt.t:1.21 rtems/doc/started/nt.t:1.22
--- rtems/doc/started/nt.t:1.21 Tue Dec 14 10:51:17 2010
+++ rtems/doc/started/nt.t Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -11,9 +11,9 @@
</font> This chapter discusses the installation of the GNU tool chain
on a computer running the Microsoft Windows operating system.
<font color='#880000'>-This chapter was originally written by<span style="background-color: #FF0000"> </span>
-@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>}<span style="background-color: #FF0000"> </span>
-with input from<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This chapter was originally written by
+@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>}
+with input from
</font> @uref{mailto:<D.J@@fiddes.surfaid.org>, David Fiddes <D.J@@fiddes.surfaid.org>}.
It was based upon his successful but unnecessarily painful efforts with
Cygwin beta versions. Cygwin and this chapter have been updated multiple
<font color='#997700'>@@ -24,7 +24,7 @@
</font>
RTEMS users report fewer problems when using Microsoft Windows XP or newer.
<font color='#880000'>-@section Cygwin<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@section Cygwin
</font>
For RTEMS development, the recommended approach is to use Cygwin. Cygwin
is available from @uref{http://www.cygwin.com, http://www.cygwin.com} .
<font color='#997700'>@@ -55,7 +55,7 @@
</font> Copyright 1999 Free Software Foundation, Inc.
@end example
<font color='#880000'>-If you get an error or it claims to be any other shell, you need<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+If you get an error or it claims to be any other shell, you need
</font> to copy it to a fake name and copy
@code{/bin/bash.exe} to @code{/bin/sh.exe}:
<font color='#997700'>@@ -70,14 +70,14 @@
</font>
@item Make sure you unarchive and build in a binary mounted
filesystem (e.g. mounted with the @code{-b} option). Otherwise,
<font color='#880000'>-many confusing errors will result.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+many confusing errors will result.
</font>
@item A user has reported that they needed to set @code{CYGWIN=ntsec}
for chmod to work correctly, but had to set @code{CYGWIN=nontsec}
for compile to work properly (otherwise there were complaints about
permissions on a temporary file).
<font color='#880000'>-@item If you want to build the tools from source, you have the<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@item If you want to build the tools from source, you have the
</font> same options as UNIX users.
@item You may have to uncompress archives during this process. You must
<font color='#997700'>@@ -85,20 +85,27 @@
</font> process uses the GNU @code{zip} and @code{tar} programs as shown below:
@example
<font color='#880000'>-tar -xzvf archive.tgz<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+tar -xzvf archive.tgz
</font> @end example
@code{tar} is provided with Cygwin.
@end itemize
<font color='#000088'>+@section MingGW
+
+You might consider choosing MinGW since it provides better perfomance. There is a wiki entry on a MinGW RTEMS toolset installer available at @uref{http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows,http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows}. Also, there are prebuilt tools for different architectures available for download at @uref{http://www.rtems.org/ftp/pub/rtems/mingw32,http://www.rtems.org/ftp/pub/rtems/mingw32}.
+
</font> @section Text Editor
<font color='#880000'>-You absolutely have to use a text editor which can save files with Unix
-format. So do @b{NOT} use Notepad or Wordpad! There are a number of
-editors freely available that can be used.
</font><font color='#000088'>+You absolutely have to use a text editor which can save files with Unix format.
+So do @b{NOT} use Notepad or Wordpad! Basically, any more or less advanced
+text editor is usually able to do that. There is a number of editors freely
+available that can be used.
</font>
@itemize @bullet
<font color='#000088'>+@item @b{Notepad++} has an interface familiar to Windows users and can be downloaded from @uref{http://notepad-plus-plus.org/,http://notepad-plus-plus.org/}.
+
</font> @item @b{VIM} (@b{Vi IMproved}) is available from
@uref{http://www.vim.org/,http://www.vim.org/}. This editor has the very
handy ability to easily read and write files in either DOS or UNIX style.
<font color='#006600'>diff -u rtems/doc/started/nt.t:1.20 rtems/doc/started/nt.t:1.20.8.1
--- rtems/doc/started/nt.t:1.20 Fri Sep 26 16:19:52 2003
+++ rtems/doc/started/nt.t Sun Jan 2 10:12:05 2011
</font><font color='#997700'>@@ -1,5 +1,5 @@
</font> @c
<font color='#880000'>-@c COPYRIGHT (c) 1988-2002.
</font><font color='#000088'>+@c COPYRIGHT (c) 1988-2010.
</font> @c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
<font color='#997700'>@@ -11,35 +11,28 @@
</font> This chapter discusses the installation of the GNU tool chain
on a computer running the Microsoft Windows operating system.
<font color='#880000'>-This chapter was originally written by<span style="background-color: #FF0000"> </span>
-@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>}<span style="background-color: #FF0000"> </span>
-with input from<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This chapter was originally written by
+@uref{mailto:g_montel@@yahoo.com, Geoffroy Montel <g_montel@@yahoo.com>}
+with input from
</font> @uref{mailto:<D.J@@fiddes.surfaid.org>, David Fiddes <D.J@@fiddes.surfaid.org>}.
<font color='#880000'>-It was based upon his successful but unnecessarily
-painful efforts with Cygwin beta versions.
-Cygwin and this chapter have been updated multiple times since
-those early days although their pioneering efforts
-and input is still greatly appreciated.
</font><font color='#000088'>+It was based upon his successful but unnecessarily painful efforts with
+Cygwin beta versions. Cygwin and this chapter have been updated multiple
+times since those early days although their pioneering efforts and input
+is still greatly appreciated.
</font>
@section Microsoft Windows Version Requirements
<font color='#880000'>-RTEMS users report fewer problems when using Microsoft
-Windows NT, 2000, or XP. Although, the open source tools
-that are used in RTEMS development do execute on Windows 95,
-98, or ME, they tend to be more stable when used with
-the modern Windows variants.
-
-@section Cygwin<span style="background-color: #FF0000"> </span>
-
-For RTEMS development, the recommended approach is to use
-Cygwin 1.0 or later. Cygwin is available from
-@uref{http://sources.redhat.com/cygwin, http://sources.redhat.com/cygwin}<span style="background-color: #FF0000"> </span>
-Recent versions of Cygwin are vastly improved over the beta
-versions. Most of the oddities, instabilities, and performance
-problems have been resolved. The installation procedure
-is much simpler. However, there are a handful of issues
-that remain to successfully use Cygwin as an RTEMS development
-environment.
</font><font color='#000088'>+RTEMS users report fewer problems when using Microsoft Windows XP or newer.
+
+@section Cygwin
+
+For RTEMS development, the recommended approach is to use Cygwin. Cygwin
+is available from @uref{http://www.cygwin.com, http://www.cygwin.com} .
+The primary issues reported by users of Cygwin is that it is slower
+on the same hardware than a native GNU/Linux installation and strange
+issues over carriage return/line feed inconsistencies between UNIX and
+Windows environments. However, there are a handful of other issues that
+may turn up when using Cygwin as an RTEMS development environment.
</font>
@itemize @bullet
<font color='#997700'>@@ -62,7 +55,7 @@
</font> Copyright 1999 Free Software Foundation, Inc.
@end example
<font color='#880000'>-If you get an error or it claims to be any other shell, you need<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+If you get an error or it claims to be any other shell, you need
</font> to copy it to a fake name and copy
@code{/bin/bash.exe} to @code{/bin/sh.exe}:
<font color='#997700'>@@ -77,45 +70,49 @@
</font>
@item Make sure you unarchive and build in a binary mounted
filesystem (e.g. mounted with the @code{-b} option). Otherwise,
<font color='#880000'>-many confusing errors will result.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+many confusing errors will result.
</font>
<font color='#880000'>-@item A user has reported that they needed<span style="background-color: #FF0000"> </span>
-to set CYGWIN=ntsec for chmod to work correctly, but had to set<span style="background-color: #FF0000"> </span>
-CYGWIN=nontsec for compile to work properly (otherwise there were
-complaints about permissions on a temporary file).
</font><font color='#000088'>+@item A user has reported that they needed to set @code{CYGWIN=ntsec}
+for chmod to work correctly, but had to set @code{CYGWIN=nontsec}
+for compile to work properly (otherwise there were complaints about
+permissions on a temporary file).
</font>
<font color='#880000'>-@item If you want to build the tools from source, you have the<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@item If you want to build the tools from source, you have the
</font> same options as UNIX users.
<font color='#880000'>-@item You may have to uncompress archives during this
-process. You must @b{NOT} use @code{WinZip} or
-@code{PKZip}. Instead the un-archiving process uses
-the GNU @code{zip} and @code{tar} programs as shown below:
</font><font color='#000088'>+@item You may have to uncompress archives during this process. You must
+@b{NOT} use @code{WinZip} or @code{PKZip}. Instead the un-archiving
+process uses the GNU @code{zip} and @code{tar} programs as shown below:
</font>
@example
<font color='#880000'>-tar -xzvf archive.tgz<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+tar -xzvf archive.tgz
</font> @end example
@code{tar} is provided with Cygwin.
@end itemize
<font color='#000088'>+@section MingGW
+
+You might consider choosing MinGW since it provides better perfomance. There is a wiki entry on a MinGW RTEMS toolset installer available at @uref{http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows,http://www.rtems.org/wiki/index.php/MinGW_Tools_for_Windows}. Also, there are prebuilt tools for different architectures available for download at @uref{http://www.rtems.org/ftp/pub/rtems/mingw32,http://www.rtems.org/ftp/pub/rtems/mingw32}.
+
</font> @section Text Editor
<font color='#880000'>-You absolutely have to use a text editor which can<span style="background-color: #FF0000"> </span>
-save files with Unix format. So do @b{NOT} use Notepad<span style="background-color: #FF0000"> </span>
-or Wordpad! There are a number of editors
-freely available that can be used.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+You absolutely have to use a text editor which can save files with Unix format.
+So do @b{NOT} use Notepad or Wordpad! Basically, any more or less advanced
+text editor is usually able to do that. There is a number of editors freely
+available that can be used.
</font>
@itemize @bullet
<font color='#000088'>+@item @b{Notepad++} has an interface familiar to Windows users and can be downloaded from @uref{http://notepad-plus-plus.org/,http://notepad-plus-plus.org/}.
+
</font> @item @b{VIM} (@b{Vi IMproved}) is available from
<font color='#880000'>-@uref{http://www.vim.org/,http://www.vim.org/}.<span style="background-color: #FF0000"> </span>
-This editor has the very handy ability to easily
-read and write files in either DOS or UNIX style.
</font><font color='#000088'>+@uref{http://www.vim.org/,http://www.vim.org/}. This editor has the very
+handy ability to easily read and write files in either DOS or UNIX style.
</font>
@item @b{GNU Emacs} is available for many platforms
<font color='#880000'>-including MS-Windows. The official homepage<span style="background-color: #FF0000"> </span>
-is @uref{http://www.gnu.org/software/emacs/emacs.html,
</font><font color='#000088'>+including MS-Windows. The official homepage is
+@uref{http://www.gnu.org/software/emacs/emacs.html,
</font> http://www.gnu.org/software/emacs/emacs.html}.
The GNU Emacs on Windows NT and Windows 95/98 FAQ is at
@uref{http://www.gnu.org/software/emacs/windows/ntemacs.html,
<font color='#997700'>@@ -123,11 +120,10 @@
</font>
@end itemize
<font color='#880000'>-If you do accidentally end up with files<span style="background-color: #FF0000"> </span>
-having MS-DOS style line termination, then you
-may have to convert them to Unix format for some
-Cygwin programs to operate on them properly. The<span style="background-color: #FF0000"> </span>
-program @code{dos2unix} can be used to put them
</font><font color='#000088'>+If you do accidentally end up with files having MS-DOS style line
+termination, then you may have to convert them to Unix format for some
+Cygwin programs to operate on them properly. The program @code{dos2unix}
+can be used to put them
</font> back into Unix format as shown below:
@example
<font color='#997700'>@@ -137,22 +133,16 @@
</font>
@section System Requirements
<font color='#880000'>-Although the finished cross-compiler is fairly easy on resources,
-building it can take a significant amount of processing power and<span style="background-color: #FF0000"> </span>
-disk space.<span style="background-color: #FF0000"> </span>
-
-@itemize @bullet
-
-@item The faster the CPU, the better. The tools and Cygwin can be
-@b{very} CPU hungry.
-
-@item The more RAM, the better. Reports are that when building GCC
-and GDB, peak memory usage can exceed 256 megabytes.
-
-@item The more disk space, the better. You need more if you are building
-the GNU tools and the amount of disk space for binaries is obviously
-directly dependent upon the number of CPUs you have cross toolsets
-installed for.
-
-@end itemize
-
</font><font color='#000088'>+Although the finished cross-compiler is fairly easy on resources, building
+it can take a significant amount of processing power and disk space.
+Luckily, desktop computers have progressed very far since this guide
+was originally written so it is unlikely you will have any problems.
+Just do not use an old cast-off machine with < 1 GB RAM and a 1 Ghz CPU.
+Unless, of course, you enjoy waiting for things to complete.
+
+The more disk space, the better. You need more if you are building the
+GNU tools and the amount of disk space for binaries is obviously directly
+dependent upon the number of CPUs you have cross toolsets installed for.
+In addition to the disk space requirements documented earlier for tool
+building, you will also have to have enough space to install the Cygwin
+environment.
</font>
<font color='#006600'>diff -u rtems/doc/started/require.t:1.14 rtems/doc/started/require.t:1.15
--- rtems/doc/started/require.t:1.14 Tue Dec 14 10:51:17 2010
+++ rtems/doc/started/require.t Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -8,14 +8,14 @@
</font>
@chapter Requirements
<font color='#880000'>-This chapter describes the build-host system requirements and initial steps<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This chapter describes the build-host system requirements and initial steps
</font> in installing the GNU Cross Compiler Tools and RTEMS on a build-host.
@section Disk Space
A fairly large amount of disk space is required to perform the build of the
GNU C/C++ Cross Compiler Tools for RTEMS. The following table may help in
<font color='#880000'>-assessing the amount of disk space required for your installation:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+assessing the amount of disk space required for your installation:
</font>
@example
+------------------------------------+--------------------------+
<font color='#997700'>@@ -45,7 +45,7 @@
</font> There are a number of factors which must be taken into
account in order to estimate the amount of disk space required
to build RTEMS itself. Attempting to build multiple BSPs in
<font color='#880000'>-a single step increases the disk space requirements. One some
</font><font color='#000088'>+a single step increases the disk space requirements. On some
</font> target architectures, this can lead to disk usage during the build
of over one gigabyte.
<font color='#997700'>@@ -87,7 +87,7 @@
</font> Both NEWLIB and RTEMS use GNU make specific features and can only be built
using GNU make. Many systems include a make utility that is not GNU make.
The safest way to meet this requirement is to ensure that when you invoke
<font color='#880000'>-the command @code{make}, it is GNU make. This can be verified by<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+the command @code{make}, it is GNU make. This can be verified by
</font> attempting to print the GNU make version information:
@example
<font color='#997700'>@@ -95,7 +95,7 @@
</font> @end example
If you have GNU make and another make on your system, it is common to put
<font color='#880000'>-the directory containing GNU make before the directory containing other<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+the directory containing GNU make before the directory containing other
</font> implementations of make.
@subsection GNU makeinfo Version Requirements
<font color='#997700'>@@ -155,7 +155,7 @@
</font>
@end itemize
<font color='#880000'>-@subsection GNU/Linux Distrobutions using Debian Packaging Format<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@subsection GNU/Linux Distrobutions using Debian Packaging Format
</font>
The RTEMS Project does not currently provide prebuilt toolsets in the Debian packaging format used by the Debian and Ubuntu distributions. If you are using a distribution using this packaging format, then you have two options for installing the RTEMS toolset.
<font color='#006600'>diff -u rtems/doc/started/require.t:1.13 rtems/doc/started/require.t:1.13.8.1
--- rtems/doc/started/require.t:1.13 Tue Feb 3 18:34:09 2004
+++ rtems/doc/started/require.t Sun Jan 2 10:12:05 2011
</font><font color='#997700'>@@ -8,14 +8,14 @@
</font>
@chapter Requirements
<font color='#880000'>-This chapter describes the build-host system requirements and initial steps<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This chapter describes the build-host system requirements and initial steps
</font> in installing the GNU Cross Compiler Tools and RTEMS on a build-host.
@section Disk Space
A fairly large amount of disk space is required to perform the build of the
GNU C/C++ Cross Compiler Tools for RTEMS. The following table may help in
<font color='#880000'>-assessing the amount of disk space required for your installation:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+assessing the amount of disk space required for your installation:
</font>
@example
+------------------------------------+--------------------------+
<font color='#997700'>@@ -82,7 +82,7 @@
</font> Both NEWLIB and RTEMS use GNU make specific features and can only be built
using GNU make. Many systems include a make utility that is not GNU make.
The safest way to meet this requirement is to ensure that when you invoke
<font color='#880000'>-the command @code{make}, it is GNU make. This can be verified by<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+the command @code{make}, it is GNU make. This can be verified by
</font> attempting to print the GNU make version information:
@example
<font color='#997700'>@@ -90,7 +90,7 @@
</font> @end example
If you have GNU make and another make on your system, it is common to put
<font color='#880000'>-the directory containing GNU make before the directory containing other<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+the directory containing GNU make before the directory containing other
</font> implementations of make.
@subsection GNU makeinfo Version Requirements
<font color='#006600'>diff -u rtems/doc/started/sample.t:1.16 rtems/doc/started/sample.t:1.17
--- rtems/doc/started/sample.t:1.16 Tue Dec 14 10:51:17 2010
+++ rtems/doc/started/sample.t Sun Jan 2 10:12:02 2011
</font><font color='#997700'>@@ -8,20 +8,20 @@
</font>
@chapter Building the Sample Applications
<font color='#880000'>-The RTEMS distribution includes a number of sample C, C++,<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The RTEMS distribution includes a number of sample C, C++,
</font> Ada, and networking applications. This chapter will provide
an overview of those sample applications.
@c
<font color='#880000'>-@c Set the Environment Variable RTEMS_MAKEFILE_PATH<span style="background-color: #FF0000"> </span>
-@c<span style="background-color: #FF0000"> </span>
-@section Set the Environment Variable RTEMS_MAKEFILE_PATH<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@c Set the Environment Variable RTEMS_MAKEFILE_PATH
+@c
+@section Set the Environment Variable RTEMS_MAKEFILE_PATH
</font>
The sample application sets use the RTEMS Application Makefiles.
<font color='#880000'>-This requires that the environment variable<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This requires that the environment variable
</font> @code{RTEMS_MAKEFILE_PATH} point to the appropriate directory containing
the installed RTEMS image built to target your particular CPU and
<font color='#880000'>-board support package combination.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+board support package combination.
</font>
@example
export RTEMS_MAKEFILE_PATH=<INSTALLATION_POINT>/<CPU>-rtems/<BOARD_SUPPORT_PACKAGE>
<font color='#997700'>@@ -30,17 +30,17 @@
</font> Where <INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> are those used when
configuring and installing RTEMS.
<font color='#880000'>-NOTE: In release 4.0, BSPs were installed at
</font><font color='#000088'>+@b{NOTE}: In release 4.0, BSPs were installed at
</font> @code{<INSTALLATION_POINT>/rtems/<BOARD_SUPPORT_PACKAGE>}. This
was changed to be more in compliance with GNU standards.
<font color='#880000'>-NOTE: GNU make is the preferred @code{make} utility. Other @code{make}
</font><font color='#000088'>+@b{NOTE}: GNU make is the preferred @code{make} utility. Other @code{make}
</font> implementations may work but all testing is done with GNU make.
If no errors are detected during the sample application build, it is
reasonable to assume that the build of the GNU Cross Compiler Tools
for RTEMS and RTEMS itself for the selected host and target
<font color='#880000'>-combination was done properly.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+combination was done properly.
</font>
@c
@c Executing the Sample Applications
<font color='#997700'>@@ -97,7 +97,7 @@
</font> integrated with the processor. This BSP can be used with
either real hardware or with the simulator included with
@code{mipstx39-rtems-gdb}. An application can be run on the simulator
<font color='#880000'>-by executing the following commands upon entering @code{mipstx39-rtems-gdb}:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+by executing the following commands upon entering @code{mipstx39-rtems-gdb}:
</font>
@example
target sim --board=jmr3904
<font color='#997700'>@@ -117,10 +117,11 @@
</font> to the script @code{powerpc/psim/tools/psim}.
@item sparc/erc32
<font color='#880000'>-The ERC32 is a radiation hardened SPARC V7. This BSP can be used with
-either real ERC32 hardware or with the simulator included with
-@code{sparc-rtems-gdb}. An application can be run on the simulator
-by executing the following commands upon entering @code{sparc-rtems-gdb}:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The ERC32 is a radiation hardened SPARC V7. This BSP can be used with either
+real ERC32 hardware or with the simulator included with @code{sparc-rtems-gdb}
+(for this, you should configure RTEMS to use @code{sis} BSP). An application
+can be run on the simulator by executing the following commands upon entering
+@code{sparc-rtems-gdb}:
</font>
@example
target sim
<font color='#997700'>@@ -128,6 +129,10 @@
</font> run
@end example
<font color='#000088'>+In case that you don't need a debugger, an application can be run by
+@code{spart-rtems-run}.
+
+
</font> @end table
RTEMS has many more BSPs and new BSPs for commercial boards and CPUs
<font color='#997700'>@@ -141,7 +146,7 @@
</font> The C/C++ sample application set includes a number of simple applications.
Some demonstrate some basic functionality in RTEMS such as writing
a file, closing it, and reading it back while others can serve as
<font color='#880000'>-starting points for RTEMS applications or libraries. Start by<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+starting points for RTEMS applications or libraries. Start by
</font> unarchiving them so you can peruse them. Use a command similar to
the following to unarchive the sample applications:
<font color='#997700'>@@ -159,8 +164,8 @@
</font> @c
@subheading Build the C Hello World Application
<font color='#880000'>-Use the following command to start the build of the sample hello<span style="background-color: #FF0000"> </span>
-world application:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Use the following command to start the build of the sample hello
+world application:
</font>
@example
cd hello_world_c
<font color='#997700'>@@ -169,7 +174,7 @@
</font>
If the sample application has successfully been built, then the application
<font color='#880000'>-executable is placed in the following directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+executable is placed in the following directory:
</font>
@example
hello_world_c/o-optimize/<filename>.ralf
<font color='#997700'>@@ -205,7 +210,7 @@
</font>
@section Build the Sample Application
<font color='#880000'>-Use the following command to start the build of the sample application:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Use the following command to start the build of the sample application:
</font>
@example
cd tools/ada-examples-@value{RTEMSAPI}.<VERSION>/ada-examples/hello_world_ada
<font color='#997700'>@@ -216,10 +221,10 @@
</font> for RTEMS and RTEMS itself for the selected host and target combination
was done properly.
<font color='#880000'>-@section Application Executable<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@section Application Executable
</font>
If the sample application has successfully been build, then the application
<font color='#880000'>-executable is placed in the following directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+executable is placed in the following directory:
</font>
@example
tools/@code{ada-examples-@value{RTEMSAPI}.<VERSION>}/hello_world_ada/o-optimize/<filename>.exe
<font color='#006600'>diff -u rtems/doc/started/sample.t:1.15 rtems/doc/started/sample.t:1.15.8.1
--- rtems/doc/started/sample.t:1.15 Mon Sep 27 17:28:16 2004
+++ rtems/doc/started/sample.t Sun Jan 2 10:12:05 2011
</font><font color='#997700'>@@ -8,20 +8,20 @@
</font>
@chapter Building the Sample Applications
<font color='#880000'>-The RTEMS distribution includes a number of sample C, C++,<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The RTEMS distribution includes a number of sample C, C++,
</font> Ada, and networking applications. This chapter will provide
an overview of those sample applications.
@c
<font color='#880000'>-@c Set the Environment Variable RTEMS_MAKEFILE_PATH<span style="background-color: #FF0000"> </span>
-@c<span style="background-color: #FF0000"> </span>
-@section Set the Environment Variable RTEMS_MAKEFILE_PATH<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@c Set the Environment Variable RTEMS_MAKEFILE_PATH
+@c
+@section Set the Environment Variable RTEMS_MAKEFILE_PATH
</font>
The sample application sets use the RTEMS Application Makefiles.
<font color='#880000'>-This requires that the environment variable<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+This requires that the environment variable
</font> @code{RTEMS_MAKEFILE_PATH} point to the appropriate directory containing
the installed RTEMS image built to target your particular CPU and
<font color='#880000'>-board support package combination.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+board support package combination.
</font>
@example
export RTEMS_MAKEFILE_PATH=<INSTALLATION_POINT>/<CPU>-rtems/<BOARD_SUPPORT_PACKAGE>
<font color='#997700'>@@ -30,17 +30,17 @@
</font> Where <INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> are those used when
configuring and installing RTEMS.
<font color='#880000'>-NOTE: In release 4.0, BSPs were installed at
</font><font color='#000088'>+@b{NOTE}: In release 4.0, BSPs were installed at
</font> @code{<INSTALLATION_POINT>/rtems/<BOARD_SUPPORT_PACKAGE>}. This
was changed to be more in compliance with GNU standards.
<font color='#880000'>-NOTE: GNU make is the preferred @code{make} utility. Other @code{make}
</font><font color='#000088'>+@b{NOTE}: GNU make is the preferred @code{make} utility. Other @code{make}
</font> implementations may work but all testing is done with GNU make.
If no errors are detected during the sample application build, it is
reasonable to assume that the build of the GNU Cross Compiler Tools
for RTEMS and RTEMS itself for the selected host and target
<font color='#880000'>-combination was done properly.<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+combination was done properly.
</font>
@c
@c Executing the Sample Applications
<font color='#997700'>@@ -97,7 +97,7 @@
</font> integrated with the processor. This BSP can be used with
either real hardware or with the simulator included with
@code{mipstx39-rtems-gdb}. An application can be run on the simulator
<font color='#880000'>-by executing the following commands upon entering @code{mipstx39-rtems-gdb}:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+by executing the following commands upon entering @code{mipstx39-rtems-gdb}:
</font>
@example
target sim --board=jmr3904
<font color='#997700'>@@ -117,10 +117,11 @@
</font> to the script @code{powerpc/psim/tools/psim}.
@item sparc/erc32
<font color='#880000'>-The ERC32 is a radiation hardened SPARC V7. This BSP can be used with
-either real ERC32 hardware or with the simulator included with
-@code{sparc-rtems-gdb}. An application can be run on the simulator
-by executing the following commands upon entering @code{sparc-rtems-gdb}:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+The ERC32 is a radiation hardened SPARC V7. This BSP can be used with either
+real ERC32 hardware or with the simulator included with @code{sparc-rtems-gdb}
+(for this, you should configure RTEMS to use @code{sis} BSP). An application
+can be run on the simulator by executing the following commands upon entering
+@code{sparc-rtems-gdb}:
</font>
@example
target sim
<font color='#997700'>@@ -128,6 +129,10 @@
</font> run
@end example
<font color='#000088'>+In case that you don't need a debugger, an application can be run by
+@code{spart-rtems-run}.
+
+
</font> @end table
RTEMS has many more BSPs and new BSPs for commercial boards and CPUs
<font color='#997700'>@@ -141,7 +146,7 @@
</font> The C/C++ sample application set includes a number of simple applications.
Some demonstrate some basic functionality in RTEMS such as writing
a file, closing it, and reading it back while others can serve as
<font color='#880000'>-starting points for RTEMS applications or libraries. Start by<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+starting points for RTEMS applications or libraries. Start by
</font> unarchiving them so you can peruse them. Use a command similar to
the following to unarchive the sample applications:
<font color='#997700'>@@ -179,8 +184,8 @@
</font> @c
@subheading Build the C Hello World Application
<font color='#880000'>-Use the following command to start the build of the sample hello<span style="background-color: #FF0000"> </span>
-world application:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Use the following command to start the build of the sample hello
+world application:
</font>
@example
cd hello_world_c
<font color='#997700'>@@ -189,7 +194,7 @@
</font>
If the sample application has successfully been built, then the application
<font color='#880000'>-executable is placed in the following directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+executable is placed in the following directory:
</font>
@example
hello_world_c/o-optimize/<filename>.exe
<font color='#997700'>@@ -230,7 +235,7 @@
</font>
@section Build the Sample Application
<font color='#880000'>-Use the following command to start the build of the sample application:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+Use the following command to start the build of the sample application:
</font>
@example
cd tools/hello_world_ada
<font color='#997700'>@@ -246,10 +251,10 @@
</font> for RTEMS and RTEMS itself for the selected host and target
combination was done properly.<span style="background-color: #FF0000"> </span>
<font color='#880000'>-@section Application Executable<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+@section Application Executable
</font>
If the sample application has successfully been build, then the application
<font color='#880000'>-executable is placed in the following directory:<span style="background-color: #FF0000"> </span>
</font><font color='#000088'>+executable is placed in the following directory:
</font>
@example
tools/hello_world_ada/o-optimize/<filename>.exe
</pre>
<p> </p>
<p>--<br />
<small>Generated by <a href="http://www.codewiz.org/projects/index.html#loginfo">Deluxe Loginfo</a> 2.122 by Bernardo Innocenti <bernie@develer.com></small></p>
</body>
</html>