Update ninja to 9b8e55d

Update ninja to 9b8e55d

On Linux, I did a full ninja checkout and then ran:
python bootstrap.py
./configure.py --with-gtest=../chrome/src/testing/gtest
./ninja ninja_test
./ninja_test  # (all tests passed)
strip ninja

I timed empty builds of 'chrome' with the old and the new version,
both took 1.1s for that. Binary size comparison:
 121632 bytes old binary
 129920 bytes new binary
I used gcc 4.4.3 to build ninja.


On Mac, I updated an existing checkout to the latest version and then ran:
CXX=../chrome-git/src/third_party/llvm-build/Release+Asserts/bin/clang++ \
  ./configure.py -with-gtest=../chrome-git/src/testing/gtest
./ninja
./ninja ninja_test  # (all tests passed)
strip ninja

I timed empty builds of 'chrome' with the old and the new version,
both took 1.1s for that. Binary size comparison:
 128976 bytes old binary
 120904 bytes new binary
I used clang r155352 to build ninja. Last time I used gcc 4.2, which
explains the size drop.


The major new features in this update are:
* ninja cleans up files when interrupted mid-build
* NINJA_STATUS environment variable to tweak the status line
  (see ninja manual)

Also set svn:mime-type to application/octet-stream on these two files.

r134307

[scottmg, 2012-04-27 18:18:03]

lgtm

[commit-bot: I haz the power, 2012-04-27 18:20:33]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/thakis@chromium.org/10221020/1

[commit-bot: I haz the power, 2012-04-27 18:20:35]

Can't apply patch for file depot_tools/ninja-linux64.
While running patch -p0 --forward --force;
patching file depot_tools/ninja-linux64
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 173.
Hunk #3 succeeded at 149 (offset -51 lines).
Hunk #4 succeeded at 218 (offset -51 lines).
Hunk #5 FAILED at 355.
3 out of 5 hunks FAILED -- saving rejects to file depot_tools/ninja-linux64.rej

[scottmg, 2012-04-27 18:22:30]

It doesn't work for binaries or > ~100k; have to gcl commit afaik.

[M-A Ruel, 2012-04-27 18:32:51]

On 2012/04/27 18:22:30, scottmg wrote:
> It doesn't work for binaries or > ~100k; have to gcl commit afaik.

For binary files, just commit them right awat.

[M-A Ruel, 2012-04-27 18:32:58]

On 2012/04/27 18:32:51, Marc-Antoine Ruel wrote:
> On 2012/04/27 18:22:30, scottmg wrote:
> > It doesn't work for binaries or > ~100k; have to gcl commit afaik.
> 
> For binary files, just commit them right awat.

away*

[Nico, 2012-04-27 23:21:25]

On 2012/04/27 18:32:51, Marc-Antoine Ruel wrote:
> On 2012/04/27 18:22:30, scottmg wrote:
> > It doesn't work for binaries or > ~100k; have to gcl commit afaik.
> 
> For binary files, just commit them right awat.

I know. I had created this CL in a binary checkout, so I clicked 'cq' even
though I knew better, hoping I wouldn't have to patch it in to a different
directory instead.