[Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Michael Renzmann
Hi. The compilation of the latest qemu CVS version aborted due to a missing texi2html package. In my opinion, the build shouldn't depend on texi2html and pod2man. I suggest to make the documentation optional and warn the user if any of the necessary tools are missing. The attached patch modifies

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Michael Renzmann
Hi again. On Fri, 2006-02-10 at 08:43 +0100, Michael Renzmann wrote: The attached patch ... ... contained some stuff that should have been ignored by diff. Sorry, revised patch attached to this mail. Bye, Mike diff -urN qemu-cvs/Makefile qemu-cvs-o42/Makefile --- qemu-cvs/Makefile 2006-02-08

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Bernhard Fischer
On Fri, Feb 10, 2006 at 08:48:39AM +0100, Michael Renzmann wrote: Hi again. On Fri, 2006-02-10 at 08:43 +0100, Michael Renzmann wrote: The attached patch ... ... contained some stuff that should have been ignored by diff. Sorry, revised patch attached to this mail. diff -urN qemu-cvs/Makefile

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Michael Renzmann
Hi. On Fri, 2006-02-10 at 09:54 +0100, Bernhard Fischer wrote: What about just doing this -install -m 644 qemu-doc.html qemu-tech.html $(docdir) That would work, but the user won't be noticed of the fact that parts of the documentation isn't generated. Bye, Mike

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Bernhard Fischer
On Fri, Feb 10, 2006 at 09:59:55AM +0100, Michael Renzmann wrote: Hi. On Fri, 2006-02-10 at 09:54 +0100, Bernhard Fischer wrote: What about just doing this -install -m 644 qemu-doc.html qemu-tech.html $(docdir) That would work, but the user won't be noticed of the fact that parts of the

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Michael Renzmann
Hi. On Fri, 2006-02-10 at 10:33 +0100, Bernhard Fischer wrote: That would work, but the user won't be noticed of the fact that parts of the documentation isn't generated. Not quite, you'll get texi2html -monolithic etc failed make: Error (ignored) and the build will move on. Uhm... yeah,

[Qemu-devel] [PATCH] distclean target: remove config-host-kqemu.mak

2006-02-10 Thread Michael Renzmann
Hi. The attached trivial patch for current CVS adds config-host-kqemu.mak to the list of removed files in the distclean target. Bye, Mike Index: Makefile === --- Makefile (revision 4) +++ Makefile (working copy) @@ -35,7 +35,7 @@

Re: [Qemu-devel] [PATCH][RFC] Make documentation optional

2006-02-10 Thread Sylvain Petreolle
The user still wont know the documentation has failed, or he will have to search through the build logs. --- Bernhard Fischer [EMAIL PROTECTED] a écrit : On Fri, Feb 10, 2006 at 09:59:55AM +0100, Michael Renzmann wrote: Hi. On Fri, 2006-02-10 at 09:54 +0100, Bernhard Fischer wrote: What

Re: [Qemu-devel] -kernel-kqemu

2006-02-10 Thread Christian MICHON
On 2/9/06, Jim C. Brown wrote: This sounds like an interesting option. Qemu has moved one step closer to VMware... It hangs my XP host with 100% cpu eaten up, no way to stop qemu, or kqemu. I have to reboot, and my linux clients freezes very early Src=CVS (yesterday 09/02/2006)

Re: [Qemu-devel] -kernel-kqemu

2006-02-10 Thread Jim C. Brown
On Fri, Feb 10, 2006 at 02:29:39PM +0100, Christian MICHON wrote: On 2/9/06, Jim C. Brown wrote: This sounds like an interesting option. Qemu has moved one step closer to VMware... It hangs my XP host with 100% cpu eaten up, no way to stop qemu, or kqemu. I have to reboot, and my linux

Re: [Qemu-devel] -kernel-kqemu

2006-02-10 Thread Kazu
Sent: Friday, February 10, 2006 7:01 AM Fabrice Bellard wrote: Hi, I will update the documentation about -kernel-kqemu soon. To be short: as some people already noticed, this option allows to run user code and most of the kernel code on bare metal. The result is usually a noticable speed

Re: [Qemu-devel] Re: Some patches for qemu on sparc

2006-02-10 Thread Paul Brook
Thanks for your feedback. I've added additional check to dyngen.c, which checks that function has either save; in the beginning and ret; restore; in the end, or ends in retl; nop;. That allowed me to get past the arm target build failure. Now it fails (during dyngen check) on ppc target, the