From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: xen-unstable build fails
Date: Wed, 05 May 2010 07:46:12 +0200 [thread overview]
Message-ID: <4BE10624.7020505@ts.fujitsu.com> (raw)
Hi,
latest xen-unstable doesn't build on my machine:
gcc -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 .xen-hptool.o.d
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror -I
../../tools/python/xen/lowlevel/xc -I ../../tools/libxc -I ../../tools/include
-c -o xen-hptool.o xen-hptool.c
xen-hptool.c: In function ‘suspend_guest’:
xen-hptool.c:136: error: too few arguments to function ‘xc_suspend_evtchn_release’
xen-hptool.c: In function ‘hp_mem_offline_func’:
xen-hptool.c:231: error: too few arguments to function ‘xc_suspend_evtchn_release’
make[3]: *** [xen-hptool.o] Error 1
make[3]: Leaving directory `/root/xen-unstable.hg/tools/misc'
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next reply other threads:[~2010-05-05 5:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 5:46 Juergen Gross [this message]
2010-05-05 6:31 ` xen-unstable build fails Shriram R
2010-05-05 9:00 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2011-03-16 13:50 xen-unstable: " Juergen Gross
2011-03-16 14:45 ` Juergen Gross
2011-03-16 16:50 ` Keir Fraser
2011-03-17 5:52 ` Juergen Gross
2011-03-17 8:11 ` Keir Fraser
2011-03-17 8:59 ` Juergen Gross
2011-03-17 10:13 ` Jan Beulich
2011-03-17 10:29 ` Juergen Gross
2011-03-17 10:48 ` Jan Beulich
2011-03-17 10:55 ` Keir Fraser
2011-03-17 10:36 ` 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=4BE10624.7020505@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.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 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).