From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Brad Smith" <brad@comstyle.com>, "Fam Zheng" <famz@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tests: vm: auto_install OpenBSD
Date: Fri, 24 Aug 2018 15:48:40 +0100 [thread overview]
Message-ID: <20180824144840.GV3430@redhat.com> (raw)
In-Reply-To: <CAFEAcA-r4CrL91gk0JhD4_iEZEOR=02Aa+noo3H3sed==P+6WQ@mail.gmail.com>
On Fri, Aug 24, 2018 at 03:46:31PM +0100, Peter Maydell wrote:
> On 24 August 2018 at 15:43, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > On Fri, Aug 24, 2018 at 10:36:30AM -0400, Brad Smith wrote:
> >> I very much appreciate the effort to bump up to 6.3 as I was going
> >> to suggest doing that at some point. But bumping up to 6.3 at the
> >> moment will fail with the configure script. We've switched from GCC 4.2
> >> to Clang. The TLS check will fail with Clang's emulated TLS. We've
> >> had a local patch for awhile to fix the test but I don't think it is
> >> appropriate to upstream as is.
> >>
> >> Index: configure
> >> --- configure.orig
> >> +++ configure
> >> @@ -1876,7 +1876,7 @@ static __thread int tls_var;
> >> int main(void) { return tls_var; }
> >> EOF
> >> -if ! compile_prog "-Werror" "" ; then
> >> +if ! compile_prog "-Werror" "-pthread" ; then
> >> error_exit "Your compiler does not support the __thread specifier for " \
> >> "Thread-Local Storage (TLS). Please upgrade to a version that does."
> >> fi
> >
> > Later on in the configure script there's a check for pthreads that
> > sets $PTHREAD_LIB to the desired arg.
> >
> > Best is probably to move that check higher up, and then use $PTHREAD_LIB
> > as the argument to the compile_prog call you show.
>
> Is emulated TLS a sufficiently complete/performant TLS
> implementation for our purposes?
>
> (I think it would be better if OpenBSD just implemented real TLS
> like every other host OS we support.)
My reading of the situation is that OpenBSD *does* support real TLS,
but our configure script failed to detect that it supported it,
due to missing "-pthread" arg.
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:[~2018-08-24 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 1:21 [Qemu-devel] [PATCH] tests: vm: auto_install OpenBSD Fam Zheng
2018-08-24 8:22 ` Daniel P. Berrangé
2018-08-24 8:52 ` Fam Zheng
2018-08-24 9:06 ` Peter Maydell
2018-08-24 9:47 ` Fam Zheng
2018-08-24 9:06 ` Daniel P. Berrangé
2018-08-24 14:36 ` Brad Smith
2018-08-24 14:43 ` Daniel P. Berrangé
2018-08-24 14:46 ` Peter Maydell
2018-08-24 14:48 ` Daniel P. Berrangé [this message]
2018-08-24 14:53 ` Peter Maydell
2018-08-24 22:13 ` Brad Smith
2018-08-27 9:05 ` Gerd Hoffmann
2018-09-05 12:54 ` Brad Smith
2018-09-05 14:24 ` Gerd Hoffmann
2018-09-05 14:43 ` Fam Zheng
2018-08-27 9:18 ` Fam Zheng
2018-08-27 13:48 ` Brad Smith
2018-09-05 12:56 ` Brad Smith
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=20180824144840.GV3430@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=famz@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 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.