From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: xl_cmdimpl.c errors
Date: Fri, 17 Feb 2012 03:06:18 -0800 (PST) [thread overview]
Message-ID: <1329476778668-5492170.post@n5.nabble.com> (raw)
In-Reply-To: <1329467829314-5491845.post@n5.nabble.com>
I have tested now xen-unstable rev. 24823:b75664e53905 build on Wheezy and is
failed with same error:
...
gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -D__XEN_TOOLS__ -MMD -MF .xl_cmdimpl.o.d
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls
-Werror -Wno-format-zero-length -Wmissing-declarations
-Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC
-DHAVE_YAJL_VERSION
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/libxc
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/libxl
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/libxc
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include
-I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include -c -o
xl_cmdimpl.o xl_cmdimpl.c
xl_cmdimpl.c: In function âprintf_infoâ:
xl_cmdimpl.c:300:5: error: statement with no effect [-Werror=unused-value]
xl_cmdimpl.c:300:21: error: expected â;â before âconfâ
xl_cmdimpl.c:306:28: error: âconfâ undeclared (first use in this function)
xl_cmdimpl.c:306:28: note: each undeclared identifier is reported only once
for each function it appears in
xl_cmdimpl.c:306:5: error: too many arguments to function âyajl_gen_allocâ
/usr/include/yajl/yajl_gen.h:118:23: note: declared here
xl_cmdimpl.c:339:5: error: passing argument 3 of âyajl_gen_get_bufâ from
incompatible pointer type [-Werror]
/usr/include/yajl/yajl_gen.h:144:30: note: expected âsize_t *â but argument
is of type âunsigned int *â
cc1: all warnings being treated as errors
make[3]: *** [xl_cmdimpl.o] Error 1
make[3]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools/libxl'
make[2]: *** [subdir-install-libxl] Error 2
make[2]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools'
make: *** [install-tools] Error 2
If can help I attach also full build log:
http://xen.1045712.n5.nabble.com/file/n5492170/xenbuild.log xenbuild.log
I tried to solve fast the problem for continue with also spice build but I
not been able to fix this problem.
Thanks for any reply and sorry for bad english.
--
View this message in context: http://xen.1045712.n5.nabble.com/xl-cmdimpl-c-errors-tp5491537p5492170.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-17 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:36 xl_cmdimpl.c errors jacek burghardt
2012-02-17 8:22 ` Ian Campbell
2012-02-17 8:37 ` Fantu
2012-02-17 11:06 ` Fantu [this message]
2012-02-17 12:01 ` Ian Campbell
2012-02-17 12:26 ` Fantu
2012-02-17 13:14 ` Fantu
2012-02-17 13:34 ` Ian Campbell
2012-02-17 13:36 ` Fantu
2012-02-17 17:39 ` jacek burghardt
2012-02-21 13:56 ` Fantu
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=1329476778668-5492170.post@n5.nabble.com \
--to=fantonifabio@tiscali.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).