From: Srinivas Maturi <srinivas.maturi@oracle.com>
To: xen-devel@lists.xensource.com
Subject: xen-unstable c/s 18846 build error
Date: Tue, 02 Dec 2008 12:01:33 -0800 [thread overview]
Message-ID: <4935941D.4080604@oracle.com> (raw)
In-Reply-To: <C45A0204.210ED%keir.fraser@eu.citrix.com>
We are seeing the following build error with xen-unstable c/s 18846.
make[4]: Entering directory
`/builddir/build/BUILD/xen-unstable/tools/ioemu-remote/i386-dm'
../xen-hooks.mak:53: *** pciutils-dev package not found - missing
/usr/include/pci
../xen-hooks.mak:54: *** PCI passthrough capability has been disabled
../xen-hooks.mak:53: *** pciutils-dev package not found - missing
/usr/include/pci
../xen-hooks.mak:54: *** PCI passthrough capability has been disabled
/builddir/build/BUILD/xen-unstable//tools/cross-install -d -m0755 -p
"/var/tmp/xen-3.2.0-18846-root//usr/lib/xen/bin"
/builddir/build/BUILD/xen-unstable//tools/cross-install -d -m0755 -p
"/var/tmp/xen-3.2.0-18846-root//etc/xen"
/builddir/build/BUILD/xen-unstable//tools/cross-install -m0755 -p
qemu-ifup "/var/tmp/xen-3.2.0-18846-root//etc/xen/"
/builddir/build/BUILD/xen-unstable//tools/cross-install -m 755 -s
qemu-dm "/var/tmp/xen-3.2.0-18846-root/usr/lib/xen/bin"
make[4]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/ioemu-remote/i386-dm'
make[3]: Leaving directory
`/builddir/build/BUILD/xen-unstable/tools/ioemu-remote'
make[2]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools'
make[2]: Entering directory `/builddir/build/BUILD/xen-unstable/tools'
make -C xenpmd install
make[3]: Entering directory
`/builddir/build/BUILD/xen-unstable/tools/xenpmd'
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__
-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__ -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__ -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-mno-tls-direct-seg-refs -Werror -I../../tools/xenstore
-I../../tools/include -L../../tools/xenstore -lxenstore xenpmd.c
-o xenpmd
cc1: warnings being treated as errors
xenpmd.c: In function 'write_battery_info_to_xenstore':
xenpmd.c:376: warning: call to __builtin___strncat_chk might overflow
destination buffer
make[3]: *** [xenpmd] Error 1
make[3]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools/xenpmd'
make[2]: *** [subdir-install-xenpmd] 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.69009 (%build)
Thanks,
Maturi
next prev parent reply other threads:[~2008-12-02 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 15:10 Debugging the hypervisor Matthew Donovan
2008-05-21 15:44 ` Keir Fraser
2008-12-02 20:01 ` Srinivas Maturi [this message]
2008-12-02 22:17 ` xen-unstable c/s 18846 build error 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=4935941D.4080604@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.