[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] building xen without mercury repository access


  • To: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 07 Feb 2008 08:18:46 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 07 Feb 2008 00:18:30 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchpYg8ITXusNtVVEdymTgAWy6hiGQ==
  • Thread-topic: [Xen-devel] building xen without mercury repository access

On 6/2/08 22:10, "Guillaume Rousse" <Guillaume.Rousse@xxxxxxxx> wrote:

> That:
> make[2]: entrant dans le répertoire «
> /home/guillomovitch/cooker/xen/BUILD/xen-3.2.0 »
> [..]
> Pulling changes from http://xenbits.xensource.com/linux-2.6.18-xen.hg
> into linux-2.6.18-xen.hg.
> pulling from http://xenbits.xensource.com/linux-2.6.18-xen.hg
> searching for changes
> no changes found

Yes, I was wrong. :-)

> However, I just found out than using the repository was just the default
> behaviour. The following env variables allow to use a local pristine
> kernel tarball:
> export XEN_LINUX_SOURCE=tarball
> export KETCHUP=/bin/true
> 
> It's just a bit difficult to grab in the makefile to find it :/

You can override them on the make command line.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.