From: Brad Smith <brad@comstyle.com>
To: Peter Maydell <peter.maydell@linaro.org>, Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: pick the right compiler for OpenBSD by default
Date: Mon, 16 Oct 2017 10:47:49 -0400 [thread overview]
Message-ID: <8b4e9396-bbef-cd14-2127-d387e7d024cc@comstyle.com> (raw)
In-Reply-To: <CAFEAcA_Jmh-UyHDtMM+yzG_3Y1eJPzPmr9ATBQp3j_-1a4U7wQ@mail.gmail.com>
On 10/13/2017 12:14 PM, Peter Maydell wrote:
> On 13 October 2017 at 12:46, Thomas Huth<thuth@redhat.com> wrote:
>> 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)
> Another possible approach would be to have a configure test
> for whatever feature it is that we need in our compiler,
> and then run through a list that starts with "cc" and
> goes on to try "egcc" etc until it finds one that works.
> That way we'll automatically DTRT when OpenBSD upgrades
> their "cc" to a working one.
The release is already out.
One issue that needs to be fixed in the configure script. Have the TLS test
link with libpthread if the initial test fails.
next prev parent reply other threads:[~2017-10-16 14:48 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 [this message]
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=8b4e9396-bbef-cd14-2127-d387e7d024cc@comstyle.com \
--to=brad@comstyle.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 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.