[nautilus] meson.build: Pass -Wno-error=maybe-uninitialized
- From: Ernestas Kulik <ernestask src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [nautilus] meson.build: Pass -Wno-error=maybe-uninitialized
- Date: Wed, 31 Oct 2018 20:54:05 +0000 (UTC)
commit 4c2e9da9a904d074b699508a969403d004f321f8
Author: Ernestas Kulik <ernestask gnome org>
Date: Wed Oct 31 21:47:59 2018 +0100
meson.build: Pass -Wno-error=maybe-uninitialized
The nightly flatpak builds after
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/commit/ce54a2527555e51e4ebf4cce9cbb6259cafa89a4
fail due to an unfortunate combination of compiler flags. This commit
disables the error, since it’s rather inconsistent when the warning is
spit out.
meson.build | 7 +++++++
1 file changed, 7 insertions(+)
---
diff --git a/meson.build b/meson.build
index 5660153df..74a441f8e 100644
--- a/meson.build
+++ b/meson.build
@@ -54,6 +54,13 @@ add_project_arguments(
'-Werror=strict-prototypes',
'-Werror=undef',
'-Werror=uninitialized',
+ # Context:
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/commit/ce54a2527555e51e4ebf4cce9cbb6259cafa89a4
+ # -O2 and -fexceptions unmask some cases of -Wmaybe-uninitialized, which
+ # become errors for some reason (I’m guessing because of the
+ # -Werror=uninitialized above, but no idea why that implies this).
+ # This being an error is nice and all, but not when its appearance is
+ # dependent on optimization level and other flags.
+ '-Wno-error=maybe-uninitialized',
]),
'-D_GNU_SOURCE',
language: 'c'
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]