patches/gcc/4.4.4/230-superh-default-multilib.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1948 d341be24dc68
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@1948
     1
diff -durN gcc-4.4.4.orig/gcc/config.gcc gcc-4.4.4/gcc/config.gcc
yann@1948
     2
--- gcc-4.4.4.orig/gcc/config.gcc	2010-02-18 05:24:04.000000000 +0100
yann@1948
     3
+++ gcc-4.4.4/gcc/config.gcc	2010-05-16 19:13:30.000000000 +0200
yann@1948
     4
@@ -2128,7 +2128,7 @@
yann@1948
     5
 	if test x${sh_multilibs} = x ; then
yann@1948
     6
 		case ${target} in
yann@1948
     7
 		sh64-superh-linux* | \
yann@1948
     8
-		sh[1234]*)	sh_multilibs=${sh_cpu_target} ;;
yann@1948
     9
+		sh[1234]*)	sh_multilibs=`cd ${srcdir}/config/sh ; echo t-mlib-sh[1-4]* | sed 's:t-mlib-sh:,m:g;s: ::g'` ;;
yann@1948
    10
 		sh64* | sh5*)	sh_multilibs=m5-32media,m5-32media-nofpu,m5-compact,m5-compact-nofpu,m5-64media,m5-64media-nofpu ;;
yann@1948
    11
 		sh-superh-*)	sh_multilibs=m4,m4-single,m4-single-only,m4-nofpu ;;
yann@1948
    12
 		sh*-*-linux*)	sh_multilibs=m1,m3e,m4 ;;