uclibc: release 0.9.28 - upgrading to the release requires a rebuild

IMPORTANT: the uClibc dynamic loader has changed in this release, the
startup and finalisation is changed and this requires applications to
be rebuilt with the new uclibc.  If this is not done the applications
will not work correctly.
 uclibc 0.9.28 contains all the non-thumb (ARM instruction set) patches
OE applied to 0.9.27, this check in includes minimal updates to the
uClibc.config file for each machine architecture, maintainers of
individual architectures may want to make more changes to take advantage
of new features in uClibc.
 It is possible to configure uClibc to offer backward compatibility with
the 0.9.27 dynamic loader, if this is done it will still be necessary to
have both uClibc DLLs (0.9.27 and 0.9.28) on the system for un-recompiled
applications to build.  This commit does *not* do this.
 With this commit the uclibc build is running the 'fix_includes.sh' script
to verify the cross build header files.  This seems to function correctly
however it is possible that some distros may have incorrect header files
(particular if uclibc-initial is built) - in that case it will be
necessary to re-introduce the nokernelheader.patch
If it is necessary to continue to use 0.9.27 in the presence of this
upgrade set PREFERRED_VERSION_uclibc in the DISTRO .conf file.

1 files changed, 22 insertions, 0 deletions

diff --git a/packages/uclibc/uclibc_0.9.28.bb b/packages/uclibc/uclibc_0.9.28.bb
new file mode 100644
index 0000000000..ae3d576e4d
--- /dev/null
+++ b/packages/uclibc/uclibc_0.9.28.bb
@@ -0,0 +1,22 @@
+DEFAULT_PREFERENCE = "1"
+PR = "r0"
+
+include uclibc.inc
+
+# This is the correct KERNEL_SOURCE location, if the uClibc
+# fix_includes.sh script is run (see nokernelheader.patch below)
+# this must be correct.
+KERNEL_SOURCE = "${CROSS_DIR}/${TARGET_SYS}"
+
+SRC_URI += "http://www.uclibc.org/downloads/uClibc-${PV}.tar.bz2"
+
+S = "${WORKDIR}/uClibc-${PV}"
+
+#*** PATCHES ***
+#
+# The nokernelheadercheck patch removes the check on the include
+# files in ${KERNEL_SOURCE}, however this check seems to be
+# functioning correct now so the patch is not included.  It may
+# be necessary to add this for architectures which do not initially
+# have a 'good' set of kernel header files in the cross directory.
+#SRC_URI += "file://nokernelheadercheck.patch;patch=1"