change log for rtems (2011-10-31)

[rtems-vc at rtems.org]

 *joel*:
2011-10-31	Joel Sherrill <joel.sherrill at oarcorp.com>

	PR 1947/doc
	* started/buildrt.t: Make note that native toolset is needed to
	configure and build RTEMS.

M  1.320  doc/ChangeLog
M   1.24  doc/started/buildrt.t

diff -u rtems/doc/ChangeLog:1.319 rtems/doc/ChangeLog:1.320
--- rtems/doc/ChangeLog:1.319	Wed Oct  5 14:59:47 2011
+++ rtems/doc/ChangeLog	Mon Oct 31 08:46:43 2011
@@ -1,3 +1,9 @@
+2011-10-31	Joel Sherrill <joel.sherrill at oarcorp.com>
+
+	PR 1947/doc
+	* started/buildrt.t: Make note that native toolset is needed to
+	configure and build RTEMS.
+
 2011-10-05	Joel Sherrill <joel.sherrill at oarcorp.com>
 		Petr Benes <benesp16 at fel.cvut.cz>
 

diff -u rtems/doc/started/buildrt.t:1.23 rtems/doc/started/buildrt.t:1.24
--- rtems/doc/started/buildrt.t:1.23	Sun Jan  2 10:12:02 2011
+++ rtems/doc/started/buildrt.t	Mon Oct 31 08:46:43 2011
@@ -156,6 +156,12 @@
 be enabled.  Thus the RTEMS configuration for a GNAT/RTEMS environment
 MUST include the @code{--enable-posix --enable-networking} flag.
 
+ at 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



--

Generated by Deluxe Loginfo [http://www.codewiz.org/projects/index.html#loginfo] 2.122 by Bernardo Innocenti <bernie at develer.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/vc/attachments/20111031/538e0f9f/attachment-0001.html>