All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gihan Munasinghe <GMunasinghe@flexiant.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Compilation error on xen-unstable.hg
Date: Tue, 01 Jun 2010 15:47:42 +0100	[thread overview]
Message-ID: <4C051D8E.4030807@flexiant.com> (raw)

Guys

I just did a hg pull from
http://xenbits.xensource.com/xen-unstable.hg

also tried from

http://xenbits.xensource.com/staging/xen-unstable.hg

when I try to build the tools directory I am getting the following error

/xenunstable/xen-unstable.hg/tools/ioemu-dir/vl.c: In function ‘main’:
/xenunstable/xen-unstable.hg/tools/ioemu-dir/vl.c:5812: warning: 
implicit declaration of function ‘dma_helper_init’
/xenunstable/xen-unstable.hg/tools/ioemu-dir/vl.c:5814: error: too few 
arguments to function ‘xc_interface_open’
make[3]: *** [vl.o] Error 1
make[3]: Leaving directory 
`/root/xenunstable/xen-unstable.hg/tools/ioemu-remote/i386-dm'
make[2]: *** [subdir-i386-dm] Error 2
make[2]: Leaving directory 
`/root/xenunstable/xen-unstable.hg/tools/ioemu-remote


Problematic code segment is
dma_helper_init();
xc_handle = xc_interface_open();

I have no idea on "dma_helper_init()" warning but, the according to 
xenctrl.h the prototype for "xc_interface_open()" is defined as

xc_interface *xc_interface_open(xentoollog_logger *logger,
xentoollog_logger *dombuild_logger,
unsigned open_flags);


Is this due to some partially updated code been in the repository or am 
I doing something wrong..

Thanks
Gihan

             reply	other threads:[~2010-06-01 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 14:47 Gihan Munasinghe [this message]
2010-06-01 15:12 ` Compilation error on xen-unstable.hg 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=4C051D8E.4030807@flexiant.com \
    --to=gmunasinghe@flexiant.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.