Make kvm configure script and Makefile work again after things have been
moved around, so that you can do 'cd kvm ./configure' to get a
kvm-enabled qemu.
Also, guard against infinite recursion in case of 'cd' commands failing.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
--
On Thu, Apr
On Sun, Apr 26, 2009 at 10:38:39AM +0300, Michael S. Tsirkin wrote:
Make kvm configure script and Makefile work again after things have been
moved around, so that you can do 'cd kvm ./configure' to get a
kvm-enabled qemu.
Also, guard against infinite recursion in case of 'cd' commands
On Sun, Apr 26, 2009 at 10:48:20AM +0300, Gleb Natapov wrote:
On Sun, Apr 26, 2009 at 10:38:39AM +0300, Michael S. Tsirkin wrote:
Make kvm configure script and Makefile work again after things have been
moved around, so that you can do 'cd kvm ./configure' to get a
kvm-enabled qemu.
Also
for me running ./configure --kerneldir=/path/to/kernel at top dir works.
(/path/to/kernel should be absolute though, otherwise kernel include path
is incorrect).
Ah, I didn't realise kvm/cofigure is obsolete.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
Make kvm configure script and Makefile work again after things have been
moved around, so that you can do 'cd kvm ./configure' to get a
kvm-enabled qemu.
Also, guard against infinite recursion in case of 'cd' commands failing.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
--
On Thu, Apr
On Sun, Apr 26, 2009 at 10:38:39AM +0300, Michael S. Tsirkin wrote:
Make kvm configure script and Makefile work again after things have been
moved around, so that you can do 'cd kvm ./configure' to get a
kvm-enabled qemu.
Also, guard against infinite recursion in case of 'cd' commands
Also
for me running ./configure --kerneldir=/path/to/kernel at top dir works.
(/path/to/kernel should be absolute though, otherwise kernel include path
is incorrect).
Ah, I didn't realise kvm/cofigure is obsolete.
--
To unsubscribe from this list: send the line unsubscribe kvm-ppc in
the
