From 6262e4e74e2cdb9f231dc71c9893d4a4bd1e88df Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Mon, 25 Apr 2011 08:06:40 +0000 Subject: disable security warning flags when possible Some toolchains enable security warning flags by default, but these don't really make sense in the u-boot world. Such as forcing changes like: -printf(foo); +printf("%s", foo); So disable the flags when the compiler supports them. Linux has already merged a similar change in their build system. Signed-off-by: Mike Frysinger --- config.mk | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'config.mk') diff --git a/config.mk b/config.mk index ed44d03ad..e2b440d8b 100644 --- a/config.mk +++ b/config.mk @@ -211,6 +211,10 @@ CFLAGS := $(CPPFLAGS) -Wall -Wstrict-prototypes endif CFLAGS += $(call cc-option,-fno-stack-protector) +# Some toolchains enable security related warning flags by default, +# but they don't make much sense in the u-boot world, so disable them. +CFLAGS += $(call cc-option,-Wno-format-nonliteral) +CFLAGS += $(call cc-option,-Wno-format-security) # $(CPPFLAGS) sets -g, which causes gcc to pass a suitable -g # option to the assembler. -- cgit v1.2.3