From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developer <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH for 2.6] configure: Allow builds -Weverything
Date: Mon, 16 May 2016 15:06:09 +0200 [thread overview]
Message-ID: <5739C5C1.20201@redhat.com> (raw)
In-Reply-To: <5739BDE3.5030301@weilnetz.de>
[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]
On 16/05/2016 14:32, Stefan Weil wrote:
> Am 16.05.2016 um 14:22 schrieb Paolo Bonzini:
>>
>>
>> On 16/05/2016 13:27, Stefan Weil wrote:
>>> I think this patch which was too late for 2.6.0 is a candidate for
>>> qemu-trivial, maybe also for qemu-stable. CC both mailing lists.
>>
>> Yes, it is confusing to have --disable-werror compilations break because
>> of warnings becoming errors. However, the subject is imprecise, what about:
>>
>> ----
>> configure: Allow builds with extra warnings
>>
>> The clang compiler supports a useful compiler option -Weverything,
>> and GCC also has other warnings not enabled by -Wall.
>>
>> If glib header files trigger a warning, however, testing glib with
>> -Werror will always fail. A size mismatch is also detected without
>> -Werror, so simply remove it.
>> ----
>>
>> Thanks,
>>
>> Paolo
>
>
> Yes, that's a better description. Maybe Michael can use it when
> applying the patch.
I'm sending a pull request with all sort of patches in a couple days, I
can include this one too.
Paolo
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developer <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 2.6] configure: Allow builds -Weverything
Date: Mon, 16 May 2016 15:06:09 +0200 [thread overview]
Message-ID: <5739C5C1.20201@redhat.com> (raw)
In-Reply-To: <5739BDE3.5030301@weilnetz.de>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On 16/05/2016 14:32, Stefan Weil wrote:
> Am 16.05.2016 um 14:22 schrieb Paolo Bonzini:
>>
>>
>> On 16/05/2016 13:27, Stefan Weil wrote:
>>> I think this patch which was too late for 2.6.0 is a candidate for
>>> qemu-trivial, maybe also for qemu-stable. CC both mailing lists.
>>
>> Yes, it is confusing to have --disable-werror compilations break because
>> of warnings becoming errors. However, the subject is imprecise, what about:
>>
>> ----
>> configure: Allow builds with extra warnings
>>
>> The clang compiler supports a useful compiler option -Weverything,
>> and GCC also has other warnings not enabled by -Wall.
>>
>> If glib header files trigger a warning, however, testing glib with
>> -Werror will always fail. A size mismatch is also detected without
>> -Werror, so simply remove it.
>> ----
>>
>> Thanks,
>>
>> Paolo
>
>
> Yes, that's a better description. Maybe Michael can use it when
> applying the patch.
I'm sending a pull request with all sort of patches in a couple days, I
can include this one too.
Paolo
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-16 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 21:33 [Qemu-devel] [PATCH for 2.6] configure: Allow builds -Weverything Stefan Weil
2016-04-29 8:29 ` Daniel P. Berrange
2016-04-29 8:51 ` Peter Maydell
2016-04-29 9:22 ` Stefan Weil
2016-05-16 11:27 ` [Qemu-trivial] " Stefan Weil
2016-05-16 11:27 ` [Qemu-devel] " Stefan Weil
2016-05-16 12:22 ` [Qemu-trivial] " Paolo Bonzini
2016-05-16 12:22 ` [Qemu-devel] " Paolo Bonzini
2016-05-16 12:32 ` [Qemu-trivial] " Stefan Weil
2016-05-16 12:32 ` [Qemu-devel] " Stefan Weil
2016-05-16 13:06 ` Paolo Bonzini [this message]
2016-05-16 13:06 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5739C5C1.20201@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.