From: mike xiao <mike.xiao@oracle.com>
To: xen-devel@lists.xensource.com, srinivas.maturi@oracle.com
Subject: build failure information
Date: Thu, 25 Jun 2009 09:20:58 +0800 [thread overview]
Message-ID: <4A42D0FA.90503@oracle.com> (raw)
build failure information.
xen-unstable c/s 19821
linux-unstable c/s 909
The build failed for xen-unstable on i386 arch with error messages:
gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -O2 -fomit-frame-pointer
-m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -O2
-fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -O2 -fomit-frame-pointer -m32 -march=i686
-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_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -O2
-fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF
.subdir-install-blktap2.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -O2
-fomit-frame-pointer -m32 -march=i686 -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_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
-I../../tools/libxc -I../../tools/include -O2 -fomit-frame-pointer -m32
-march=i686 -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_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
-I../../tools/libxc -I../../tools/include -O2 -fomit-frame-pointer -m32
-march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .block-ram.o.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
-Werror -g -O0 -Wno-unused -fno-strict-aliasing -I../lib -I../../libxc
-I../include -I../../include -I ../../..//tools/libaio/src -D_GNU_SOURCE
-DUSE_NFS_LOCKS -c -o block-ram.o block-ram.c
cc1: warnings being treated as errors
block-ram.c: In function 'get_image_info':
block-ram.c:104: warning: format '%lu' expects type 'long unsigned int',
but argument 3 has type 'uint64_t'
block-ram.c: In function 'tdram_open':
block-ram.c:129: warning: format '%lu' expects type 'long unsigned int',
but argument 3 has type 'uint64_t'
make[5]: *** [block-ram.o] Error 1
make[5]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/blktap2/drivers'
make[4]: *** [subdir-install-drivers] Error 2
make[4]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/blktap2'
make[3]: *** [subdirs-install] Error 2
make[3]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/blktap2'
make[2]: *** [subdir-install-blktap2] 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.93464 (%build)
reply other threads:[~2009-06-25 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A42D0FA.90503@oracle.com \
--to=mike.xiao@oracle.com \
--cc=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.