Filipe Brandenburger a01a4517e1 build-sys: Check behavior of -Werror=shadow before deciding to use it ... gcc versions 4.6 and earlier used to complain when a local variable shadows a global function, 4.7 and above only complain if a local variable shadows a global variable. Fix this by checking whether gcc 4.7+ behavior is in place before deciding to use -Werror=shadow in $(CFLAGS), by using a custom test program source that shadows a global function with a local variable and confirming that -Werror=shadow does not make the compile to break. Tested: - On gcc 4.7 and 4.8, confirmed nothing changed (other than the order of the -Werror=shadow argument, going to the end of CFLAGS.) - On gcc 4.6, confirmed by looking at the config.log output that the check for -Werror=shadow failed and it was not included in CFLAGS. - Ran `make V=1` to confirm -Werror=shadow was still in use, introduced a bogus shadowing issue and confirmed it was caught when building with a recent gcc.		2015-09-22 09:54:33 -07:00
..
.gitignore	remove gudev and gtk-doc	2015-06-03 00:22:53 +02:00
arch.m4	sd-boot: add EFI boot manager and stub loader	2015-02-17 14:36:59 +01:00
attributes.m4	build-sys: Check behavior of -Werror=shadow before deciding to use it	2015-09-22 09:54:33 -07:00
ax_compiler_vendor.m4	build-sys: Look for gcc-* binutils wrappers only if we're using GCC	2015-09-01 13:27:42 +02:00
ax_normalize_path.m4	build-sys: Normalize paths of configure options	2015-06-02 07:54:51 -07:00