Allow goma to work w/ NaCl toolchains in GN build.

Allow goma to work w/ NaCl toolchains in GN build.

This change allows the default logic for goma to work
for NaCl (which appears to work fine, at least in local
testing, and it looks like build_nexe.py supports goma
these days as well).

Let's enable this and see what happens; if this doesn't
work, then we need to figure out a way to set a
per-toolchain limit on concurrent compiles like there
is for concurrent_links , and figure out how to make
that get set appropriately for nacl differently from
cc.

R=mcgrathr@chromium.org
BUG=555123
Committed: https://crrev.com/d434bf3f1b28416a88604325372a01b908c099c0
Cr-Commit-Position: refs/heads/master@{#359595}

[Dirk Pranke, 2015-11-12 23:24:07]

Description was changed from

==========
Allow goma to work w/ NaCl toolchains in GN build.

This change allows the default logic for goma to work
for NaCl (which appears to work fine, at least in local
testing, and it looks like build_nexe.py supports goma
these days as well).

Let's enable this and see what happens; if this doesn't
work, then we need to figure out a way to set a
per-toolchain limit on concurrent compiles like there
is for concurrent_links , and figure out how to make
that get set appropriately for nacl differently from
cc.

R=mcgrathr@chromium.org
BUG=555123
==========

to

==========
Allow goma to work w/ NaCl toolchains in GN build.

This change allows the default logic for goma to work
for NaCl (which appears to work fine, at least in local
testing, and it looks like build_nexe.py supports goma
these days as well).

Let's enable this and see what happens; if this doesn't
work, then we need to figure out a way to set a
per-toolchain limit on concurrent compiles like there
is for concurrent_links , and figure out how to make
that get set appropriately for nacl differently from
cc.

R=mcgrathr@chromium.org
BUG=555123
==========

[Roland McGrath, 2015-11-13 18:01:11]

lgtm

[Roland McGrath, 2015-11-13 18:01:16]

The CQ bit was checked by mcgrathr@chromium.org

[commit-bot: I haz the power, 2015-11-13 18:02:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1437303002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1437303002/1

[commit-bot: I haz the power, 2015-11-13 18:11:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-13 18:11:48]

Try jobs failed on following builders:
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)

[Dirk Pranke, 2015-11-13 18:42:17]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2015-11-13 18:44:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1437303002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1437303002/1

[commit-bot: I haz the power, 2015-11-13 19:17:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-13 19:18:40]

Patchset 1 (id:??) landed as
https://crrev.com/d434bf3f1b28416a88604325372a01b908c099c0
Cr-Commit-Position: refs/heads/master@{#359595}