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	2006-12-21 23:13:33.000000000 +0100

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

@@ -1045,6 +1045,15 @@

 		/*

 		 * Note: we only deal with only 32-bit CPUs here.

 		 */

+

+		if (!(tcp->flags & TCB_INSYSCALL) &&

+		    (tcp->flags & TCB_WAITEXECVE)) {

+			/* caught a fake syscall from the execve's exit */

+			tcp->flags &= ~TCB_WAITEXECVE;

+			return 0;

+		}

+ 

+

 		if (regs.ARM_cpsr & 0x20) {

 			/*

 			 * Get the Thumb-mode system call number