From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Build vmlinuz-2.6.29-rc5-tip Date: Mon, 23 Feb 2009 02:39:50 +0000 Message-ID: <49A20C76.7000602@eu.citrix.com> References: <310295.43521.qm@web56107.mail.re3.yahoo.com> <927395.41213.qm@web56108.mail.re3.yahoo.com> <499D971C.7020304@goop.org> <499EC52F.3080901@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Lyon Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , "bderzhavets@yahoo.com" , "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" List-Id: xen-devel@lists.xenproject.org Andrew Lyon wrote: > what is the correct technique for applying patches to ioemu-remote ? > the source doesn't exist until the build process is started, is it > possible to manually pull the source and then tell the build process > not to download it? > you can easily clone the qemu-xen repository manually from here: http://xenbits.xensource.com/git-http/qemu-xen-unstable.git apply your patches, then compile it: export XEN_ROOT=/path/to/xen-unstable.hg ./xen-setup make you'll find the compiled binary under i386-dm