From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Ed Maste" <emaste@freebsd.org>, "Li-Wen Hsu" <lwhsu@freebsd.org>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: [PATCH v2 0/4] Improve FreeBSD and macOS jobs in the Cirrus-CI
Date: Tue, 28 Jul 2020 09:44:01 +0200 [thread overview]
Message-ID: <20200728074405.13118-1-thuth@redhat.com> (raw)
Our configure script does not enable -Werror on macOS and FreeBSD
by default yet. That's bad in the CI, since we might miss compiler
warnings and thus bugs this way. So after fixing a problem in the
configure script in the first patch, we now turn on -Werror here
in the second and third patch. The fourth patch is just a cosmetical
one, since Cirrus-CI seems to upgrade all jobs automatically to
Cataline these days.
v2:
- Split the -Werror enablement patch into two, one for FreeBSD and
one for macOS
- Use -Wno-error=deprecated-declarations instead of --disable-sasl
on macOS to work-around the deprecation messages from Apple.
Thomas Huth (4):
configure: Fix atomic64 test for --enable-werror on macOS
cirrus.yml: Compile FreeBSD with -Werror
cirrus.yml: Compile macOS with -Werror
cirrus.yml: Update the macOS jobs to Catalina
.cirrus.yml | 13 ++++++++-----
configure | 10 +++++-----
2 files changed, 13 insertions(+), 10 deletions(-)
--
2.18.1
next reply other threads:[~2020-07-28 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 7:44 Thomas Huth [this message]
2020-07-28 7:44 ` [PATCH v2 1/4] configure: Fix atomic64 test for --enable-werror on macOS Thomas Huth
2020-07-28 7:44 ` [PATCH v2 2/4] cirrus.yml: Compile FreeBSD with -Werror Thomas Huth
2020-07-28 10:05 ` Daniel P. Berrangé
2020-07-28 7:44 ` [PATCH v2 3/4] cirrus.yml: Compile macOS " Thomas Huth
2020-07-28 10:04 ` Daniel P. Berrangé
2020-07-28 7:44 ` [PATCH v2 4/4] cirrus.yml: Update the macOS jobs to Catalina Thomas Huth
2020-07-28 10:04 ` Daniel P. Berrangé
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=20200728074405.13118-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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.