Update for release

Changelog

@@ -1,3 +1,31 @@
+0.9.30	30 June 2003
+
+See Changelog.full for the complete list of who did what. 
+
+Note:
+    This release remains binary compatible with 0.9.18 and 0.9.19.
+
+
+Release highlights:
+    o Some ldd, profiling, and gcc wrapper updates 
+    o Updated to support and compile with gcc 3.3
+    o Several needed mips updates
+    o Building under cygwin should now work...
+    o Prevent non-PIC code getting into PIC libs
+    o Added mmap64 support
+    o mmu-less systems now get a 16k default thread stack size
+	which is much more sane than the old 2 MB default...
+    o Implemented syscall() for powerpc
+    o Optionally struct tm extension support
+    o Lots of other sundry little fixes and cleanups.
+    o Prevent buffer overflows in the passwd and group functions.
+
+ -Erik
+
+
+
+
+
 0.9.19	3 March 2003
 
 See Changelog.full for the complete list of who did what. 

TODO

@@ -1,24 +1,22 @@
-
 Erik's TODO list for the next release:
 
-    1) Fix profiling support
-    2) Implement getgrgid_r and getgrnam_r, per SuSv3 
-    3) When options are disabled, also disable them in the
+    *) Implement getgrgid_r and getgrnam_r, per SuSv3 
+    *) When options are disabled, also disable them in the
 	include files as well.
-    4) Make all configured out symbols optionally add a linker warning saying
+    *) Make all configured out symbols optionally add a linker warning saying
 	"Hey!  You are trying to use a function that you have configured out.  
 	If you really want to use this function, enable CONFIG_FOO and rebuild
 	uClibc".
-    5) Make all small objects (>~50 bytes) into either inlines or
+    *) Make all small objects (>~50 bytes) into either inlines or
 	into a static library
-    6) Rework all code that fails conformance tests
-    7) Document all differences between the feature set of uClibc 
+    *) Document all differences between the feature set of uClibc 
 	and glibc.
-    8) Add missing syscall() function to ports that are still 
-	missing it.  (x86 and arm are finished so far).
-    9) Fix regex so it isn't so stinking big
-    10) Fix glob so it isn't so stinking big
-
+    *) Fix regex so it isn't so stinking big
+    *) Fix glob so it isn't so stinking big
+    *)  Fix the dlopen() bug with handling of symbols that are already
+	resolved.  Seems if it is already resolved it ignores them rather than
+	resolving the new symbol and overriding.
+    *) Adapt uClibc to use Linux 2.5.x pthreads
 
 -----------------------------------------------------------------------------
 Manuel's todo:

docs/uclibc.org/index.html

@@ -111,6 +111,69 @@ you might want to search the mailing list archives...
 
 <ul>
 
+    <p>
+    <li> <b>30 June 2003, uClibc 0.9.20 Released</b>
+    <br>
+
+    CodePoet Consulting is pleased to announce the immediate availability of
+    uClibc 0.9.20.  This is primarily a bug-fix release.  This release remains
+    binary compatible with 0.9.18 and 0.9.19, so you don't have to recompile
+    everything if you don't really feel like it.
+    <p>
+
+    This release has many small improvements.  At this point, most applications
+    that compile and work with glibc will also compile and run with uClibc.
+    Perl and Python even pass all the tests in their test suites.  
+    <p>
+
+    There is currently one notable exception.  Applications with use dlopen()
+    to load libraries that themselves depend on other libraries, may have weak
+    symbols within those depended-upon libraries resolved incorrectly.  This
+    problem is currently being worked on.  Other than that, everything seems to
+    be working.  And everything seems to now be working as expected....
+
+    <p>
+    As usual, the 
+    <a href="http://www.uclibc.org/downloads/Changelog">Changelog</a>, 
+    <a href="http://www.uclibc.org/downloads/Changelog.full">detailed changelog</a>, 
+    and <a href="http://www.uclibc.org/downloads/uClibc-0.9.19.tar.bz2">source code for this release</a> 
+    are available <a href="http://www.uclibc.org/downloads/">here</a>.
+    <p>
+    
+
+    <p>
+    <li> <b>30 June March 2003, dev systems updated to uClibc 0.9.20</b>
+    <br>
+
+    The uClibc development systems for
+    <a href="http://www.uclibc.org/downloads/root_fs-i386.bz2">i386</a>,
+    <a href="http://www.uclibc.org/downloads/root_fs-powerpc.bz2">powerpc</a>,
+    <a href="http://www.uclibc.org/downloads/root_fs-arm.bz2">arm</a>,
+    <a href="http://www.uclibc.org/downloads/root_fs-mipsel.bz2">mips</a>,
+    have been updated to uClibc 0.9.20.  Several problems have been fixed up,
+    gcc has been updated to version 3.3, and Perl 5.8.0 is now included.
+    <p>
+
+    This is a 150 MB ext2 filesystem that runs natively on the specified
+    architecture.  It contains all the development software you need to build
+    your own uClibc applications, including bash, coreutils, findutils,
+    diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace,
+    make, gcc, g++,  autoconf, automake, ncurses, zlib, openssl, openssh perl, 
+    and more.   And of course, everything is dynamically linked against uClibc.  By
+    using a uClibc only system, you can avoid all the painful
+    cross-configuration problems that have made using uClibc somewhat painful
+    in the past.  If you want to quickly get started with testing or using
+    uClibc you should give these images a try.  You can loop mount and then
+    chroot into them, you can boot into them using user-mode Linux, and you can
+    even 'dd' them to a spare partition and use resize2fs to make them fill the
+    drive.  Whatever works for you.
+
+    <p> If you would like to build your own custom uClibc system, you can
+	use <a href="/cgi-bin/cvsweb/buildroot/">buildroot</a>, which is
+	how the uClibc development systems were created.
+    <p>
+
+
     <p>
     <li> <b>6 March 2003, development system updates</b>
     <br>