patches/gcc/3.3.4/gcc-3.3.4-libstdcxx-sh.patch
changeset 330 447b203edc2e
parent 329 419d959441ed
child 331 0c05f9ea3254
     1.1 --- a/patches/gcc/3.3.4/gcc-3.3.4-libstdcxx-sh.patch	Tue Aug 14 19:32:22 2007 +0000
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,38 +0,0 @@
     1.4 -Date: Tue, 06 Jul 2004 10:40:57 +0900 (JST)
     1.5 -Message-Id: <20040706.104057.48529182.kkojima@rr.iij4u.or.jp>
     1.6 -To: dank@kegel.com
     1.7 -Cc: linux-sh@m17n.org, linuxsh-dev@lists.sourceforge.net
     1.8 -Subject: gcc-3.4.1 (Was: The current kernel for a Jornada 680 SH3)
     1.9 -From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
    1.10 -In-Reply-To: <20040529.175014.48668611.kkojima@rr.iij4u.or.jp>
    1.11 -References: <20040528.125858.50336810.kkojima@rr.iij4u.or.jp>
    1.12 -	<40B8205D.8030200@kegel.com>
    1.13 -	<20040529.175014.48668611.kkojima@rr.iij4u.or.jp>
    1.14 -
    1.15 -Hi,
    1.16 -
    1.17 -...
    1.18 -
    1.19 -BTW, gcc-3.3.4 was also released and there is a bad news :-(  Someone
    1.20 -reverted wrongly a configury patch against libstdc++ for sh-linux at
    1.21 -the last moment.  We have to regenerate gcc-3.3.4/libstdc++-v3/configure
    1.22 -with autoconf 2.13 or apply the one-line patch below manually:
    1.23 -
    1.24 ---- gcc-3.3.4-orig/libstdc++-v3/configure	2004-06-01 09:45:44.000000000 +0900
    1.25 -+++ gcc-3.3.4/libstdc++-v3/configure	2004-06-29 22:38:05.000000000 +0900
    1.26 -@@ -2009,7 +2009,7 @@ irix5* | irix6*)
    1.27 - # This must be Linux ELF.
    1.28 - linux-gnu*)
    1.29 -   case $host_cpu in
    1.30 --  alpha* | hppa* | i*86 | powerpc* | sparc* | ia64* )
    1.31 -+  alpha* | hppa* | i*86 | powerpc* | sparc* | ia64* | sh* )
    1.32 -     lt_cv_deplibs_check_method=pass_all ;;
    1.33 -   *)
    1.34 -     # glibc up to 2.1.1 does not perform some relocations on ARM
    1.35 -
    1.36 -
    1.37 -Regards,
    1.38 -	kaz
    1.39 -
    1.40 -
    1.41 -