Hi,
qemu in trunk might not build on all architectures and optimization
settings
due to our gcc-4 (though we already patched it heavily).
The next qemu upstream update will work with any gcc-4.x or other
compiler due to the new TCG "technology".
In the meantme I use kvm anyway.
Neither qemu nor kvm does require a bit of xen - if the T2 dependencies
might indicate this then it's only due to some tested file or optional
extra
support. I did not check that - but I do not use Xen for ages and qemu
and
kvm build here.
Yours,
On 19.01.2009, at 10:19, [email protected] wrote:
Hi All,
Formerly (I can not find now the exact revision reference number,
but it
should have been something from last summer) I succeeded in building
qemu
0.9.1 without xen.
This time (trunk, rev 31768) I found that
1) qemu does not compile without xen, however I read on a related
forum
that xen in order to build from source needs qemu to be built already
2) xen (3.2.0) does not compile (due to the patch not finding the
file to
be patched) -> my first attemtps () to solve this were unsuccessful
Does anybody have suggestion for solving this? (I need only qemu,
possibly
no xen)
remark: the name for 'xen' in the package matrix is 'xen-tools'
which is
the same name of a collection of perl scripts for debian (related to
xen).
I personally was at the begining confusing these packages. Is there a
special reason for choosing this naming in T2?
best regards,
helasz
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
