From: Programmingkid <programmingkidx@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-coroutine.c: error: thread-local storage not supported for this target
Date: Fri, 23 Jan 2015 17:54:11 -0500 [thread overview]
Message-ID: <6EF0A76B-7542-4045-B983-19076069A7F0@gmail.com> (raw)
In-Reply-To: <54C2C199.3060607@redhat.com>
On Jan 23, 2015, at 4:48 PM, Paolo Bonzini wrote:
>
>
> On 23/01/2015 22:37, Paolo Bonzini wrote:
>>
>>
>> On 23/01/2015 22:33, Programmingkid wrote:
>>>> Use clang then.
>>>
>>> Could you provide directions on how you want me to do this? In the configure options, this was all I found:
>>> --objcc=OBJCC use Objective-C compiler OBJCC [clang]
>>
>> ./configure --cc=clang --cxx=clang++
>>
>> But QEMU uses "cc" and "c++" by default, not "gcc" and "g++", and on Mac
>> OS X "cc" and "c++" should be clang. So "./configure" should just work.
>
> Sorry, I was wrong. I missed that you are using 10.6.x.
>
> Thread-local storage was introduced on Mac OS X in 10.7. For 10.6.x
> you'll have to compile GCC 4.3 or newer yourself (or take it from
> fink/homebrew/whatever the Mac folks use these days).
>
The code that causes this problem needs to be #ifdef'ed. I'm just not sure what the problem code is.
next prev parent reply other threads:[~2015-01-23 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 19:27 [Qemu-devel] qemu-coroutine.c: error: thread-local storage not supported for this target Programmingkid
2015-01-23 20:33 ` Paolo Bonzini
2015-01-23 20:39 ` Programmingkid
2015-01-23 20:55 ` Paolo Bonzini
2015-01-23 21:33 ` Programmingkid
2015-01-23 21:37 ` Paolo Bonzini
2015-01-23 21:48 ` Paolo Bonzini
2015-01-23 22:54 ` Programmingkid [this message]
2015-01-24 18:54 ` Paolo Bonzini
2015-01-24 19:33 ` Peter Maydell
2015-01-24 19:59 ` Paolo Bonzini
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=6EF0A76B-7542-4045-B983-19076069A7F0@gmail.com \
--to=programmingkidx@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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.