Roll chromium to fix java_cpp_enum.py

Roll chromium to fix java_cpp_enum.py

Remove assumption on absolute paths in java_cpp_enum.py.

In java_cpp_enum.py there were assumptions on 'build' being
a component of the absolute path of the script invoking the
script. This leads to problems when other projects are using
the Chromium build toolchain (in this case libyuv), where
the script invoking GYP is located in the root of the project
dir (https://chromium.googlesource.com/libyuv/libyuv/+/master/gyp_libyuv).

TBR=harryjin@google.com, jkellander@chromium.org
BUG=libyuv:536
Committed: https://chromium.googlesource.com/libyuv/libyuv/+/d1c6eb0887e83fb03e00aa9c35be59a26e4735a0

[fbarchard, 2016-01-13 02:22:17]

Description was changed from

==========
Roll chromium to fix java_cpp_enum.py

Remove assumption on absolute paths in java_cpp_enum.py.

In java_cpp_enum.py there were assumptions on 'build' being
a component of the absolute path of the script invoking the
script. This leads to problems when other projects are using
the Chromium build toolchain (in this case libyuv), where
the script invoking GYP is located in the root of the project
dir (https://chromium.googlesource.com/libyuv/libyuv/+/master/gyp_libyuv).

R=harryjin@google.com, jkellander@chromium.org
BUG=libyuv:536
==========

to

==========
Roll chromium to fix java_cpp_enum.py

Remove assumption on absolute paths in java_cpp_enum.py.

In java_cpp_enum.py there were assumptions on 'build' being
a component of the absolute path of the script invoking the
script. This leads to problems when other projects are using
the Chromium build toolchain (in this case libyuv), where
the script invoking GYP is located in the root of the project
dir (https://chromium.googlesource.com/libyuv/libyuv/+/master/gyp_libyuv).

TBR=harryjin@google.com, jkellander@chromium.org
BUG=libyuv:536
==========

[fbarchard, 2016-01-13 02:37:33]

fbarchard@chromium.org changed reviewers:
+ fbarchard@chromium.org
- harryjin@google.com

[fbarchard, 2016-01-13 02:37:33]

This resolves the gyp issue but causes a build error

../../third_party/gflags/src/gflags.cc:281:53: error: unused typedef
'true_false_equal' [-Werror,-Wunused-local-typedef]
    COMPILE_ASSERT(sizeof(kTrue) == sizeof(kFalse), true_false_equal);
                                                    ^
1 error generated.
[8/231] CXX obj/chromium/src/testing/gtest/src/gtest.gtest.o

[fbarchard, 2016-01-14 19:39:05]

disabled warning in gtest.gyp/build.gn.  builds 32 bit linux now.

[fbarchard1, 2016-01-14 19:39:16]

Description was changed from

==========
Roll chromium to fix java_cpp_enum.py

Remove assumption on absolute paths in java_cpp_enum.py.

In java_cpp_enum.py there were assumptions on 'build' being
a component of the absolute path of the script invoking the
script. This leads to problems when other projects are using
the Chromium build toolchain (in this case libyuv), where
the script invoking GYP is located in the root of the project
dir (https://chromium.googlesource.com/libyuv/libyuv/+/master/gyp_libyuv).

TBR=harryjin@google.com, jkellander@chromium.org
BUG=libyuv:536
==========

to

==========
Roll chromium to fix java_cpp_enum.py

Remove assumption on absolute paths in java_cpp_enum.py.

In java_cpp_enum.py there were assumptions on 'build' being
a component of the absolute path of the script invoking the
script. This leads to problems when other projects are using
the Chromium build toolchain (in this case libyuv), where
the script invoking GYP is located in the root of the project
dir (https://chromium.googlesource.com/libyuv/libyuv/+/master/gyp_libyuv).

TBR=harryjin@google.com, jkellander@chromium.org
BUG=libyuv:536

Committed:
https://chromium.googlesource.com/libyuv/libyuv/+/d1c6eb0887e83fb03e00aa9c35b...
==========

[fbarchard1, 2016-01-14 19:39:17]

Committed patchset #1 (id:1) manually as
d1c6eb0887e83fb03e00aa9c35be59a26e4735a0 (presubmit successful).