only use gold-specific flags for the target linker

only use gold-specific flags for the target linker

The host linker might not be gold if linux_use_gold_binary==0,
eg where we have a cross toolchain with gold and we want to use
that instead of third_party/gold/gold64.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=212823

[Mostyn Bramley-Moore, 2013-07-19 10:45:29]

PTAL...

[Sam Clegg, 2013-07-19 18:52:39]

On 2013/07/19 10:45:29, Mostyn Bramley-Moore wrote:
> PTAL...

So this means we never get multi-threaded linking for host binary?  Is that
desirable/acceptable?

[Mostyn Bramley-Moore, 2013-07-19 23:16:57]

> So this means we never get multi-threaded linking for host binary?  Is that
> desirable/acceptable?

I strongly suspect that the host binary is only used for a tiny percentage of
the overall build time.  ie desirable: not really, acceptable: yes probably. 
The only (linux) host targets I have noticed so far are yasm and protobuf.  

I'm happy to gather some statistics if you like, but I'd be very surprised to be
wrong.  Alternatively we could split this into two gyp settings for the host and
target.

[Sam Clegg, 2013-07-20 00:41:57]

ok, lgtm.

[commit-bot: I haz the power, 2013-07-20 19:09:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mostynb@opera.com/19541006/1

[commit-bot: I haz the power, 2013-07-20 19:41:50]

Step "update" is always a major failure.
Look at the try server FAQ for more details.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...

[commit-bot: I haz the power, 2013-07-21 13:16:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mostynb@opera.com/19541006/1

[commit-bot: I haz the power, 2013-07-21 14:03:35]

Change committed as 212823