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

Original patch from: ../4.3.2/170-libiberty-pic.patch

-= BEGIN original header =-

Original patch from gentoo: gentoo/src/patchsets/gcc/4.3.1/gentoo/51_all_gcc-3.4-libiberty-pic.patch

-= END original header =-

diff -durN gcc-4.3.3.orig/libiberty/Makefile.in gcc-4.3.3/libiberty/Makefile.in

--- gcc-4.3.3.orig/libiberty/Makefile.in	2007-07-25 08:26:45.000000000 +0200

+++ gcc-4.3.3/libiberty/Makefile.in	2009-01-27 22:19:30.000000000 +0100

@@ -225,6 +225,7 @@

 	  $(AR) $(AR_FLAGS) $(TARGETLIB) \

 	    $(REQUIRED_OFILES) $(EXTRA_OFILES) $(LIBOBJS); \

 	  $(RANLIB) $(TARGETLIB); \

+	  cp $(TARGETLIB) ../ ; \

 	  cd ..; \

 	else true; fi