[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xen-unstable c/s 18846 build error



Thanks. Fixed as c/s 18849.

 -- Keir

On 02/12/2008 20:01, "Srinivas Maturi" <srinivas.maturi@xxxxxxxxxx> wrote:

> 
> 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
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.