All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Maturi <srinivas.maturi@oracle.com>
To: xen-devel@lists.xensource.com
Subject: xen-unstable build failure in tools/blktap/drivers for block-qcow2.c
Date: Wed, 27 Feb 2008 12:08:50 -0800	[thread overview]
Message-ID: <47C5C352.4020200@oracle.com> (raw)


We are seeing build failure of xen-unstable for the last couple of 
changesets,
in tools/blktap/drivers for block-qcow2.c

This seems to be because of the fact that the compile line
uses these flags, -Werror -Wno-unused, treating warnings as errors
and aborting the compilation.

The Makefile in tools/blktap/drivers has these CFLAGS set:
CFLAGS += -Werror
CFLAGS += -Wno-unused

gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -m64 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement -m64 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement -m64 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -m64 -fno-strict-aliasing 
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value 
-Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -m64 -fno-strict-aliasing -std=gnu99 -Wall 
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement 
-D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -m64 
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror -Wno-unused 
-I../../../tools/libxc -I../../../tools/include -I ../../libaio/src -I.. 
-I../lib -I../../../tools/include -I. -I../../xenstore -D_GNU_SOURCE 
-Wp,-MD,.block-qcow2.o.d -c -o block-qcow2.o block-qcow2.c
cc1: warnings being treated as errors
block-qcow2.c: In function ‘qcow2_create’:
block-qcow2.c:1312: warning: ignoring return value of ‘write’, declared 
with attribute warn_unused_result
block-qcow2.c:1314: warning: ignoring return value of ‘write’, declared 
with attribute warn_unused_result
block-qcow2.c:1319: warning: ignoring return value of ‘write’, declared 
with attribute warn_unused_result
block-qcow2.c:1322: warning: ignoring return value of ‘write’, declared 
with attribute warn_unused_result
block-qcow2.c:1325: warning: ignoring return value of ‘write’, declared 
with attribute warn_unused_result
block-qcow2.c: In function ‘qcow_write_compressed’:
block-qcow2.c:1354: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result
.....
.....


Thanks,
Maturi

             reply	other threads:[~2008-02-27 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 20:08 Srinivas Maturi [this message]
2008-02-28 10:27 ` xen-unstable build failure in tools/blktap/drivers for block-qcow2.c Keir Fraser
2008-02-28 12:14   ` Kevin Wolf
2008-02-28 12:37     ` [PATCH] blktap: Fix unused warnings in block-qcow2.c Kevin Wolf
2008-02-28 13:02     ` xen-unstable build failure in tools/blktap/drivers for block-qcow2.c Keir Fraser
2008-02-28 18:59   ` Srinivas Maturi
2008-02-29  8:18     ` Kevin Wolf
2008-02-29 18:38       ` Srinivas Maturi

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=47C5C352.4020200@oracle.com \
    --to=srinivas.maturi@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.