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

 --- strace-4.5.15.orig/syscall.c	2007-07-14 19:21:44.000000000 +0200

 +++ strace-4.5.15/syscall.c	2007-07-14 19:22:49.000000000 +0200

 @@ -125,6 +125,18 @@

  #define TP TRACE_PROCESS

  #define TS TRACE_SIGNAL

 +#ifndef HAVE_STATFS64

 +/*

 + * Ugly hacks for systems that do not have LFS

 + */

 +

 +#define sys_truncate64  sys_truncate

 +#define sys_ftruncate64 sys_ftruncate

 +#define sys_getdents64  sys_getdents

 +#define sys_statfs64    sys_statfs

 +#define sys_fstatfs64   sys_fstatfs

 +#endif

 +

  static const struct sysent sysent0[] = {

  #include "syscallent.h"

  };