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/net.c strace-4.5.15/net.c

--- strace-4.5.15.orig/net.c	2006-12-13 20:57:23.000000000 +0100

+++ strace-4.5.15/net.c	2007-07-14 19:29:36.000000000 +0200

@@ -800,8 +800,12 @@

 #ifdef SOL_PACKET

 static const struct xlat sockpacketoptions[] = {

+#if defined(PACKET_ADD_MEMBERSHIP)

 	{ PACKET_ADD_MEMBERSHIP,	"PACKET_ADD_MEMBERSHIP"	},

+#endif

+#if defined(PACKET_DROP_MEMBERSHIP)

 	{ PACKET_DROP_MEMBERSHIP,	"PACKET_DROP_MEMBERSHIP"},

+#endif

 #if defined(PACKET_RECV_OUTPUT)

 	{ PACKET_RECV_OUTPUT,		"PACKET_RECV_OUTPUT"	},

 #endif