summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Johns <chrisj@rtems.org>2018-02-05 03:35:51 (UTC)
committerChris Johns <chrisj@rtems.org>2018-02-05 03:35:51 (UTC)
commit0319856bca6a0655e453a5faa20344d97ff78c64 (patch)
tree8d728f94ee0f8e35350667ca88205688fdd89b15
parentba143e0b300bfde55c328ca5152bbc05d4386f07 (diff)
downloadrtems-docs-0319856bca6a0655e453a5faa20344d97ff78c64.tar.bz2
user: Fix typos in the User Manual.
Close #3004
-rw-r--r--user/installation/releases.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/user/installation/releases.rst b/user/installation/releases.rst
index 92fce78..0d5150c 100644
--- a/user/installation/releases.rst
+++ b/user/installation/releases.rst
@@ -53,8 +53,8 @@ shosted here. It has excellent internet access and performance.
By default all the BSPs for an architecture are built. If you only wish to
have a specific BSP built you can specify the BSP list by providing to the
- RSB the option ``--with-rtemsbsp``. For example to build two BSPs for the
- SPARC architecture you can supply ``--with-rtemsbsp="erc32 sis"``. This can
+ RSB the option ``--enable-rtemsbsp``. For example to build two BSPs for the
+ SPARC architecture you can supply ``--enable-rtemsbsp="erc32 sis"``. This can
speed the build time up for some architectures that have a lot of BSPs.
Once you have built the tools and kernel you can move to the Packages section
@@ -112,7 +112,7 @@ you have unpacked the tar file:
$ tar Jxf rtems-source-builder-4.11.0.tar.xz
$ mv rtems-source-builder-4.11.0 4.110
- $ cd 4.11.0
+ $ cd 4.11.0/rtems
Build a tool chain for the SPARC architecure. We are using the SPARC
architecture in our example because GDB has a good simulator that lets us run