binutils/binutils: simplify gold dependencies

In preparation of adding a new kernel-type, Yann D. came up
with a change in semantic on binutils/gold availability.

So far, it was architectures' responsibility to declare that
they did support binutils/gold or not. It makes much more sense
that binutils/gold declares its own availability depending on
the current architecture; after all, architectures have no way
to know wether gold supports them, while gold does know it.

Signed-off-by:Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971

 diff -durN gcc-4.4.0.orig/gcc/config.gcc gcc-4.4.0/gcc/config.gcc

 --- gcc-4.4.0.orig/gcc/config.gcc	2009-04-17 13:58:41.000000000 +0200

 +++ gcc-4.4.0/gcc/config.gcc	2009-05-27 21:38:31.000000000 +0200

 @@ -2121,7 +2121,7 @@

  	if test x${sh_multilibs} = x ; then

  		case ${target} in

  		sh64-superh-linux* | \

 -		sh[1234]*)	sh_multilibs=${sh_cpu_target} ;;

 +		sh[1234]*)	sh_multilibs=`cd ${srcdir}/config/sh ; echo t-mlib-sh[1-4]* | sed 's:t-mlib-sh:,m:g;s: ::g'` ;;

  		sh64* | sh5*)	sh_multilibs=m5-32media,m5-32media-nofpu,m5-compact,m5-compact-nofpu,m5-64media,m5-64media-nofpu ;;

  		sh-superh-*)	sh_multilibs=m4,m4-single,m4-single-only,m4-nofpu ;;

  		sh*-*-linux*)	sh_multilibs=m1,m3e,m4 ;;