mac: remove libc++-static 10.6 compatibility hack

build/config/compiler/BUILD.gn

 # Copyright (c) 2013 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.
 
 import("//build/config/android/config.gni")
 import("//build/config/chrome_build.gni")
 import("//build/config/compiler/compiler.gni")
 import("//build/config/nacl/config.gni")
 import("//build/toolchain/cc_wrapper.gni")
 import("//build/toolchain/toolchain.gni")
@@ skipping 385 matching lines @@
     # http://crbug.com/427584
     cflags_cc += [ "-std=gnu++11" ]
   } else if (!is_win && !is_nacl) {
     # TODO(mcgrathr) - the NaCl GCC toolchain doesn't support either gnu++11
     # or c++11; we technically don't need this toolchain any more, but there
     # are still a few buildbots using it, so until those are turned off
     # we need the !is_nacl clause and the (is_nacl && is_clang) clause, above.
     cflags_cc += [ "-std=c++11" ]
   }
 
-  if (is_mac) {
-    # Tell the compiler to use libc++'s headers and the linker to link
-    # against libc++.  The latter part normally requires OS X 10.7,
-    # but we still support running on 10.6.  How does this work?  Two
-    # parts:
-    # 1. Chromium's clang doesn't error on -mmacosx-version-min=10.6
-    #    combined with -stdlib=libc++ (it normally silently produced a
-    #    binary that doesn't run on 10.6)
-    # 2. Further down, library_dirs is set to
-    #    third_party/libc++-static, which contains a static
-    #    libc++.a library.  The linker then links against that instead
-    #    of against /usr/lib/libc++.dylib when it sees the -lc++ flag
-    #    added by the driver.
-    #
-    # In component builds, just link to the system libc++.  This has
-    # the effect of making everything depend on libc++, which means
-    # component-build binaries won't run on 10.6 (no libc++ there),
-    # but for a developer-only configuration that's ok.  (We don't
-    # want to raise the deployment target yet so that official and
-    # dev builds have the same deployment target.  This affects
-    # things like which functions are considered deprecated.)
-    cflags_cc += [ "-stdlib=libc++" ]

[Mark Mentovai, 2016/09/12 18:33:26]

We still need -stdlib, until we finally get our deployment target bumped to 10.8
or higher.

-    ldflags += [ "-stdlib=libc++" ]
-    if (!is_component_build && !is_asan) {

[Mark Mentovai, 2016/09/12 18:33:26]

But this stuff, and the long comment in this block, are no longer necessary.

-      ldflags += [
-        "-L",
-        rebase_path("//third_party/libc++-static", root_build_dir),
-      ]
-    }
-  }
-
   # Add flags for link-time optimization. These flags enable
   # optimizations/transformations that require whole-program visibility at link
   # time, so they need to be applied to all translation units, and we may end up
   # with miscompiles if only part of the program is compiled with LTO flags. For
   # that reason, we cannot allow targets to enable or disable these flags, for
   # example by disabling the optimize configuration.
   # TODO(pcc): Make this conditional on is_official_build rather than on gn
   # flags for specific features.
   if (!is_debug && (allow_posix_link_time_opt || is_cfi) && !is_nacl) {
     cflags += [ "-flto" ]
@@ skipping 1153 matching lines @@
 
 if (is_ios || is_mac) {
   # On Mac and iOS, this enables support for ARC (automatic ref-counting).
   # See http://clang.llvm.org/docs/AutomaticReferenceCounting.html.
   config("enable_arc") {
     common_flags = [ "-fobjc-arc" ]
     cflags_objc = common_flags
     cflags_objcc = common_flags
   }
 }