All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: qemu-xen-unstable build error
Date: Fri, 28 May 2010 16:50:52 +0800	[thread overview]
Message-ID: <4BFF83EC.4010404@oracle.com> (raw)
In-Reply-To: <C8253A09.161EA%keir.fraser@eu.citrix.com>

On 05/28/2010 04:14 PM, Keir Fraser wrote:
> 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

I created soft links to the qemu-xen-unstable tree:

rwxrwxrwx  1 zhigang zhigang       12 2010-05-28 15:19 ioemu-dir -> ioemu-remote
lrwxrwxrwx  1 zhigang zhigang       23 2010-05-11 08:23 ioemu-remote ->
../../qemu-xen-unstable

So it will not checkout the tag.

Seems the QEMU_TAG hack is not a good enough. I'm wondering whether can we make
master always be compiled and rename QEMU_TAG to QEMU_BRANCH? All experimental
patches go to another branch and users set the QEMU_BRANCH for testing.

Thanks,

Zhigang

  reply	other threads:[~2010-05-28  8:50 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 [this message]
2010-05-28  8:55     ` Keir Fraser
2010-05-28  8:53   ` Jiang, Yunhong
2010-05-28  8:57     ` Keir Fraser
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=4BFF83EC.4010404@oracle.com \
    --to=zhigang.x.wang@oracle.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.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.