From 704fe5e663d7e02f8e375e0bf8617a1aacc4903c Mon Sep 17 00:00:00 2001 From: Ryan Macnak Date: Mon, 6 May 2019 23:50:32 +0000 Subject: [PATCH] [build] Newer versions of Mac have a predefined _FORTIFY_SOURCE that creates a conflict trying to set it with a compiler argument. Change-Id: I7518f30a8eaf4302f76326db1ea970fdd9760f61 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/101324 Reviewed-by: Zach Anderson Reviewed-by: Aart Bik Commit-Queue: Ryan Macnak --- build/config/compiler/BUILD.gn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/config/compiler/BUILD.gn b/build/config/compiler/BUILD.gn index 0a6a259d2d2..baa7bc3bc70 100644 --- a/build/config/compiler/BUILD.gn +++ b/build/config/compiler/BUILD.gn @@ -594,7 +594,7 @@ config("chromium_code") { ] defines = [] - if (!using_sanitizer && (!is_linux || !is_clang)) { + if (!using_sanitizer && !is_clang) { # _FORTIFY_SOURCE isn't really supported by Clang now, see # http://llvm.org/bugs/show_bug.cgi?id=16821. # It seems to work fine with Ubuntu 12 headers though, so use it in