uClibc patches

This is a multi-part message in MIME format.

Hi,

I am afraid the GCC-upgrade from 4.2.4 to 4.3.1 in rev 29691 broke
uclibc-based builds.

There seem to be some gcc-related patches in package/base/uclibc that
do no longer apply cleanly to the new version if I am interpreting
the output correctly:

>Apply patch 
/home/kbox/t2/package/base/uclibc/patches/gcc-200-uclibc-locale.patch ...
>patching file libstdc++-v3/acinclude.m4
>Hunk #1 succeeded at 1349 (offset 15 lines).
>Hunk #2 succeeded at 1370 with fuzz 2 (offset -15 lines).
>Hunk #3 succeeded at 1544 (offset 13 lines).
>patching file libstdc++-v3/config/locale/uclibc/c++locale_internal.h
>patching file libstdc++-v3/config/locale/uclibc/c_locale.cc
>patching file libstdc++-v3/config/locale/uclibc/c_locale.h
>patching file libstdc++-v3/config/locale/uclibc/codecvt_members.cc
>patching file libstdc++-v3/config/locale/uclibc/collate_members.cc
>patching file libstdc++-v3/config/locale/uclibc/ctype_members.cc
>patching file libstdc++-v3/config/locale/uclibc/messages_members.cc
>patching file libstdc++-v3/config/locale/uclibc/messages_members.h
>patching file libstdc++-v3/config/locale/uclibc/monetary_members.cc
>patching file libstdc++-v3/config/locale/uclibc/numeric_members.cc
>patching file libstdc++-v3/config/locale/uclibc/time_members.cc
>patching file libstdc++-v3/config/locale/uclibc/time_members.h
>patching file libstdc++-v3/configure
>Hunk #1 succeeded at 14001 (offset 8237 lines).
>Hunk #2 succeeded at 14034 with fuzz 2 (offset 8245 lines).
>Hunk #3 succeeded at 14425 (offset 8403 lines).
>patching file libstdc++-v3/include/c_compatibility/wchar.h
>Hunk #1 succeeded at 106 (offset 5 lines).
>can't find file to patch at input line 2781
>Perhaps you used the wrong -p or --strip option?
>The text leading up to this was:
>--------------------------
>|--- gcc/libstdc++-v3/include/c_std/std_cwchar.h
>|+++ gcc/libstdc++-v3/include/c_std/std_cwchar.h
>--------------------------
>No file to patch.  Skipping patch.
>1 out of 1 hunk ignored
>Due to previous errors, no 0-gcc.log file!

Ciao, MM
--
Marian Aldenhövel, Rosenhain 23, 53123 Bonn
http://www.marian-aldenhoevel.de
"I ran some quick calculations on it. He's about 80% on the right
 track.  That leaves him only 20% dead when he crashes." Bob C