From: Tim Orling <timothy.t.orling@linux.intel.com>
To: Roger Smith <roger@sentientblue.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building on MacOS X
Date: Sat, 14 Jan 2017 11:49:55 -0800 [thread overview]
Message-ID: <6694C76C-B48D-48A1-AEFB-A3B458279EC6@linux.intel.com> (raw)
In-Reply-To: <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com>
[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]
> On Jan 14, 2017, at 11:45 AM, Roger Smith <roger@sentientblue.com> wrote:
>
>>
>> On Jan 13, 2017, at 12:50 AM, Clemens Lang <Clemens.Lang@bmw-carit.de> wrote:
>>
>> Hi,
>>
>>
>>> On 12 Jan 2017, at 23:59, Mark Hatle <mark.hatle@windriver.com> wrote:
>>>
>>> As far as I know pseudo and the security introduced in 10.11 that affect
>>> preloading is likely the biggest technical problem... everything else is just
>>> "it's not Linux”.
>>
>> With System Integrity Protection disabled, pseudo should still work as it did before, if that’s an acceptable step for you.
>>
>> If it isn’t, Apple’s new limitations can also be worked around in pseudo by hooking the exec(2) and posix_spawn(2) syscalls, checking if the binary to be executed is under system integrity protection, making a copy without the SIP-bit if it is and transparently running that copy instead. That code would need to be written, though (Let me know if you want to do that, I have the code for a different project.). It’s probably only a matter of time until Apple prevents that from working, too, though, e.g. by making some standard system tools signed binaries that no longer load preloaded libraries.
>>
>>
>
>
> This topic could have been clarified better, since there are multiple ways to “build” Yocto Project in MacOS X,
>
> Is Building Yocto project on a POSIX system, a desire for the Yocto project? It would allow support on all bsd UNIX’s including macOS
>
Many of us use Mac laptops for development, so I think the answer is yes. As Mark mentioned, it has been an issue of time and resources. We would welcome patches :)
>
> There are many teams inside Apple that use Linux systems for one reason or another. They would appreciate building open source tools out the door without some other additional overhead..
>
> Replacing a platforms POSIX version of tools with gnu versions because your build environment didn’t like it, seems like a step backwards for these types of initiatives.
>
> Curious to know about long term support for POSIX systems.
>
> Apple spent alot of time and effor years ago to vertify OS X as POSIX compliant.
>
> Roger
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
[-- Attachment #2: Type: text/html, Size: 14743 bytes --]
next prev parent reply other threads:[~2017-01-14 19:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 15:14 Building on MacOS X Roger Smith
2017-01-12 15:34 ` Burton, Ross
2017-01-12 15:39 ` Tim Orling
2017-01-12 15:42 ` Burton, Ross
2017-01-12 16:21 ` Belisko Marek
2017-01-12 16:27 ` Khem Raj
2017-01-12 16:50 ` Andrea Galbusera
2017-01-12 17:41 ` Roger Smith
2017-01-12 17:47 ` Burton, Ross
2017-01-12 22:59 ` Mark Hatle
2017-01-13 8:50 ` Clemens Lang
2017-01-14 19:45 ` Roger Smith
2017-01-14 19:49 ` Tim Orling [this message]
2017-01-16 11:19 ` Burton, Ross
2017-01-17 2:33 ` Brian Avery
2017-01-12 22:32 ` Tim Orling
2017-01-12 17:55 ` Maciej Borzęcki
2017-01-12 18:03 ` Burton, Ross
2017-01-12 18:12 ` Andrea Galbusera
2017-01-12 18:43 ` Maciej Borzęcki
2017-01-12 22:16 ` Tim Orling
2017-01-12 15:38 ` Mark Hatle
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=6694C76C-B48D-48A1-AEFB-A3B458279EC6@linux.intel.com \
--to=timothy.t.orling@linux.intel.com \
--cc=roger@sentientblue.com \
--cc=yocto@yoctoproject.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.