bump chromium version and disable use_sysroot

libyuv.gyp

Index: libyuv.gyp
diff --git a/libyuv.gyp b/libyuv.gyp
index 3d8cb35953c35162c13f96f2719ea5b0007c5b16..4e42312fc5da2889d5d573a024a4ee6ce433db3b 100644
--- a/libyuv.gyp
+++ b/libyuv.gyp
@@ -17,6 +17,13 @@
     'GCC_PRECOMPILE_PREFIX_HEADER': 'NO',
   },
   'variables': {
+    'variables': {
+      # Disable use of sysroot for Linux. It's enabled by default in Chromium,
+      # but it currently lacks the libudev-dev package.
+      # TODO(kjellander): Remove when crbug.com/561584 is fixed.
+      'use_sysroot': 0,

[Sam Clegg, 2016/01/06 18:37:34]

I think this broke the Linux ARM builder, where sysroot is required to be used:
https://build.chromium.org/p/chromium.fyi/builders/Linux%20ARM

Can you tell my why this change was needed?   Is udev actually used by libyuv?  

[kjellander_chromium, 2016/01/11 20:36:03]

Frank was making this change with the assumption that it was needed because
WebRTC was hitting problems with libudev being missing when using sysroots. It's
not used by libyuv so libyuv should be able to use sysroots.

For libyuv, this setting could go into a supplement.gypi file instead, as we do
in WebRTC. Then it won't affect downstream. Just make sure to put it into a
subdirectory, like 'source' or 'util' in this case.
That said, I think it's better to enable the sysroot again. But for the runhooks
step to execute you must then either roll chromium_revision (it only runs as
part of when
https://chromium.googlesource.com/libyuv/libyuv/+/master/sync_chromium.py runs),
or increment the SCRIPT_VERSION number in that file.

+    },
+    'use_sysroot%': '<(use_sysroot)',
     'use_system_libjpeg%': 0,
     'libyuv_disable_jpeg%': 0,
     # 'chromium_code' treats libyuv as internal and increases warning level.