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 -ru ltrace-0.5.3.org/configure ltrace-0.5.3/configure

--- ltrace-0.5.3.org/configure	2011-08-21 18:55:15.000000000 +0200

+++ ltrace-0.5.3/configure	2011-08-21 18:54:46.000000000 +0200

@@ -15,8 +15,12 @@

 echo $PACKAGE_VERSION

 echo -n "checking HOST_OS... "

-HOST_OS=$( uname -s )

-if [ "$HOST_OS" = "Linux" ]

+if [ -z "$HOST_OS" ] ; then

+  HOST_OS=$( uname -s )

+else

+  echo -n "using preset: "

+fi

+if [ "$HOST_OS" = "Linux" -o "$HOST_OS" = "linux" ]

 then

   HOST_OS="linux-gnu"

 fi