From: Srinivas Maturi <srinivas.maturi@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Build failure with xen-unsable c/s 19286
Date: Mon, 09 Mar 2009 11:44:38 -0700 [thread overview]
Message-ID: <49B56396.8080502@oracle.com> (raw)
Build failed for xen-unstable c/s 19286 with the following messages:
make[5]: Entering directory
`/builddir/build/BUILD/xen-unstable/tools/blktap/drivers'
.....
.....
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .subdir-install-blktap.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .subdir-install-drivers.d -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF
.block-qcow2.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror
-Wno-unused -I../lib -I../../../tools/libxc -I../../../tools/include
-I../../../tools/xenstore -I../../../tools/include -I ../../libaio/src
-D_GNU_SOURCE -c -o block-qcow2.o block-qcow2.c
cc1: warnings being treated as errors
block-qcow2.c: In function 'qcow2_create':
block-qcow2.c:2045: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
block-qcow2.c:2047: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
block-qcow2.c:2052: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
block-qcow2.c:2055: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
block-qcow2.c:2058: warning: ignoring return value of 'write', declared
with attribute warn_unused_result
make[5]: *** [block-qcow2.o] Error 1
make[5]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/blktap/drivers'
make[4]: *** [subdir-install-drivers] Error 2
make[4]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools/blktap'
make[3]: *** [subdirs-install] Error 2
make[3]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools/blktap'
make[2]: *** [subdir-install-blktap] Error 2
make[2]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools'
make: *** [install-tools] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.78277 (%build)
Thanks,
Maturi
next reply other threads:[~2009-03-09 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 18:44 Srinivas Maturi [this message]
2009-03-09 19:06 ` Build failure with xen-unsable c/s 19286 Keir Fraser
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=49B56396.8080502@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.