qemu: explicitly disable xen support
PATCH 1/1 qemu: explicitly disable xen support
We don't make use of xen and when building on Ubuntu 13.04 when libxen-dev is installed on the build host you will get errors like the following:
| /usr/include/x86_64-linux-gnu/bits/string3.h:81: warning: memset used with constant zero length parameter; this could be due to transposed parameters | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_alone_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_code@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_stream_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_end@XZ_5.0'
This change disables xen for both -native and target packages but since it is a PACKAGECONFIG a user could tune this to have xen support in the target package.
--- meta/recipes-devtools/qemu/qemu.inc | 1 + 1 file changed, 1 insertion(+)
meta/recipes-devtools/qemu/qemu.inc +1 -0
@@ -79,6 +79,7 @@ do_install_append() { PACKAGECONFIG ??= "" PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap attr," PACKAGECONFIG[aio] = "--enable-linux-aio,--disable-linux-aio,libaio," +PACKAGECONFIG[xen] = "--enable-xen, --disable-xen,," # Qemu target will not build in world build for ARM or Mips BROKEN_qemuarm = "1"
Signature · 1 line
1.8.4.1
Quoted 25 lines · Ming Liu
We don't make use of xen and when building on Ubuntu 13.04 when libxen-dev is installed on the build host you will get errors like the following:
| /usr/include/x86_64-linux-gnu/bits/string3.h:81: warning: memset used with constant zero length parameter; this could be due to transposed parameters | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_alone_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_code@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_stream_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_end@XZ_5.0'This change disables xen for both -native and target packages but since it is a PACKAGECONFIG a user could tune this to have xen support in the target package.
Signed-off-by Mark Asselstine <[email protected]>Signed-off-by Ming Liu <[email protected]>--- meta/recipes-devtools/qemu/qemu.inc | 1 + 1 file changed, 1 insertion(+)meta/recipes-devtools/qemu/qemu.inc +0
-0
meta/recipes-devtools/qemu/qemu.inc do_install_append() { · line 83
Quoted 5 lines
meta/recipes-devtools/qemu/qemu.inc +1
-0@@ -79,6 +79,7 @@ do_install_append() { PACKAGECONFIG ??= "" PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap attr," PACKAGECONFIG[aio] = "--enable-linux-aio,--disable-linux-aio,libaio," +PACKAGECONFIG[xen] = "--enable-xen, --disable-xen,,"
If enabled what dependencies or rdepends does it need? liblzma seems like it might be one.
Sau!
Quoted 3 lines
meta/recipes-devtools/qemu/qemu.inc +0
-0# Qemu target will not build in world build for ARM or Mips BROKEN_qemuarm = "1"
Quoted 21 lines · Saul Wold
Quoted 20 lines · Ming Liu
We don't make use of xen and when building on Ubuntu 13.04 when libxen-dev is installed on the build host you will get errors like the following:
| /usr/include/x86_64-linux-gnu/bits/string3.h:81: warning: memset used with constant zero length parameter; this could be due to transposed parameters | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_alone_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_code@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_stream_decoder@XZ_5.0' | /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libxenguest.so: undefined reference to `lzma_end@XZ_5.0'This change disables xen for both -native and target packages but since it is a PACKAGECONFIG a user could tune this to have xen support in the target package.
Signed-off-by Mark Asselstine <[email protected]>Signed-off-by Ming Liu <[email protected]>--- meta/recipes-devtools/qemu/qemu.inc | 1 + 1 file changed, 1 insertion(+)
Quoted 12 lines
meta/recipes-devtools/qemu/qemu.inc do_install_append() { · line 83
Quoted 11 lines
meta/recipes-devtools/qemu/qemu.inc +1
-1@@ -79,6 +79,7 @@ do_install_append() { PACKAGECONFIG ??= "" PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap attr," PACKAGECONFIG[aio] = "--enable-linux-aio,--disable-linux-aio,libaio," +PACKAGECONFIG[xen] = "--enable-xen, --disable-xen,,"If enabled what dependencies or rdepends does it need? liblzma seems like it might be one.
I'd like to explain it in more detail, there is no dependency relationship between them actually, and we don't need set any rdepends for it.
The root cause is that when xen support is detected by qemu configure, "-lxenstore" is added to LDFLAGS, but mostly libxenstore.so itself on host is also compiled as a shared library, so it is linked to liblzma.so of host path, which will lead a version mismatch with lzma in sysroot.
//Ming Liu
Quoted 8 lines
Sau!
Quoted 3 lines
meta/recipes-devtools/qemu/qemu.inc +0
-0# Qemu target will not build in world build for ARM or Mips BROKEN_qemuarm = "1"