Currently, using an undeclared function gives a compile warning, but it
can lead to a nasty to debug runtime stack corruptions if the prototype
of the function is different from what gcc guessed.
With -Werror-implicit-function-declaration we are getting an immediate
compile error instead.
Signed-off-by: Adrian Bunk <[email protected]>
---
Makefile | 3 ++-
drivers/input/joystick/iforce/Makefile | 2 --
2 files changed, 2 insertions(+), 3 deletions(-)
--- linux-2.6.17-mm6-full/Makefile.old 2006-07-06 12:17:02.000000000 +0200
+++ linux-2.6.17-mm6-full/Makefile 2006-07-06 12:18:52.000000000 +0200
@@ -318,7 +318,8 @@
CPPFLAGS := -D__KERNEL__ $(LINUXINCLUDE)
CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
- -fno-strict-aliasing -fno-common
+ -fno-strict-aliasing -fno-common \
+ -Werror-implicit-function-declaration
# Force gcc to behave correct even for buggy distributions
CFLAGS += $(call cc-option, -fno-stack-protector-all \
-fno-stack-protector)
--- linux-2.6.17-mm6-full/drivers/input/joystick/iforce/Makefile.old 2006-07-06 12:19:08.000000000 +0200
+++ linux-2.6.17-mm6-full/drivers/input/joystick/iforce/Makefile 2006-07-06 12:19:16.000000000 +0200
@@ -16,5 +16,3 @@
ifeq ($(CONFIG_JOYSTICK_IFORCE_USB),y)
iforce-objs += iforce-usb.o
endif
-
-EXTRA_CFLAGS = -Werror-implicit-function-declaration
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]