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

 Index: ltrace-0.5.3/configure

 ===================================================================

 --- ltrace-0.5.3/configure

 +++ ltrace-0.5.3/configure

 @@ -78,7 +78,10 @@ fi

  rm -f conftest.c a.out

  CFLAGS='-g -O2'

 -LIBS='-lelf -lsupc++ -liberty '

 +LIBS='-lelf'

 +[ -n "$HAVE_LIBSUPC__" ] && LIBS="$LIBS -lsupc++"

 +[ -n "$HAVE_LIBIBERTY" ] && LIBS="$LIBS -liberty"

 +

  INSTALL='install -c'

  iquote='-iquote '

  iquoteend=''