From: G 3 <programmingkidx@gmail.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] macOS 10.12 Sierra, Xcode 8 & clock_gettime()
Date: Wed, 26 Oct 2016 11:32:35 -0400 [thread overview]
Message-ID: <C714D654-9C0E-4053-955C-F82E2FFD31F2@gmail.com> (raw)
In-Reply-To: <5A857D10-76C1-47CE-93C0-F4C67E2AD26C@livius.net>
On Oct 26, 2016, at 11:15 AM, Liviu Ionescu wrote:
>
>> On 26 Oct 2016, at 17:32, G 3 <programmingkidx@gmail.com> wrote:
>>
>> Maybe changing the base SDK from Mac OS 10.12 to say Mac OS 10.6
>> might fix the problem.
>
> any suggestion how to do this?
>
> for my linux and windows builds I use docker images, and I'm quite
> happy with this setup, it is stable and I get the same results
> regardless the environment I use to run the builds.
>
> unfortunately, for macOS, my development platform, I do not have a
> stable, fully controllable, build platform, and each time Apple
> updates the system I run into problems.
>
> currently deep inside Xcode 8 is OSX 10.12 SDK only, and I do not
> know how to install other versions.
>
> I'm considering a custom homebrew install, with all specific tools,
> but, as far as I know, this will not completely severe the links to
> the system libraries.
>
>
> so any suggestions on how to stick to a specific base SDK will be
> highly appreciated.
>
>
> regards,
>
> Liviu
I think the isysroot command-line option is what you would use.
Something like this: -isysroot /Developer/SDKs/MacOSX10.6.sdk
This link has some more info:
http://stackoverflow.com/questions/2279499/isysroot-or-sdkroot-problem
next prev parent reply other threads:[~2016-10-26 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12713.1477406219.22738.qemu-devel@nongnu.org>
2016-10-26 14:32 ` [Qemu-devel] macOS 10.12 Sierra, Xcode 8 & clock_gettime() G 3
2016-10-26 15:15 ` Liviu Ionescu
2016-10-26 15:32 ` G 3 [this message]
2016-10-26 15:39 ` Liviu Ionescu
2016-10-26 16:03 ` G 3
2016-10-25 9:43 Liviu Ionescu
2016-10-25 10:02 ` Peter Maydell
2016-10-25 10:34 ` Liviu Ionescu
2016-10-25 13:40 ` Liviu Ionescu
2016-10-25 11:40 ` Paolo Bonzini
2016-10-25 13:36 ` Liviu Ionescu
2016-10-25 13:48 ` Paolo Bonzini
2016-10-25 14:12 ` Liviu Ionescu
2016-10-25 14:21 ` Paolo Bonzini
2016-10-25 14:37 ` Liviu Ionescu
2016-10-25 14:38 ` 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=C714D654-9C0E-4053-955C-F82E2FFD31F2@gmail.com \
--to=programmingkidx@gmail.com \
--cc=ilg@livius.net \
--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 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).