From 0ae8906d7a52a7ab305c236668555c37fbbc1e76 Mon Sep 17 00:00:00 2001 From: Alexey Gladkov Date: Fri, 30 Mar 2018 21:27:10 +0300 Subject: [PATCH 19/24] ALT: allow _FORTIFY_SOURCE for clang Signed-off-by: Alexey Gladkov --- 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 959a5923174..988708210b1 100644 --- a/build/config/compiler/BUILD.gn +++ b/build/config/compiler/BUILD.gn @@ -1516,21 +1516,21 @@ config("chromium_code") { } # In Chromium code, we define __STDC_foo_MACROS in order to get the # C99 macros on Mac and Linux. defines = [ "__STDC_CONSTANT_MACROS", "__STDC_FORMAT_MACROS", ] if (!is_debug && !using_sanitizer && - (!is_linux || !is_clang || is_official_build) && + (!is_linux || is_official_build) && current_cpu != "s390x" && current_cpu != "s390" && current_cpu != "ppc64" && current_cpu != "ppc64" && current_cpu != "mips" && current_cpu != "mips64") { # _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 # official builds. # # Non-chromium code is not guaranteed to compile cleanly with # _FORTIFY_SOURCE. Also, fortified build may fail when optimizations are -- 2.17.1