From mboxrd@z Thu Jan  1 00:00:00 1970
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Subject: Re: building xen without mercury repository access
Date: Mon, 11 Feb 2008 23:32:27 +0100
Message-ID: <47B0CCFB.30709@inria.fr>
References: <C3D06F66.137B3%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C3D06F66.137B3%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Keir Fraser a =E9crit :
>> However, I just found out than using the repository was just the defau=
lt
>> behaviour. The following env variables allow to use a local pristine
>> kernel tarball:
>> export XEN_LINUX_SOURCE=3Dtarball
>> export KETCHUP=3D/bin/true
>>
>> It's just a bit difficult to grab in the makefile to find it :/
I also found I had to explicitely use IMAGE_TARGET=3DbzImage, because
default value IMAGE_TARGET=3Dvmlinuz was wrong.

Anyway, using pristine kernel source tarball is not enough. How can I
fetch just the xen dom0 patchset against it ? cloning the whole
linux-2.6.18-xen.hg repository is a bit overkill for me (beside the
additional constraints of preventing network access during build).
--=20
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62