|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] xen 4.1.0 rc1 build problem for local CONFIG_QEMU	direct
 
M A Young writes ("[Xen-devel] xen 4.1.0 rc1 build problem for local 
CONFIG_QEMU directory"):
> The problem is that (in tools/Makefile) if CONFIG_QEMU is a directory 
> (when tested from tools) then QEMU_ROOT is set to this. Then the script 
> goes into the ioemu-dir directory and runs $(QEMU_ROOT)/xen-setup . 
> Unfortunately QEMU_ROOT is relative to tools not tools/ioemu-dir and 
> things break. If you hack around this by adding and extra ../ to QEMU_ROOT 
> it fails later because symbolic links created later on such as 
> ioemu-dir/i386-dm/Makefile don't work.
Thanks.  I have improved this.
Ian.
# HG changeset patch
# User Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
# Date 1295286912 0
# Node ID 654563af359ff8287419ee4f5248f236565542d1
# Parent  726c616fca5eead370ca29f733362d44fe413ca9
Config.mk: commented-out CONFIG_QEMU example now uses 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.
Reported-by: M A Young <m.a.young@xxxxxxxxxxxx>
Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
diff -r 726c616fca5e -r 654563af359f Config.mk
--- a/Config.mk Mon Jan 17 17:52:39 2011 +0000
+++ b/Config.mk Mon Jan 17 17:55:12 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 ?= ../qemu-xen.git
+# CONFIG_QEMU ?= $(XEN_ROOT)/../qemu-xen.git
 CONFIG_QEMU ?= $(QEMU_REMOTE)
 
 QEMU_TAG := xen-4.1.0-rc1
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 |   
 
 | 
    | 
  
  
    |   | 
    |