[Android] Revert the NDK back to r10e.

build/common.gypi

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 1708 matching lines @@
             # Unfortunately, it is required to use the absolute path to the SDK
             # because it us passed to ant which uses a different relative path
             # from GYP.
             'android_sdk_root%': '<!(cd <(DEPTH) && pwd -P)/third_party/android_tools/sdk/',
             # Similarly, gdbserver and the Android toolchain need to use the
             # absolute path to the NDK because they are used at different levels
             # in the GYP files.
             'android_ndk_absolute_root%': '<!(cd <(DEPTH) && pwd -P)/third_party/android_tools/ndk/',
             'android_host_arch%': '<!(uname -m)',
             # Version of the NDK. Used to ensure full rebuilds on NDK rolls.
-            'android_ndk_version%': 'r11c',
+            'android_ndk_version%': 'r10e',

[Michael Achenbach, 2016/06/07 07:08:23]

We might need a better mechanism in v8 for this. We have an auto-roller that
automatically pulls in the new android_tools, but it doesn't automatically
change this version variable in our standalone.gypi.

Clang has a similar mechanism for rebuilding, but the version isn't hardcoded in
a config file, but comes from the repo that rolled. Could we get something
similar here too? E.g. a small config file in android_tools that holds this
version, letting this variable here point to the content of that file. On each
roll the file could be edited.

Otherwise we get incremental build breakages on each android roll/revert (just
got one).

[jbudorick, 2016/06/07 12:59:58]

Sure, I'll do something like that before the next roll.

             # Android API-level of the SDK used for compilation.
             'android_sdk_version%': '23',
             'android_sdk_build_tools_version%': '23.0.1',
             'host_os%': "<!(uname -s | sed -e 's/Linux/linux/;s/Darwin/mac/')",
 
             'conditions': [
               # Figure this out early since it needs symbols from libgcc.a, so it
               # has to be before that in the set of libraries.
               # ASan needs to dynamically link to libc++ even in static builds so
               # that it can interpose operator new.
@@ skipping 4629 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }