From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Cc: xen-devel@lists.xensource.com
Subject: Re: building xen without mercury repository access
Date: Mon, 11 Feb 2008 23:32:27 +0100 [thread overview]
Message-ID: <47B0CCFB.30709@inria.fr> (raw)
In-Reply-To: <C3D06F66.137B3%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser a écrit :
>> 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 :/
I also found I had to explicitely use IMAGE_TARGET=bzImage, because
default value IMAGE_TARGET=vmlinuz 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).
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
next prev parent reply other threads:[~2008-02-11 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 17:54 building xen without mercury repository access Guillaume Rousse
2008-02-05 19:08 ` Keir Fraser
2008-02-06 22:10 ` Guillaume Rousse
2008-02-07 8:18 ` Keir Fraser
2008-02-07 9:17 ` Guillaume Rousse
2008-02-07 10:33 ` Yves-Gaël Chény
2008-02-11 22:32 ` Guillaume Rousse [this message]
2008-02-11 22:40 ` Valter Douglas Lisbôa Jr.
2008-02-11 23:10 ` Keir Fraser
2008-02-12 10:27 ` Ian Jackson
2008-02-12 10:43 ` Guillaume Rousse
2008-02-12 10:46 ` Keir Fraser
2008-02-12 11:02 ` Ian Jackson
2008-02-12 11:25 ` Maximilian Wilhelm
2008-02-12 11:34 ` Keir Fraser
2008-02-13 9:30 ` Guillaume Rousse
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=47B0CCFB.30709@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=xen-devel@lists.xensource.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.