From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default
Date: Fri, 13 Oct 2017 13:46:24 +0200 [thread overview]
Message-ID: <f43d6c1c-1112-bfcf-ae19-ed2a002b7873@redhat.com> (raw)
In-Reply-To: <20171013113859.GG20515@redhat.com>
On 13.10.2017 13:38, Daniel P. Berrange wrote:
> On Fri, Oct 13, 2017 at 12:55:40PM +0200, Thomas Huth wrote:
>> On 13.10.2017 12:52, Thomas Huth wrote:
[...]
>> By the way, looks like OpenBSD is also switching to clang by default soon:
>>
>> https://www.phoronix.com/scan.php?page=news_item&px=OpenBSD-Default-Clang
>
> In a few years time we could potentially revert this patch, but in the
> meantime it is clearly beneficial for anyone using OpenBSD and has no
> significant maint burden for us to carry it while there are widely
> supported OpenBSD releases which need it.
I disagree. If the next OpenBSD release uses Clang by default, we're not
building QEMU there with the *working default* C compiler anymore.
You're then rather forcing the OpenBSD users then to install an
additional (likely unliked, since GPLv3) GCC package on their systems.
So IMHO, just drop this patch and wait for the next OpenBSD release, and
the problem will be solved automatically. (and the few users who still
use an older release of OpenBSD will likely use the QEMU from their
ports system anyway)
Thomas
next prev parent reply other threads:[~2017-10-13 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 10:28 [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default Daniel P. Berrange
2017-10-13 10:52 ` Thomas Huth
2017-10-13 10:55 ` Thomas Huth
2017-10-13 11:38 ` Daniel P. Berrange
2017-10-13 11:46 ` Thomas Huth [this message]
2017-10-13 16:14 ` Peter Maydell
2017-10-16 14:47 ` Brad Smith
2017-10-16 7:44 ` Gerd Hoffmann
2017-10-16 10:14 ` Daniel P. Berrange
2017-10-13 11:37 ` Daniel P. Berrange
2017-11-06 14:25 ` Kamil Rytarowski
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=f43d6c1c-1112-bfcf-ae19-ed2a002b7873@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).