0020.patch (1605B)
1 From 8e4789150a58704b56686573d93863b7a9104059 Mon Sep 17 00:00:00 2001 2 From: Michael Froman <mfroman@mozilla.com> 3 Date: Fri, 7 Nov 2025 12:13:00 -0600 4 Subject: Bug 1997515 - remove hardening settings from 5 third_party/chromium/build r?ng! 6 7 In bug 1974813 we updated the third_party/chromium/build directory which 8 added hardening settings to the moz.build files under libwebrtc (and 9 abseil-cpp) but we really should be getting these settings from 10 build/moz.configure/toolchain.configure. We currently see warnings 11 during (at least) builds on macOS due to conflicting settings. 12 Mercurial Revision: https://hg.mozilla.org/mozilla-central/rev/d9db1d783e13f2c288c4f195830851ab2ee27209 13 --- 14 config/compiler/BUILD.gn | 3 +++ 15 1 file changed, 3 insertions(+) 16 17 diff --git a/config/compiler/BUILD.gn b/config/compiler/BUILD.gn 18 index a59a5df6e..c4c706052 100644 19 --- a/config/compiler/BUILD.gn 20 +++ b/config/compiler/BUILD.gn 21 @@ -1099,6 +1099,8 @@ config("disallow_unstable_features") { 22 } 23 24 config("libcxx_hardening") { 25 +# Mozilla - these settings come from third_party/chromium/build/config/compiler/BUILD.gn 26 +if (false) { 27 # Normally, this would be defined in the `runtime_library` config but NaCl 28 # saigo libc++ does not use the custom hermetic libc++. Unfortunately, there 29 # isn't really a better config to add this define for the define to 30 @@ -1119,6 +1121,7 @@ config("libcxx_hardening") { 31 defines += [ "_GLIBCXX_ASSERTIONS=1" ] 32 } 33 } 34 +} 35 36 # The BUILDCONFIG file sets this config on targets by default, which means when 37 # building with ThinLTO, no optimization is performed in the link step.