Hi,

Marian Aldenhövel wrote:
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!

Yes, I know. We already patched quite some normal packages to build
with gcc-4.3 (that is no major one is pending as far as I know),
The biggest thing left for GCC-4.3 adaption is rediffing this uclibc
support patches.

(Maybe it even already builds with this wchar chunk removed, I
 have not yet tried.)

General GCC-4.3 support felt ready (well, yeah I already have 2
of our local systems running on GCC-4.3 builds - that is my
workstation and laptop :-) and lingering on my local working
copies for over 2 months (since I wrote the German Linux Magazin
article :-). I wanted to have it finally flushed and in the hands
of others.

Patches for the uClibC adaption are welcome, I might find the
time to fix it soon otherwise.

PS: trunk is for such changes, just a reminder: stable production
systems should be based on the stable branches:

  http://svn.exactcode.de/t2/branches/

trunk will become the 8.0 branch sometime this autumn.

Stable branches only receive fixes, security and minor
updates (like gcc-4.2.3 -> gcc-4.2.4).

Yours,

--
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2

Reply via email to