xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Zhigang Wang <zhigang.x.wang@oracle.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: qemu-xen-unstable build error
Date: Fri, 28 May 2010 09:57:56 +0100	[thread overview]
Message-ID: <C8254424.16203%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E78DA02@shsmsx501.ccr.corp.intel.com>

Perhaps it should also check against QEMU_TAG if defined, even if the
directory exists, and pull/checkout if necessary.

 K.

On 28/05/2010 09:53, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

> I meet the issue just now. In the end I enter the ioemu-remote and do the
> branch/checkout manually.
> 
> When will the ioemu_remote be updated? Seems it will only be updated if this
> directory does not exist?
> 
>                 if [ ! -d ioemu-remote ]; then \
>                         rm -rf ioemu-remote ioemu-remote.tmp; \
>                         mkdir ioemu-remote.tmp; rmdir ioemu-remote.tmp; \
>                         $(GIT) clone $(CONFIG_QEMU) ioemu-remote.tmp; \
>                         if [ "$(QEMU_TAG)" ]; then                      \
>                                 cd ioemu-remote.tmp;                    \
>                                 $(GIT) branch -D dummy >/dev/null 2>&1 ||:; \
>                                 $(GIT) checkout -b dummy $(QEMU_TAG);   \
>                                 cd ..;                                  \
>                         fi;                                             \
>                         mv ioemu-remote.tmp ioemu-remote; \
> 
> Thanks
> --jyh
> 
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
>> Sent: Friday, May 28, 2010 4:15 PM
>> To: Zhigang Wang; Ian Jackson
>> Cc: xen-devel
>> Subject: Re: [Xen-devel] qemu-xen-unstable build error
>> 
>> On 28/05/2010 08:23, "Zhigang Wang" <zhigang.x.wang@oracle.com> wrote:
>> 
>>> Seems this commit is incomplete:
>>> 
>>> commit ffb0cf2ad55e952dae55e6166c4fcea79be6cd30
>>> Author: Ian Jackson <ian.jackson@eu.citrix.com>
>>> Date:   Thu Apr 15 17:01:15 2010 +0100
>>> 
>>>     Change callers of libxc to use new libxc API.
>>> 
>>>     Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
>>> 
>>> I cannot find the definition of xc_interface.
>>> 
>>> Checkout to commit 805ed3b20492d2f4bb465bfda65cedd286e23209 can finish the
>>> build.
>> 
>> Perhaps your build is not respecting the QEMU_TAG in Config.mk, for some
>> reason? There are (humungous) patches pending on xen-unstable.hg which will
>> introduce xc_interface.
>> 
>> -- Keir
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-05-28  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  7:23 qemu-xen-unstable build error Zhigang Wang
2010-05-28  8:14 ` Keir Fraser
2010-05-28  8:50   ` Zhigang Wang
2010-05-28  8:55     ` Keir Fraser
2010-05-28  8:53   ` Jiang, Yunhong
2010-05-28  8:57     ` Keir Fraser [this message]
2010-05-28  9:21       ` Jiang, Yunhong

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=C8254424.16203%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.com \
    --cc=zhigang.x.wang@oracle.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).