1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/patches/binutils/2.22/120-sh-conf.patch	Wed Dec 14 19:57:47 2011 +0100
     1.3 @@ -0,0 +1,31 @@
     1.4 +r10231 | lethal | 2005-05-02 09:58:00 -0400 (Mon, 02 May 2005) | 13 lines
     1.5 +
     1.6 +Likewise, binutils has no idea about any of these new targets either, so we 
     1.7 +fix that up too.. now we're able to actually build a real toolchain for 
     1.8 +sh2a_nofpu- and other more ineptly named toolchains (and yes, there are more 
     1.9 +inept targets than that one, really. Go look, I promise).
    1.10 +
    1.11 +diff -durN binutils-2.22.orig/configure binutils-2.22/configure
    1.12 +--- binutils-2.22.orig/configure	2011-08-14 14:28:15.000000000 +0200
    1.13 ++++ binutils-2.22/configure	2011-12-14 19:49:40.284777434 +0100
    1.14 +@@ -3570,7 +3570,7 @@
    1.15 +   mips*-*-*)
    1.16 +     noconfigdirs="$noconfigdirs gprof"
    1.17 +     ;;
    1.18 +-  sh-*-* | sh64-*-*)
    1.19 ++  sh*-*-* | sh64-*-*)
    1.20 +     case "${target}" in
    1.21 +       sh*-*-elf)
    1.22 +          ;;
    1.23 +diff -durN binutils-2.22.orig/configure.ac binutils-2.22/configure.ac
    1.24 +--- binutils-2.22.orig/configure.ac	2011-11-21 12:58:27.000000000 +0100
    1.25 ++++ binutils-2.22/configure.ac	2011-12-14 19:49:40.316777436 +0100
    1.26 +@@ -1006,7 +1006,7 @@
    1.27 +   mips*-*-*)
    1.28 +     noconfigdirs="$noconfigdirs gprof"
    1.29 +     ;;
    1.30 +-  sh-*-* | sh64-*-*)
    1.31 ++  sh*-*-* | sh64-*-*)
    1.32 +     case "${target}" in
    1.33 +       sh*-*-elf)
    1.34 +          ;;