summarylogtreecommitdiffstats
path: root/chromium-FORTIFY_SOURCE.patch
diff options
context:
space:
mode:
authorBlackEagle2017-03-12 21:41:46 +0100
committerBlackEagle2017-03-12 21:41:46 +0100
commit0c95a5f5b0a770d46c39f6538e65119896bfd2a2 (patch)
tree00c70a6eab4c16da32b7f682cce4d920912cd562 /chromium-FORTIFY_SOURCE.patch
parent2ed45f15e65b74422e7fffd97c921c9d7f1c78a2 (diff)
downloadaur-0c95a5f5b0a770d46c39f6538e65119896bfd2a2.tar.gz
opera-developer-ffmpeg-codecs :: 58.0.3029.6-1
Signed-off-by: BlackEagle <ike.devolder@gmail.com>
Diffstat (limited to 'chromium-FORTIFY_SOURCE.patch')
-rw-r--r--chromium-FORTIFY_SOURCE.patch27
1 files changed, 27 insertions, 0 deletions
diff --git a/chromium-FORTIFY_SOURCE.patch b/chromium-FORTIFY_SOURCE.patch
new file mode 100644
index 000000000000..c6477d690872
--- /dev/null
+++ b/chromium-FORTIFY_SOURCE.patch
@@ -0,0 +1,27 @@
+Drop _FORTIFY_SOURCE=2 from defines
+
+Gentoo toolchains enable this by default. Removing this prevents spammy
+warnings about the macro being redefined.
+
+--- a/build/config/compiler/BUILD.gn
++++ b/build/config/compiler/BUILD.gn
+@@ -1069,19 +1069,6 @@ config("chromium_code") {
+ "__STDC_FORMAT_MACROS",
+ ]
+
+- if (!is_debug && !using_sanitizer &&
+- (!is_linux || !is_clang || is_official_build)) {
+- # _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
+- # disabled, so only do that for Release build.
+- defines += [ "_FORTIFY_SOURCE=2" ]
+- }
+-
+ if (is_mac || is_ios) {
+ cflags_objc = [ "-Wobjc-missing-property-synthesis" ]
+ cflags_objcc = [ "-Wobjc-missing-property-synthesis" ]