public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Chris Phlipot <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, acme@redhat.com, hpa@zytor.com,
	cphlipot0@gmail.com, peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org
Subject: [tip:perf/core] tools lib subcmd: Respect WERROR=0 for build
Date: Tue, 5 Jul 2016 03:22:47 -0700	[thread overview]
Message-ID: <tip-fd01d06ae33be63cff7d133e650cd1eb32f1d548@git.kernel.org> (raw)
In-Reply-To: <1467349955-1135-3-git-send-email-cphlipot0@gmail.com>

Commit-ID:  fd01d06ae33be63cff7d133e650cd1eb32f1d548
Gitweb:     http://git.kernel.org/tip/fd01d06ae33be63cff7d133e650cd1eb32f1d548
Author:     Chris Phlipot <cphlipot0@gmail.com>
AuthorDate: Thu, 30 Jun 2016 22:12:33 -0700
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Mon, 4 Jul 2016 20:27:26 -0300

tools lib subcmd: Respect WERROR=0 for build

this enables the workaround for compilers that generate warnings when
compiling libsubcmd.

Signed-off-by: Chris Phlipot <cphlipot0@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1467349955-1135-3-git-send-email-cphlipot0@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/lib/subcmd/Makefile | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/tools/lib/subcmd/Makefile b/tools/lib/subcmd/Makefile
index a810370..ce4b7e5 100644
--- a/tools/lib/subcmd/Makefile
+++ b/tools/lib/subcmd/Makefile
@@ -19,7 +19,13 @@ MAKEFLAGS += --no-print-directory
 LIBFILE = $(OUTPUT)libsubcmd.a
 
 CFLAGS := $(EXTRA_WARNINGS) $(EXTRA_CFLAGS)
-CFLAGS += -ggdb3 -Wall -Wextra -std=gnu99 -Werror -O6 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fPIC
+CFLAGS += -ggdb3 -Wall -Wextra -std=gnu99 -O6 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fPIC
+
+# Treat warnings as errors unless directed not to
+ifneq ($(WERROR),0)
+  CFLAGS += -Werror
+endif
+
 CFLAGS += -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE
 
 CFLAGS += -I$(srctree)/tools/include/

  reply	other threads:[~2016-07-05 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01  5:12 [PATCH 0/4] perf tool: Fix Android build Chris Phlipot
2016-07-01  5:12 ` [PATCH 1/4] tools lib api: Respect WERROR=0 for build Chris Phlipot
2016-07-05 10:22   ` [tip:perf/core] " tip-bot for Chris Phlipot
2016-07-01  5:12 ` [PATCH 2/4] tools lib subcmd: " Chris Phlipot
2016-07-05 10:22   ` tip-bot for Chris Phlipot [this message]
2016-07-01  5:12 ` [PATCH 3/4] perf tool: Fix build when sysconf doesn't support cache line size Chris Phlipot
2016-07-04 22:48   ` Arnaldo Carvalho de Melo
2016-07-05  0:19     ` Chris Phlipot
2016-07-05  0:26       ` Arnaldo Carvalho de Melo
2016-07-05  0:47         ` Chris Phlipot
2016-07-05  0:55           ` Arnaldo Carvalho de Melo
2016-07-01  5:12 ` [PATCH 4/4] perf tool: Update android build documentation Chris Phlipot
2016-07-05 10:23   ` [tip:perf/core] perf tools: " tip-bot for Chris Phlipot

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=tip-fd01d06ae33be63cff7d133e650cd1eb32f1d548@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=cphlipot0@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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