Hide Forgot
Description of problem: Current rhel6-qemu-kvm fails to build when one does not specify --enable-spice due to dummy wrapper macros returning a value. This fails when the macro is called without storing the return value. cc1: warnings being treated as errors /home/jes/src/rhel6/qemu-kvm-rhel6/monitor.c: In function 'redhat_set_password': /home/jes/src/rhel6/qemu-kvm-rhel6/monitor.c:1397: error: statement with no effect Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fix: http://patchwork.ozlabs.org/patch/81327/
*** Bug 688037 has been marked as a duplicate of this bug. ***
Looks like commit 1c6074d107dff93c7c7b0edfb5da871504802946 added a dependency on spice. That wasn't intentional. Scheduling to fix for 6.3.
(In reply to comment #12) > Looks like commit 1c6074d107dff93c7c7b0edfb5da871504802946 added a dependency > on spice. That wasn't intentional. Scheduling to fix for 6.3. Hi,Gerd Would you please tell me your plan?as you mentioned,you patch added a dependency on spice.do you plan to revert this patch or reserve this patch? Would you please tell us in details?
Plan is to apply a patch which #ifdefs the spice bits with CONFIG_SPICE so no spice functions are called in case spice is disabled at compile time.
patch posted.
Verified this issue by the steps below: 1. git clone the latest qemu-kvm-rhel6 source code from ehabkost's tree 2. ./configure --disable-spice --enable-werror 3. make && make install Actual Result: No spice related warning or error prompts, qemu-system-x86_64 is installed correctly. So, this issue has been fixed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No Documentation Needed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0746.html