diff options
| author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2011-10-31 13:46:43 +0000 |
|---|---|---|
| committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2011-10-31 13:46:43 +0000 |
| commit | b009f48110357ce3ccf01461e181954920f59985 (patch) | |
| tree | 94f90b65d0cf7ade699d21dbb125a8e5349328ad /doc/started/buildrt.t | |
| parent | New. (diff) | |
| download | rtems-b009f48110357ce3ccf01461e181954920f59985.tar.bz2 | |
2011-10-31 Joel Sherrill <joel.sherrill@oarcorp.com>
PR 1947/doc
* started/buildrt.t: Make note that native toolset is needed to
configure and build RTEMS.
Diffstat (limited to '')
| -rw-r--r-- | doc/started/buildrt.t | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t index a18f0d9847..f7d8cff3a6 100644 --- a/doc/started/buildrt.t +++ b/doc/started/buildrt.t @@ -156,6 +156,12 @@ disabled. Your application does not have to use networking but it must be enabled. Thus the RTEMS configuration for a GNAT/RTEMS environment MUST include the @code{--enable-posix --enable-networking} flag. +@b{NOTE}: Building RTEMS requires that a few support programs be compiled +natively. This means there must be a native toolchain installed on your +development host. You will need to have a native compiler such as @i{gcc} +or @i{cc} in your execution path. If you cannot compile, link and execute +a native hello world program, then you will be unable to build RTEMS. + The following shows the command sequence required to configure, compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP, and C++ support disabled. RTEMS will be built to target |