Prep for 6.23 releasenuttx-6.23

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5313 42af7a65-404d-4744-a932-0658087f49c3

6 files changed, 156 insertions, 13 deletions

diff --git a/misc/buildroot/ChangeLog b/misc/buildroot/ChangeLog
index cdbef5da1..6b09b8b94 100644
--- a/misc/buildroot/ChangeLog
+++ b/misc/buildroot/ChangeLog
@@ -101,7 +101,7 @@ buildroot-1.10 2011-05-06 <gnutt@nuttx.org>
 	* configs/arm920t-eabi-defconfig-4.5.2 - Add a configuration to build a
 	  GCC 4.5.2 EABI ARM toolchain for the ARM920t.
 
-buildroot-1.11 2011-xx-xx <gnutt@nuttx.org>
+buildroot-1.11 2011-11-05 <gnutt@nuttx.org>
 
 	* configs/avr-defconfig-4.3.3 - Added --enable-long-long as a GCC
 	  option.
@@ -127,3 +127,4 @@ buildroot-1.11 2011-xx-xx <gnutt@nuttx.org>
 	  past the end of allocated memory.  Partial restoration of R_ARM_REL32
 	  logic.  There are lots of issues that I still do not understand here.
 
+buildroot-1.12 2011-xx-xx <gnutt@nuttx.org>
diff --git a/misc/buildroot/ReleaseNotes b/misc/buildroot/ReleaseNotes
index 889b97073..266354e63 100644
--- a/misc/buildroot/ReleaseNotes
+++ b/misc/buildroot/ReleaseNotes
@@ -1,5 +1,8 @@
-ReleaseNotes v0.1.10:
-^^^^^^^^^^^^^^^^^^^^^
+ReleaseNotes v0.1.11
+====================
+
+Supported Toolchains
+--------------------
 
 This is a highly hacked up version of the buildroot (see
 http://buildroot.uclibc.org/). It has been hacked so that it
@@ -13,7 +16,7 @@ can be used to build the following NuttX-compatible toolchains:
     NXFLAT toolchain for use with the ARM7 and ARM9.
 
   o arm-elf ARM Cortex-M3 (thumb2) toolchain needed for use with
-    the Luminary LM3Sxxx, NXP 17xxxx, Atmel SAM3u, and STMicor
+    the Luminary LM3Sxxx, NXP 17xxxx, Atmel SAM3u, and STMicro
     STM32 ports provided with the NuttX releases.
 
     NXFLAT toolchain for use with the ARM Cortex-M3.
@@ -26,11 +29,11 @@ can be used to build the following NuttX-compatible toolchains:
 
   o i486-elf toochain.  Why would you want such a thing?  On Linux, of 
     course, such a thing is not needed because you can use the installed GCC 
-	to build i486 ELF binaries.  But that will not work under Cygwin!  The
-	Cygwin toolchain (and probably MinGW), build DOS MZ format executables
-	(i.e., .exe files).  That is probably not usable for most NuttX targets.
-	Instead, you should use this i486-elf-gcc to generate true ELF binaries
-	under Cygwin.
+    to build i486 ELF binaries.  But that will not work under Cygwin!  The
+    Cygwin toolchain (and probably MinGW), build DOS MZ format executables
+    (i.e., .exe files).  That is probably not usable for most NuttX targets.
+    Instead, you should use this i486-elf-gcc to generate true ELF binaries
+    under Cygwin.
 
   o bfin-elf toolchain not currently used in any NuttX
     configuration).
@@ -59,8 +62,9 @@ Supported tool versions include:
   o gcc-4.2.4 + binutils-2.19
   o gcc-4.3.3 + binutils-2.19.1
   o gcc-4.5.2 + binutils-2.21
+  o gcc-4.6.3 + binutils-2.22
 
-See the ChangeLog of features/architectures added in v0.1.9.
+See the ChangeLog of features/architectures added in v0.1.11.
 
 Installation instructions:
 
@@ -79,11 +83,30 @@ then:
 
 And set the "Path to the NuttX root directory" appropriately.
 
+Version Information
+-------------------
+
+buildroot release 1.11 corresponds to SVN revision r5313.
+
+Note that all SVN information has been stripped from the tarball.  If you
+need the SVN configuration, you should check out directly from SVN.  Revision
+r5313 should equivalent to release 1.0 of NuttX buildroot:
+
+    svn checkout -r5313 svn://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
+
+Or
+
+    svn checkout -r5313 http://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
+
 NXFLAT Toolchain Build
+----------------------
 
 You can select to build the NXFLAT toolchain with GCC by selecting
 the NXFLAT toolchin during the configuration process(you can also
 select omit building GCC with and only build the NXFLAT toolchain
 for use with your own GCC toolchain.
 
-NFFLAT is only available for ARM and Cortex-M3 architectures.
+NOTES:
+  - NFFLAT is only available for ARM and Cortex-M3 architectures.
+  - The GCC 4.6.3 will not work with NXFLAT.  See "Toolchain Compatibility
+    Problem" at http://www.nuttx.org/doku.php?id=wiki:vfs:nxflat for details.
diff --git a/misc/uClibc++/ChangeLog.txt b/misc/uClibc++/ChangeLog.txt
new file mode 100644
index 000000000..8c680392c
--- /dev/null
+++ b/misc/uClibc++/ChangeLog.txt
@@ -0,0 +1,7 @@
+uClibc++-1.0 2011-11-05 <gnutt@nuttx.org>
+
+    * The initial release of the uClibc++ implementation of the standard
+      C++ library for NuttX.  This package was contributed ay Qiang Yu and
+      David for the RGMP team.
+
+uClibc++-1.1 2011-xx-xx <gnutt@nuttx.org>
diff --git a/misc/uClibc++/README.txt b/misc/uClibc++/README.txt
index 751f23587..8d306fd5a 100755
--- a/misc/uClibc++/README.txt
+++ b/misc/uClibc++/README.txt
@@ -48,7 +48,7 @@ Dependencies
   libraries.
 2. NuttX C++ support
 3. Math library
-4. TLS support is currenly provided only under RGMP
+4. TLS support is currently provided only under RGMP
 
 NuttX Configuration File Changes
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -64,7 +64,7 @@ If you choose to use the NuttX math library, that is enabled as follows:
   CONFIG_LIBM=y
 
 The math libraries depend on the float.h header file that is normally
-provided by your tooltchain.  A dummy (and probably wrong) fload.h file
+provided by your toolchain.  A dummy (and probably wrong) fload.h file
 can be installed by setting:
 
   CONFIG_ARCH_FLOAT_H=y
diff --git a/misc/uClibc++/ReleaseNotes.txt b/misc/uClibc++/ReleaseNotes.txt
new file mode 100644
index 000000000..63e4b7583
--- /dev/null
+++ b/misc/uClibc++/ReleaseNotes.txt
@@ -0,0 +1,32 @@
+uClibc++-1.0
+============
+
+This package is a version of the uClibc++ C++ library customized to work
+with NuttX.  This code originates from http://cxx.uclibc.org/ and has been
+adapted for NuttX by the RGMP team (http://rgmp.sourceforge.net/wiki/index.php/Main_Page).
+Thanks go to Qiang Yu and David.
+
+uClibc++ is released as a separate packet rather than being integrated with
+the core NuttX source code. This separation is due to differences in
+licensing betweein uClibc++ and NuttX:  NuttX is licensed under the
+permissive modified BSD License; uClibc, on the other hand, is licensed
+under the stricter GNU LGPL Version 3 license.
+
+A simple installation script is provided at misc/uClibc++/install.sh that
+can be used to install the uClibc++ components into the NuttX source tree.
+See the README file in the top-level uClibc++ directory for instructions on
+using the installation script.  If you wish to use uClibc++ with NuttX, you
+will be required to comply with the licensing requires of the GNU LGPL
+Version 3 license.
+
+uClibc++ release 1.0 corresponds to SVN revision r5313.
+
+Note that all SVN information has been stripped from the tarball.  If you
+need the SVN configuration, you should check out directly from SVN.  Revision
+r5313 should equivalent to release 1.0 of NuttX uClibc++:
+
+    svn checkout -r5313 svn://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
+
+Or
+
+    svn checkout -r5313 http://svn.code.sf.net/p/nuttx/code/trunk nuttx-code
diff --git a/misc/uClibc++/zipme.sh b/misc/uClibc++/zipme.sh
new file mode 100755
index 000000000..d20a78463
--- /dev/null
+++ b/misc/uClibc++/zipme.sh
@@ -0,0 +1,80 @@
+#!/bin/sh
+#set -x
+
+WD=`pwd`
+VERSION=$1
+
+TAR="tar cvf"
+ZIP=gzip
+
+# Make sure we know what is going on
+
+if [ -z ${VERSION} ] ; then
+   echo "You must supply a version like xx.yy.zz as a parameter"
+   exit 1;
+fi
+
+# Find the directory we were executed from and where we expect to
+# see the directory to tar up
+
+MYNAME=`basename $0`
+UCLIBCXX_DIR=uClibc++-${VERSION}
+
+if [ -x ${WD}/${MYNAME} ] ; then
+   MISCDIR=`dirname ${WD}`
+else
+   if [ -x ${WD}/${UCLIBCXX_DIR}/${MYNAME} ] ; then
+     MISCDIR=${WD}
+   else
+     echo "You must cd into the misc/ or misc/${UCLIBCXX_DIR}/ directory to execute this script."
+     exit 1
+   fi
+fi
+
+# Get the path to the parent directory
+
+SUBDIR=`basename ${MISCDIR}`/${UCLIBCXX_DIR}
+PARENT=`dirname ${MISCDIR}`
+
+# The name of the directory must match the version number
+
+cd ${PARENT} || \
+   { echo "Failed to cd to ${PARENT}" ; exit 1 ; }
+
+if [ ! -d ${SUBDIR} ] ; then
+   echo "${PARENT}/${SUBDIR} does not exist!"
+   exit 1
+fi
+
+TAR_NAME=${UCLIBCXX_DIR}.tar
+ZIP_NAME=${TAR_NAME}.gz
+
+# Prepare the uClibc++ directory -- Remove editor garbage
+
+find ${SUBDIR} -name '*~' -exec rm -f '{}' ';' || \
+      { echo "Removal of emacs garbage failed!" ; exit 1 ; }
+find ${SUBDIR} -name '*.swp' -exec rm -f '{}' ';' || \
+      { echo "Removal of VI garbage failed!" ; exit 1 ; }
+
+# Remove any previous tarballs
+
+if [ -f ${TAR_NAME} ] ; then
+   echo "Removing ${TAR_NAME}"
+   rm -f ${TAR_NAME} || \
+      { echo "rm ${TAR_NAME} failed!" ; exit 1 ; }
+fi
+
+if [ -f ${ZIP_NAME} ] ; then
+   echo "Removing ${ZIP_NAME}"
+   rm -f ${ZIP_NAME} || \
+      { echo "rm ${ZIP_NAME} failed!" ; exit 1 ; }
+fi
+
+# Then zip it
+
+${TAR} ${TAR_NAME} ${SUBDIR} || \
+      { echo "tar of ${TAR_NAME} failed!" ; exit 1 ; }
+${ZIP} ${TAR_NAME} || \
+      { echo "zip of ${TAR_NAME} failed!" ; exit 1 ; }
+
+cd ${WD}