aboutsummaryrefslogtreecommitdiff
path: root/m4/compiler_warnings.m4
AgeCommit message (Collapse)Author
2020-01-30build: use AX_IS_RELEASE() and AX_COMPILER_FLAGS()Aleksander Morgado
The autoconf macros AX_COMPILER_FLAGS_{CFLAGS|GIR|LDFLAGS} test for compiler and linker support of various flags, and add the flags to the generated output. If the command-line option '--enable-compile-warnings' is specified to 'configure', a number of additional warning options is also added to the output. This is the default. This update requires the presence of the GNU autoconf-archive in the system.
2019-04-05build: make compiler warning options compatible with clangBen Chan
This patch updates m4/compiler-warnings.m4 as follows to make it more compatible with clang: * clang doesn't support -Wunused-but-set-variable, which can be replaced with -Wunused-variable as the latter covers unused variables with or without an assigned value and is supported by gcc and clang. * -Wno-unused-function is added to let clang ignore unused functions that are auto-generated.
2019-04-02build: fix -Wunused-but-set-variable support and handle clang betterDan Williams
By default the build used -Wno-unused-but-set-variable but that's clearly not what we want. Fix those problems. When using clang, the compiler doesn't error on unknown compile options, so let's add -Werror to the checking too. CC='clang' configure:3408: checking for gcc configure:3435: result: clang ... configure:17644: checking whether gcc understands -Wno-unused-but-set-variable configure:17657: clang -c -Wall -std=gnu89 -g -O2 -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wstrict-prototypes -Wno-unused-parameter -Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-but-set-variable conftest.c >&5 warning: unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-const-variable'? [-Wunknown-warning-option] 1 warning generated. configure:17657: $? = 0 configure:17666: result: yes Reported-by: Torsten Hilbrich <torsten.hilbrich@secunet.com>
2018-04-24m4/compiler_warnings.m4: Let -Werror be disabledIain Lane
It's annoying for distributors to build with -Werror, since it means that compiler upgrades can break the build. Let's let them disable it, but keep it enabled by default.
2016-07-21build: don't disable the aliasing checksLubomir Rintel
We now don't break the strict aliasing rules. Also, having a compiler flag that disables a warning among the flags that are meant to add extra sanity checking is not correct either: --enable-extra-warnings=no would generate a bad aliasin warning while the --enable-extra-warnings=yes would not.
2013-05-17build: use -Wformat-securityAleksander Morgado
2012-08-24build: warn about unused but set variablesAleksander Morgado
2012-03-15build: avoid using -Wfloat-equal compilation optionAleksander Morgado
In order to compile code generated by gdbus-codegen.
2012-03-15build: avoid using -Wshadow compilation optionAleksander Morgado
In order to compile code generated by gdbus-codegen.
2012-02-07build: do not warn about using deprecated methodsAleksander Morgado
GValueArray is deprecated since GLib 2.31.14, but we need to use it for dbus-glib based code. We should re-enable deprecation warnings once we switch to GDBus.
2010-01-27build: unify compiler warningsMichael Biebl