Bug 632707 - fix kvm build warnings and enable -Werror
fix kvm build warnings and enable -Werror
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm (Show other bugs)
5.6
All Linux
low Severity medium
: beta
: ---
Assigned To: Eduardo Habkost
Virtualization Bugs
:
Depends On:
Blocks: Rhel5KvmTier2
  Show dependency treegraph
 
Reported: 2010-09-10 15:02 EDT by Eduardo Habkost
Modified: 2011-01-13 18:37 EST (History)
5 users (show)

See Also:
Fixed In Version: kvm-83-211.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-13 18:37:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Eduardo Habkost 2010-09-10 15:02:47 EDT
There are many warnings on the current build of KVM, and this can make us miss other important warnings.

posix-aio-compat.c:185: warning: 'return' with a value, in function returning void
/builddir/build/BUILD/kvm-83-maint-snapshot-20090205/qemu/hw/virtio-net.c:283: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
/builddir/build/BUILD/kvm-83-maint-snapshot-20090205/qemu/hw/virtio-net.c:283: warning: format '%zd' expects type 'signed size_t', but argument 6 has type 'int'
main.c:494: warning: ignoring return value of 'write', declared with attribute warn_unused_result
kvmtrace.c:311: warning: ignoring return value of 'ftruncate', declared with attribute warn_unused_result

Version:
kvm-83-196.el5
Comment 16 errata-xmlrpc 2011-01-13 18:37:30 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0028.html

Note You need to log in before you can comment on or make changes to this bug.