From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Ed Maste" <emaste@freebsd.org>, "Thomas Huth" <thuth@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.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: Sun, 26 Jul 2020 19:19:03 +0200 [thread overview]
Message-ID: <2063507.Rj2kWPf9UF@silver> (raw)
In-Reply-To: <CAPyFy2A-7gLhsCAdAohdnm9BDcHyR2y7EZK2nAKTkp0zYtYC9w@mail.gmail.com>
On Sonntag, 26. Juli 2020 18:14:11 CEST Ed Maste wrote:
> On Fri, 24 Jul 2020 at 10:32, Thomas Huth <thuth@redhat.com> 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.
>
> Reviewed-by: Ed Maste <emaste@freebsd.org>
>
> for the FreeBSD change; I'm indifferent on which method is used to
> address the macos deprecation warnings.
Like I pointed out on my response to Peter, it is a bit risky to just blindly
link against Apple's version of sasl on macOS. Say you compile qemu on a
certain macOS version, then you run qemu again after an update of macOS
without recompiling qemu, chances are that you get misbehaviours.
One solution would be bundling the qemu app along with sasl, so qemu would be
forced to use that bundled sasl version instead of whatever Apple's version of
sasl is installed on the system.
Another appraoch would be checking the system's sasl version on qemu startup
by calling either sasl_version() or sasl_version_info() and comparing that
with the version qemu was compiled with, and erroring out on doubt.
Or obvious last option: simply taking the risk by ignoring this potential
issue. The SASL headers are still made available by Apple, which suggests that
they don't break SASL 'too often'.
Your choice. ;-)
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2020-07-26 17:19 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é
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 [this message]
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=2063507.Rj2kWPf9UF@silver \
--to=qemu_oss@crudebyte.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).