From: Peter Maydell <peter.maydell@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-doc.texi: Add information on compiling source code on Mac OS X
Date: Sat, 8 Aug 2015 00:13:23 +0100 [thread overview]
Message-ID: <CAFEAcA8L5eQdmJSppGf48ja5=ytadii5s61p6OOLSvSXz49qwQ@mail.gmail.com> (raw)
In-Reply-To: <A4B0AA72-0484-4A8F-B783-9EBB67ECA1C8@gmail.com>
On 7 August 2015 at 21:32, Programmingkid <programmingkidx@gmail.com> wrote:
>
> On Aug 7, 2015, at 1:00 PM, Peter Maydell wrote:
>> (https://trac.macports.org/wiki/UsingTheRightCompiler
>> suggests that XCode 3.2 for OSX 10.6 provided a non-default
>> 'clang'; I don't have a 10.6 + 3.2 system to check whether that
>> clang will build QEMU though. If it does then we should
>> recommend using it rather than building gcc. 10.5 users
>> are definitely stuck with finding or building a non-Apple
>> compiler, though.)
>
> I just checked and my system does include clang. Didn't even know
> about it. Too bad it didn't work to compile QEMU. It doesn't support
> Thread-Local Storage. It is probably too old (version 3.0).
Thanks for testing that -- you're running OSX 10.6, right?
I guess the TLS stuff got added to clang for the version
that's in Xcode 4.2. So it looks like we have a fairly
straightforward
* 10.5 and 10.6 -> compile a gcc or download a third-party build
* 10.7 and above -> use Xcode's clang
division.
-- PMM
next prev parent reply other threads:[~2015-08-07 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 15:35 [Qemu-devel] [PATCH] qemu-doc.texi: Add information on compiling source code on Mac OS X Programmingkid
2015-08-07 17:00 ` Peter Maydell
2015-08-07 20:32 ` Programmingkid
2015-08-07 23:13 ` Peter Maydell [this message]
2015-08-08 1:06 ` Programmingkid
2015-08-07 20:57 ` [Qemu-devel] [PATCH v2] " Programmingkid
2015-08-14 15:16 ` Peter Maydell
2015-08-14 16:09 ` Programmingkid
2015-08-14 16:28 ` Peter Maydell
2015-08-14 16:45 ` Programmingkid
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='CAFEAcA8L5eQdmJSppGf48ja5=ytadii5s61p6OOLSvSXz49qwQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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 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).