diff options
| author | Philip Withnall <philip.withnall@collabora.co.uk> | 2016-01-30 15:44:03 +0100 |
|---|---|---|
| committer | Philip Withnall <philip.withnall@collabora.co.uk> | 2016-01-30 15:44:03 +0100 |
| commit | 0ff7ca94a608663649defc72021062de098853a8 (patch) | |
| tree | 6d13df9d398ba68ed591ebff20c065c35ffc5f68 /gir/gio-2.0.c | |
| parent | c598d73125c7fd6577ea911c103bf63fb23f0813 (diff) | |
| download | gobject-introspection-0ff7ca94a608663649defc72021062de098853a8.tar.gz | |
giscanner: Disable warnings arising from -D_FORTIFY_SOURCE -O0
Using distutils.ccompiler means that we are forced to use the CFLAGS
from the system’s Python installation, which may contain
-D_FORTIFY_SOURCE. The user’s environment-provided CFLAGS may contain
-O0 (because they are a developer). These two flags cause a warning when
used together. Silence that warning by passing -Wno-cpp to disable
warnings from #warning preprocessor statements in the generated C code.
It doesn’t seem to be possible to selectively undefine _FORTIFY_SOURCE
or to stop using the compiler flags from distutils.sysconfig,
unfortunately.
https://bugzilla.gnome.org/show_bug.cgi?id=757934
Diffstat (limited to 'gir/gio-2.0.c')
0 files changed, 0 insertions, 0 deletions