From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
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: Mon, 16 Oct 2017 11:14:02 +0100 [thread overview]
Message-ID: <20171016101402.GE17583@redhat.com> (raw)
In-Reply-To: <1508139882.15782.2.camel@redhat.com>
On Mon, Oct 16, 2017 at 09:44:42AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > 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
>
> It did happen already. On openbsd 6.2 (released a week ago) cc is
> clang:
>
> $ cc --version
> OpenBSD clang version 4.0.0 (tags/RELEASE_400/final) (based on LLVM
> 4.0.0)
Oh, I didn't notice that was out already. Lets drop my patch and I'll
update the BSD page on the wiki
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:[~2017-10-16 10:14 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
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 [this message]
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=20171016101402.GE17583@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).