mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/5] Makefile: disable unused-but-set-variable warning
Date: Mon,  2 Jan 2012 14:57:11 +0100	[thread overview]
Message-ID: <1325512634-25797-3-git-send-email-s.hauer@pengutronix.de> (raw)
In-Reply-To: <1325512634-25797-1-git-send-email-s.hauer@pengutronix.de>

This produces too many false positives.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 Makefile |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/Makefile b/Makefile
index b6e4c0c..d96fc88 100644
--- a/Makefile
+++ b/Makefile
@@ -450,6 +450,10 @@ endif
 # Force gcc to behave correct even for buggy distributions
 CFLAGS          += $(call cc-option, -fno-stack-protector)
 
+# This warning generated too much noise in a regular build.
+# Use make W=1 to enable this warning (see scripts/Makefile.build)
+CFLAGS += $(call cc-disable-warning, unused-but-set-variable)
+
 # arch Makefile may override CC so keep this after arch Makefile is included
 NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)
 CHECKFLAGS     += $(NOSTDINC_FLAGS)
-- 
1.7.7.3


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2012-01-02 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 13:57 patches for compiler warnings Sascha Hauer
2012-01-02 13:57 ` [PATCH 1/5] scripts/Kbuild.include: update to latest kernel version Sascha Hauer
2012-01-02 13:57 ` Sascha Hauer [this message]
2012-01-02 13:57 ` [PATCH 3/5] mtd Kconfig: only select NAND_READ_OOB when NAND is enabled Sascha Hauer
2012-01-02 13:57 ` [PATCH 4/5] net dm9k: Fix compiler warning Sascha Hauer
2012-01-02 13:57 ` [PATCH 5/5] Makefile: disable warning: generating trampoline in object Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1325512634-25797-3-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox