qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h h


From: Andreas Färber
Subject: Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...)
Date: Fri, 27 Jul 2007 20:54:49 +0200


Am 27.07.2007 um 16:58 schrieb Sunil Amitkumar Janki:

Dan Shearer wrote:
I see this as a different class of testing
[...], checking out and compiling
under different circumstances. That's very valuable, and will help
address a problem that drives away a lot of potential QEMU users - they
just can't compile it.

That would be great. I am regularly compiling and using QEMU CVS
snapshots because features get added all the time. A lot of the time
it happens that these build fine on x86 whereas they don't work on
other architectures because the developers don't have access to those.

I have been running self-built Slackware 12.0 on MIPS for the last
few months and would like to run QEMU on that architecture. previously
it built but didn't run, but now it doesn't even compile anymore. The
error message I get is the following: [...]

I recently reported build failure of the ppc target on OS X due to an unsupported GCC feature but no-one has shown any interest in fixing it, neither applying my workaround patch nor proposing a different solution.

It's a strange phenomenon that many other open source projects don't suffer - qemu seems to expect everyone to patch it herself instead of fixing problems in the repository at their origin. Major example being qemu clinging on to GCC 3.x instead of supporting both 3 and 4 by updating and integrating the existing patches that worked for 0.9.0.

Andreas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]