From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: qemu-xen-unstable build error Date: Fri, 28 May 2010 09:55:40 +0100 Message-ID: References: <4BFF83EC.4010404@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BFF83EC.4010404@oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Zhigang Wang Cc: xen-devel , Ian Jackson List-Id: xen-devel@lists.xenproject.org On 28/05/2010 09:50, "Zhigang Wang" 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