From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Zhigang Wang <zhigang.x.wang@oracle.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 09:55:40 +0100 [thread overview]
Message-ID: <C825439C.161FF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BFF83EC.4010404@oracle.com>
On 28/05/2010 09:50, "Zhigang Wang" <zhigang.x.wang@oracle.com> wrote:
> 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.
Yes, I do similar (well, I specify CONFIG_QEMU) and so QEMU_TAG does nothing
much for me also. Generally I find the build breaks rarely enough that I've
never bothered to change things.
> 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.
Perhaps if CONFIG_QEMU is specified then the build system should clone from
the local repository, or copy it (which is presumably fast) and then do a
private checkout in that clone/copy, so that QEMU_TAG is always respected.
Getting the right qemu version is a bit of a crapshoot right now.
-- Keir
next prev parent reply other threads:[~2010-05-28 8:55 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 [this message]
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=C825439C.161FF%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.