| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] xen 4.1.0 rc1 build problem for local CONFIG_QEMU direct
M A Young writes ("Re: [Xen-devel] xen 4.1.0 rc1 build problem for local
CONFIG_QEMU directory"):
> CONFIG_QEMU ?= `pwd`/$(XEN_ROOT)/qemu-xen.git does work.
Thanks. Evidently you have your qemu-xen.git in the xen-unstable.hg
toplevel; the example puts it in the parent.
# HG changeset patch
# User Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
# Date 1296157360 0
# Node ID e429b133278b37fbb22a9afc2230e35f4bfcb9f3
# Parent c80960244942ddd67595885354bfdc42d1562b22
Config.mk: commented-out CONFIG_QEMU example now uses `pwd`/$(XEN_ROOT)
If you actually set it to a relative path, the qemu build breaks.
So this commented-out rune (an example) should arrange to be absolute.
Unfortunately XEN_ROOT is itself relative so the previous attempt to
fix this (22772:654563af359f) didn't work. So use `pwd`.
Tested-by: M A Young <m.a.young@xxxxxxxxxxxx>
Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
diff -r c80960244942 -r e429b133278b Config.mk
--- a/Config.mk Thu Jan 27 19:03:42 2011 +0000
+++ b/Config.mk Thu Jan 27 19:42:40 2011 +0000
@@ -182,7 +182,7 @@ endif
# Specify which qemu-dm to use. This may be `ioemu' to use the old
# Mercurial in-tree version, or a local directory, or a git URL.
-# CONFIG_QEMU ?= $(XEN_ROOT)/../qemu-xen.git
+# CONFIG_QEMU ?= `pwd`/$(XEN_ROOT)/../qemu-xen.git
CONFIG_QEMU ?= $(QEMU_REMOTE)
QEMU_TAG := xen-4.1.0-rc2
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home