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 -dur strace-4.5.15.orig/signal.c strace-4.5.15/signal.c

--- strace-4.5.15.orig/signal.c	2007-01-11 23:08:38.000000000 +0100

+++ strace-4.5.15/signal.c	2007-07-14 19:24:43.000000000 +0200

@@ -1440,7 +1440,7 @@

 	  	tcp->u_rval = tcp->u_error = 0;

 		if(tcp->u_arg[0] == 0)

 		  	return 0;

-		tcp->auxstr = sprintsigmask("mask now ", tcp->u_arg[1]);

+		tcp->auxstr = sprintsigmask("mask now ", tcp->u_arg[1], 0);

 		return RVAL_NONE | RVAL_STR;

 	}

 	return 0;