xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Michael A. Collins" <mike.a.collins@ark-net.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable stubdom build error version(3432abcf9380)
Date: Sat, 4 Feb 2012 07:19:01 +0100	[thread overview]
Message-ID: <1328336341.3610.2.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <000601cce2e8$af745ab0$0e5d1010$@ark-net.org>

On Fri, 2012-02-03 at 21:57 -0500, Michael A. Collins wrote:
> parent: 24691:3432abcf9380 tip
>  Fix x86_32 build
> branch: default
> commit: 4 modified, 1439 unknown
> update: (current)
> 
> /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c: In function âqemu_aio_waitâ:
> /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:20: error: macro "remove_waiter" requires 2 arguments, but only 1 given
> /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:5: error: âremove_waiterâ undeclared (first use in this function)
> /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:5: note: each undeclared identifier is reported only once for each function it appears in
> make[3]: *** [block-vbd.o] Error 1
> 
> [...]
> It appears to me that possibly I need to either add a queue like the
> above sys.c calls, or define a new macro that does not need a queue?

You needed to update your qemu tree with:
	$ make tools/qemu-xen-traditional-dir-force-update
We don't do this automatically because we are wary of blowing away
peoples local changes.

Of course cloning a new tree will have had the same effect.

Ian.


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

      parent reply	other threads:[~2012-02-04  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04  2:57 xen-unstable stubdom build error version(3432abcf9380) Michael A. Collins
2012-02-04  3:29 ` Michael A. Collins
2012-02-04  6:19 ` Ian Campbell [this message]

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=1328336341.3610.2.camel@cthulhu.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=mike.a.collins@ark-net.org \
    --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).