From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Ed Maste" <emaste@freebsd.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH 2/3] cirrus.yml: Compile macOS and FreeBSD with -Werror
Date: Fri, 24 Jul 2020 15:46:51 +0100 [thread overview]
Message-ID: <20200724144651.GG3146350@redhat.com> (raw)
In-Reply-To: <20200724143220.32751-3-thuth@redhat.com>
On Fri, Jul 24, 2020 at 04:32:19PM +0200, Thomas Huth wrote:
> Compiler warnings currently go unnoticed in our FreeBSD and macOS builds,
> since -Werror is only enabled for Linux and MinGW builds by default. So
> let's enable them here now, too.
> For macOS, that unfortunately means that we have to disable the vnc-sasl
> feature, since this is marked as deprecated in the macOS headers and thus
> generates a lot of deprecation warnings.
I wonder if its possible to add
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wdeprecated"
...
#pragma GCC diagnostic pop
to silence just one source file ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-07-24 14:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 14:32 [PATCH 0/3] Improve FreeBSD and macOS jobs in the Cirrus-CI Thomas Huth
2020-07-24 14:32 ` [PATCH 1/3] configure: Fix atomic64 test for --enable-werror on macOS Thomas Huth
2020-07-24 15:01 ` Christian Schoenebeck
2020-07-27 13:14 ` Alex Bennée
2020-07-24 14:32 ` [PATCH 2/3] cirrus.yml: Compile macOS and FreeBSD with -Werror Thomas Huth
2020-07-24 14:46 ` Daniel P. Berrangé [this message]
2020-07-24 16:46 ` Philippe Mathieu-Daudé
2020-07-24 16:49 ` Daniel P. Berrangé
2020-07-27 5:44 ` Thomas Huth
2020-07-27 8:30 ` Peter Maydell
2020-07-27 8:45 ` Thomas Huth
2020-07-24 16:50 ` Peter Maydell
2020-07-24 17:21 ` Christian Schoenebeck
2020-07-27 10:57 ` Daniel P. Berrangé
2020-07-28 6:43 ` Thomas Huth
2020-07-28 10:02 ` Daniel P. Berrangé
2020-07-24 15:01 ` Peter Maydell
2020-07-26 16:14 ` Ed Maste
2020-07-26 17:19 ` Christian Schoenebeck
2020-07-27 15:14 ` Thomas Huth
2020-07-24 14:32 ` [PATCH 3/3] cirrus.yml: Update the macOS jobs to Catalina Thomas Huth
2020-07-26 16:18 ` Ed Maste
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=20200724144651.GG3146350@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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.