Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATXH v3 2/2] package/xen: Disable strict unused-const-variable checking
Date: Thu, 8 Dec 2016 12:11:12 -0800	[thread overview]
Message-ID: <1481227872-31723-3-git-send-email-alistair.francis@xilinx.com> (raw)
In-Reply-To: <1481227872-31723-1-git-send-email-alistair.francis@xilinx.com>

The strict unused-const-variable checking was causing autobuilder errors
when trying to build Xen tools/libxl as the migrate_*[] arrays are not
always accessed.

To avoid the error edit the Makefile to stop the warnings being treated
as errors.

Fixes:
  http://autobuild.buildroot.net/results/0e0/0e0d4aa4a05da5804821951289c0a4049b009c61/

Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
---
 ...-Disable-strict-unused-const-variable-che.patch | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 package/xen/0003-tools-libxl-Disable-strict-unused-const-variable-che.patch

diff --git a/package/xen/0003-tools-libxl-Disable-strict-unused-const-variable-che.patch b/package/xen/0003-tools-libxl-Disable-strict-unused-const-variable-che.patch
new file mode 100644
index 0000000..05575fa
--- /dev/null
+++ b/package/xen/0003-tools-libxl-Disable-strict-unused-const-variable-che.patch
@@ -0,0 +1,27 @@
+From 2e04c2db466b2d7881b46505741798701b1aa271 Mon Sep 17 00:00:00 2001
+From: Alistair Francis <alistair.francis@xilinx.com>
+Date: Wed, 7 Dec 2016 11:35:10 -0800
+Subject: [PATCH] tools/libxl: Disable strict unused-const-variable checking
+
+Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
+---
+ tools/libxl/Makefile | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/tools/libxl/Makefile b/tools/libxl/Makefile
+index defeb40..9d320d1 100644
+--- a/tools/libxl/Makefile
++++ b/tools/libxl/Makefile
+@@ -12,7 +12,8 @@ XLUMAJOR = 4.7
+ XLUMINOR = 0
+ 
+ CFLAGS += -Werror -Wno-format-zero-length -Wmissing-declarations \
+-	-Wno-declaration-after-statement -Wformat-nonliteral
++	-Wno-declaration-after-statement -Wformat-nonliteral \
++	-Werror=unused-const-variable=0
+ CFLAGS += -I. -fPIC
+ 
+ ifeq ($(CONFIG_Linux),y)
+-- 
+2.7.4
+
-- 
2.7.4

  parent reply	other threads:[~2016-12-08 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 20:11 [Buildroot] [PATXH v3 0/2] Update Xen and fix build issue Alistair Francis
2016-12-08 20:11 ` [Buildroot] [PATXH v3 1/2] package/xen: Bump Xen to 4.7.1 Alistair Francis
2016-12-08 21:42   ` Thomas Petazzoni
2016-12-08 21:46     ` Alistair Francis
2016-12-08 20:11 ` Alistair Francis [this message]
2016-12-08 21:06   ` [Buildroot] [PATXH v3 2/2] package/xen: Disable strict unused-const-variable checking Thomas Petazzoni
2016-12-08 22:48     ` Alistair Francis

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=1481227872-31723-3-git-send-email-alistair.francis@xilinx.com \
    --to=alistair.francis@xilinx.com \
    --cc=buildroot@busybox.net \
    /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