Forcefully set the right gyp variables for 32-bit Linux builds.

Forcefully set the right gyp variables for 32-bit Linux builds.

BUG=455572
TBR=thakis@chromium.org

Committed: https://crrev.com/cc09711e43f8a71f91af6cbbfe40fb3d2941dc06
Cr-Commit-Position: refs/heads/master@{#314799}

[Lei Zhang, 2015-02-05 11:16:16]

TBR

In my chroot, I'm building with Clang, but gyp thinks $clang is 0 when it's
trying to figure out $binutils_version. Even though the comments say
compiler_version.py does not work with Clang, it somehow figured out and sets
$binutils_version to 224, which is why I tested and approved jam's unbreak
32-bit Linux CL.

I didn't try to figure out what's different on the 32-bit Linux bot, but it
believes $binutils_version < 223. Thus the lack of --disable-new-dtags and the
broken testers.

I mucked around with common.gypi, but the more I look at it (and the more I talk
to rsleevi about gyp) the less I understand gyp variables and scoping. So screw
it for now. Force set the variable, hopefully unbreak the bots, and deal with
this another day.

[Lei Zhang, 2015-02-05 11:18:12]

The CQ bit was checked by thestig@chromium.org

[commit-bot: I haz the power, 2015-02-05 11:18:34]

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

[commit-bot: I haz the power, 2015-02-05 13:58:45]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-05 13:59:34]

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