= On 12 January 2017 at 17:41, Roger Smith <roger@sentientblue.com&= gt; wrote:

As I mentioned, I = tried to simply source the oe-init-build-env, and got an error that the rea= dlink command that yocto is using is incompatible with the bsd version of r= eadlink built into os x.=C2=A0

Yes, = we assume GNU tools.=C2=A0 That was the first step I posted: use brew to in= stall gnu awk/coreutils/etc etc.=C2=A0 But thats also the easy bit...

Ross

<= /div> --001a1147603262a2f30545e9500c-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 9BD15E009BA; Thu, 12 Jan 2017 09:56:14 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.46 listed in list.dnswl.org] * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [74.125.82.46 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 12403E0088B for ; Thu, 12 Jan 2017 09:56:02 -0800 (PST) Received: by mail-wm0-f46.google.com with SMTP id r126so30651230wmr.0 for ; Thu, 12 Jan 2017 09:56:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rndity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ldf+qDPVj9YB70RRYjLqsnbIAOED0tcf2BYQ6hzfp9o=; b=iabIkGkNP7B3WKAOhQakZ5RTeNSqxi6Mc8Yiz3jM7LNDTwbnA+hurlR+muy/Jd33HZ 4FdorA8uD2LCGHJE0+aRlBYmFngnVOxREoy5urHlSRcXs/xbvN6xLR9iWEihj76/doIg Rz0S5umDXN+HHPRWWnUkk8aSBMWmWkdG0OE/c29fqnwKo+0LhMI/j8XN/EqZWWvVQyPh BqOF7jscir1UBNGcHwiRA8ZpEyF7WJmBCopvpo5CSjxiwu6IEd0sStCLrsvObKYuQwEW 5xEAo+mifWsHXZlay112pHCxD+m6owSiRcmS+kzLgWz5gKKMKhjY5qgUMmpHqMRBFi1S DaeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ldf+qDPVj9YB70RRYjLqsnbIAOED0tcf2BYQ6hzfp9o=; b=q9llXAJi5YaLzMpsSyr6TvO2qfAufqBEqlGsavHH5xnUOVybqVeovxGNgSK6CFoXof IZ2kHFlCrKWAReRvNprCRRS/xSE2xeeN/lo/OLi/0IykvbW3m9huzceyjd0ErXDapczX sAS8Z/U5g7XWZCKlYjk/oog7jnQcXJs4la48CNR55FtGp5RRh9C+KXt79zFSFGXEQ/0L T4pyPQ0fZA7HmxALahFMxorUq439qqF0x87vkpQ5oOeN9NsE4oYwLiijcvvfkIwqqBTF QE9Lzdo8N/ewNhVZwxhPDslfeoLoUxIeWLzugI4+jqlsRbcKeczN27Umia+eTBS8ANZz /eww== X-Gm-Message-State: AIkVDXIAYKo20nBQNoDNi2FKFJNxsElXymiPKqDCCRiqZYPmmDxqHIi/mdEv/asCKKYWcDj5Ad5y7o9DybuZOA== X-Received: by 10.28.100.70 with SMTP id y67mr5482604wmb.45.1484243762100; Thu, 12 Jan 2017 09:56:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.10.69 with HTTP; Thu, 12 Jan 2017 09:55:41 -0800 (PST) In-Reply-To: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> From: =?UTF-8?Q?Maciej_Borz=C4=99cki?= Date: Thu, 12 Jan 2017 18:55:41 +0100 Message-ID: To: Tim Orling Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 17:56:14 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling wrote: > You can also build using Docker containers: > https://github.com/crops/docker-win-mac-docs/wiki IIRC docker on mac relies on docker-machine, which in turn spins up a virtualbox VM. > > On Jan 12, 2017, at 7:34 AM, Burton, Ross wrote: > > > On 12 January 2017 at 15:14, Roger Smith wrote: >> >> Is there any documentation for running the Yocto build system on Mac OS = X >> or macOS as Apple now calls it? I am working with the Intel Aero board. >> Before I go down the rabbit hole of fixing issues like this one (and I a= m >> using the bash shell), I=E2=80=99d like to know if anyone has build it o= n os x >> before. > > > If you install all of the GNU tools using brew or similar and put them fi= rst > on $PATH then you can get bitbake started. Then you need to stub out the > linux-specific bits in bitbake. I've previously started on this work > already > (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/dar= win). > The next step is figuring out how to configure OE to build and link nativ= ely > on OSX using LLVM instead of GCC. > > However all of this is mostly academic because in Sierra (iirc) onwards > there is tighter security on processes, which means that pseudo won't wor= k > even if you port it to macOS. > > So unless you fancy some non-trivial engineering the short version is jus= t > use something like Docker to run a Linux system on your Mac. > > Ross > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > --=20 Maciej Borzecki RnDity From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id EBF83E003C1; Thu, 12 Jan 2017 10:03:41 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.216.172 listed in list.dnswl.org] * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [209.85.216.172 listed in dnsbl.sorbs.net] Received: from mail-qt0-f172.google.com (mail-qt0-f172.google.com [209.85.216.172]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BDF98E0033D for ; Thu, 12 Jan 2017 10:03:37 -0800 (PST) Received: by mail-qt0-f172.google.com with SMTP id l7so25553339qtd.1 for ; Thu, 12 Jan 2017 10:03:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lyWC/cUV4ljOjMoCUod9GVqoL2TcS7SjbPnvKMg+hFU=; b=08gyFcsOWAffjCl5Z8As2DMB3wfV4SSbnKJ7AdNkueY6TSWDqEORz5XRZ4/4Ojy0yQ q364qs39crqiERI1ZB8AH6RimG/V2URCyBCSMnivrIkWrRWPPZk+sH605AXYnqFOZcTr m+Jj8sc7Mk/ybSUB9/sjq2Z749ez6zWgsjBedrIpFtCyc+XMAhe2YU+upBXTozZ5Mq1y DkddeKIuu9Jyr6lFVN69mS0LAOd9f8qICl9JNCXsR7kIPf+1ElD6TSZc19K0/q1m+55Y 5IF2KY+E+tYJUbnzFKnXdPFB2ulQQ37mm377cNc9KUnxl9vjKb7bPiMR7w4b0t5sgfZc OtYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lyWC/cUV4ljOjMoCUod9GVqoL2TcS7SjbPnvKMg+hFU=; b=m+73x0QCbsYQ+ZUD7qk1PuMWDaIY4gblLg28wuPQ1YhXDJTYLTUcrGZkh6qZTh8FT/ /uLWjAD0Dzw/tlHIl5R4M3xj9XY2+44mI/vPpXVqBY/FjaZayXARR/BZ4Me3/6mb+mS0 S23gCo8NTwd4T7qX9A5DtrV2KwloB7uxm7II0xrysQkk3fpntVBM3aVbTHS79gAUUF0Q ZI5PheaIY8usJHfKnZFQOXEcmTrd8oe5aC5yNNqQLjVrDuhcz/8YZJN01m3VQ3NviN/4 NPHgY1CAmXK/Rwrc2Rri+q1gms3I8jrN+8gH8DvII4gMqYojouHQl4a+TQSMeafoohN9 Ofxg== X-Gm-Message-State: AIkVDXJ5YtPyc7ruL3ymNYQr97Jg9TfF3QenSY2tyoET/Q14hHvWJyV1nVp7oFeZdLMUdX33K9Gu4KVtiyWbBHtU X-Received: by 10.237.54.1 with SMTP id e1mr13385636qtb.68.1484244217039; Thu, 12 Jan 2017 10:03:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.106.99 with HTTP; Thu, 12 Jan 2017 10:03:16 -0800 (PST) In-Reply-To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> From: "Burton, Ross" Date: Thu, 12 Jan 2017 18:03:16 +0000 Message-ID: To: =?UTF-8?Q?Maciej_Borz=C4=99cki?= Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 18:03:42 -0000 Content-Type: multipart/alternative; boundary=001a1142dcf0512b910545e98976 --001a1142dcf0512b910545e98976 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12 January 2017 at 17:55, Maciej Borz=C4=99cki wrote: > IIRC docker on mac relies on docker-machine, which in turn spins up a > virtualbox VM. > That's the old Docker (Docker Toolbox), the new Docker (Docker for Mac) uses the built-in hypervisor so basically works exactly like Docker on Linux. Ross --001a1142dcf0512b910545e98976 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 12 January 2017 at 17:55, Maciej Borz=C4=99cki <maciej.borzeck= i@rndity.com> wrote:

IIRC docker on mac relies = on docker-machine, which in turn spins up a
virtualbox VM.

That's the old Docker (Docke= r Toolbox), the new Docker (Docker for Mac) uses the built-in hypervisor so= basically works exactly like Docker on Linux.

Ross

--001a1142dcf0512b910545e98976-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8D156E0034A; Thu, 12 Jan 2017 10:12:42 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.67 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (gizero[at]gmail.com) * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [74.125.82.67 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4F215E0030B for ; Thu, 12 Jan 2017 10:12:40 -0800 (PST) Received: by mail-wm0-f67.google.com with SMTP id r126so5505009wmr.3 for ; Thu, 12 Jan 2017 10:12:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kyCYMIV9imTYP3IZ9txtY5r/2Dmeq9pf3UAE4dqpY2Q=; b=e4+53PwVqPNVJBexuFdxY1JlmcLjLJRMUXgnkRilnQhwS+sJbrDhvQXOpeski37puj I7Y9wN8j+WMzxNpLBmgg47tTfoscAJ4/BR2Y2WViLR9NM+xX35LlpG9cv2cZRDcmkuNq FDCGFNU5jUoseZ1Ky8zayhGIZt8JofG0VH/prkA5rT57PQBxGcQ2p/qUr0DRpzOzoA8W RB9ygT5VPCP/gd7RWzqp7G8wrOA/du1LUgbEkWGRATM+T62ZFMC0Ocv5iAgkMXsrwGS6 Yve/iool04AIgCQiCySV2W55mPtnq3Dk6vMA3/0/EGbc5/UmkNga2qOdFdYbRHOsW4V9 TrFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kyCYMIV9imTYP3IZ9txtY5r/2Dmeq9pf3UAE4dqpY2Q=; b=ZX7Rss4QnUjj++3BsuA774MPIL3Qei5PfguU/4JkImndAdP7ZQQ2bpJZk/CGUW14C7 wOAGMyOJjIkhiMNwjIE1ICXvjJxskH/ziC7XccxJm5/2yzdAIyOiyZJlju//pgdyy/+d NN59Z3/VkIjlmMHFN3tSj3dRXaIBycuMHsa/A56Pbwp8gTpmwMXdnh9F3BlYpWhxOrXP 0FHB6x2I0PQbOSrQoqEM19J+z/cUD+n49u3srxa6It4UH11hgP0cRtH+PAzpyir3sY2q rX3n7FRRim1K3PKpWjbgpM1zP0La5D+HwIecW09QFyVRAa0/WDhEDv7H81k2XNA5+FDO LO5w== X-Gm-Message-State: AIkVDXJhXSexoDAKsTqHJhM6G+OkAB+KU/I+XFeRt6eY5o3c0WqFbG5weoKP3ov2qGH2arrrOFsdprftz67yzw== X-Received: by 10.223.162.10 with SMTP id p10mr8281753wra.160.1484244759282; Thu, 12 Jan 2017 10:12:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.169.38 with HTTP; Thu, 12 Jan 2017 10:12:38 -0800 (PST) In-Reply-To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> From: Andrea Galbusera Date: Thu, 12 Jan 2017 19:12:38 +0100 Message-ID: To: =?UTF-8?Q?Maciej_Borz=C4=99cki?= Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 18:12:42 -0000 Content-Type: multipart/alternative; boundary=f403045ed4b2a30ac70545e9a9c4 --f403045ed4b2a30ac70545e9a9c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki wrote: > On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling > wrote: > > You can also build using Docker containers: > > https://github.com/crops/docker-win-mac-docs/wiki > > IIRC docker on mac relies on docker-machine, which in turn spins up a > virtualbox VM. > Not anymore! There's a native implementation [1] but still a linux kernel around anyway! ;-) [1] https://www.docker.com/docker-news-and-press/docker-released-native-mac-and= -windows-apps-optimize-developer-experience > > > > > > On Jan 12, 2017, at 7:34 AM, Burton, Ross wrote= : > > > > > > On 12 January 2017 at 15:14, Roger Smith wrote= : > >> > >> Is there any documentation for running the Yocto build system on Mac O= S > X > >> or macOS as Apple now calls it? I am working with the Intel Aero board= . > >> Before I go down the rabbit hole of fixing issues like this one (and I > am > >> using the bash shell), I=E2=80=99d like to know if anyone has build it= on os x > >> before. > > > > > > If you install all of the GNU tools using brew or similar and put them > first > > on $PATH then you can get bitbake started. Then you need to stub out t= he > > linux-specific bits in bitbake. I've previously started on this work > > already > > (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/ > log/?h=3Dross/darwin). > > The next step is figuring out how to configure OE to build and link > natively > > on OSX using LLVM instead of GCC. > > > > However all of this is mostly academic because in Sierra (iirc) onwards > > there is tighter security on processes, which means that pseudo won't > work > > even if you port it to macOS. > > > > So unless you fancy some non-trivial engineering the short version is > just > > use something like Docker to run a Linux system on your Mac. > > > > Ross > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > -- > Maciej Borzecki > RnDity > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > --f403045ed4b2a30ac70545e9a9c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On T= hu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki <maciej.borzeck= i@rndity.com> wrote:

On Thu, Jan 12, 2017 at 4:39 PM, Tim Or= ling
<timothy.t.orling@li= nux.intel.com> wrote:
> You can also build using Docker containe= rs:
> https://github.com/crops/docker-win-mac-d= ocs/wiki

IIRC docker on mac relies on docker-machine, which in turn spins up = a
virtualbox VM.

Not anymore! There's= a native implementation [1] but still a linux kernel around anyway! ;-)

[1]=C2=A0https://www.docker.com/docker-news-and-press/docker-released-n= ative-mac-and-windows-apps-optimize-developer-experience

=C2= =A0

>
> On Jan 12, 2017, at 7:34 AM, Burton, Ross <ross.burton@intel.com> wrote:
>
>
> On 12 January 2017 at 15:14, Roger Smith <roger@sentientblue.com> wrote:
>>
>> Is there any documentation for running the Yocto build system on M= ac OS X
>> or macOS as Apple now calls it? I am working with the Intel Aero b= oard.
>> Before I go down the rabbit hole of fixing issues like this one (a= nd I am
>> using the bash shell), I=E2=80=99d like to know if anyone has buil= d it on os x
>> before.
>
>
> If you install all of the GNU tools using brew or similar and put them= first
> on $PATH then you can get bitbake started.=C2=A0 Then you need to stub= out the
> linux-specific bits in bitbake.=C2=A0 I've previously started on t= his work
> already
> (http://git.yoctopro= ject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/darwin). > The next step is figuring out how to configure OE to build and link na= tively
> on OSX using LLVM instead of GCC.
>
> However all of this is mostly academic because in Sierra (iirc) onward= s
> there is tighter security on processes, which means that pseudo won= 9;t work
> even if you port it to macOS.
>
> So unless you fancy some non-trivial engineering the short version is = just
> use something like Docker to run a Linux system on your Mac.
>
> Ross
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto=
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto=
>

--
Maciej Borzecki
RnDity

--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto<= br>

--f403045ed4b2a30ac70545e9a9c4-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 07F94E009AD; Thu, 12 Jan 2017 10:43:43 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.48 listed in list.dnswl.org] * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [74.125.82.48 listed in dnsbl.sorbs.net] Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 601FCE003E4 for ; Thu, 12 Jan 2017 10:43:30 -0800 (PST) Received: by mail-wm0-f48.google.com with SMTP id r126so32489443wmr.0 for ; Thu, 12 Jan 2017 10:43:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rndity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=YdKnr+e7ktpPXg49AMueq6ahcIPscbIoC28CRV1XRqY=; b=uKrBckLe+BjITiTTpk7x301bK5YA3RMQparI7QCWbLr8pTpf5lI4VskemUlKgC6dBa ae1zQV6sp3CWfJvhEixjUS8+MOoyp8R3VJmzMJLr/h1Q9UZ/gf6h/sA3kNF13IuQq0hP rHWMwx9cm0XNi61TU+wEC5HizsH4Hqhh68dfhTywujA+mJ47N/3nyWu3gqf/lHO02knF do0gqHjqZ1P2ax9hroJRYZ+9Sja3gP64hp9Q4o/hb5d/mkgqIPzuM+iGIv4IZ4SPBa3j 2WH9r5I6W8wL0SO5gMp3tUcK5U5NjN8C2EtO3jyzLSHU+UyYJeZRDAHWOCUs/VEhZb1O 7SzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=YdKnr+e7ktpPXg49AMueq6ahcIPscbIoC28CRV1XRqY=; b=RPdQV+hDrPe/D8zl6Q+g//YJtbHb8Cenr1EG9oNSAd0ajzG33GWTbGlzSxFnwET/T4 E5URTvpbGu3lY4XGcS2MSRVnKaMcO4yiadrX6Q2mq0pDc+78aU1uIlSxmgjp2Z8dINF1 hhIwmz5xoQp53gx4tRUXshUg8+fSUZ7wNOwWM41rN9FM4GH/pl3CmlmqeZFBKJSxrS2v ys19jGlehAorg31W7EO2l2pqY9h4JV57dcprQUlUYnw9QJaaOsUzwEInoCvQGX0ldatf tR/mOIKRGNZbNGpMzztG1sJQz7lGFGv+WttrZi5sMbO+sPFyYOkwMkWVm8Yl+c1oMdE0 s9zg== X-Gm-Message-State: AIkVDXJZzpLE8u1BR8TE1jkCupXYlbCNVM7M16Yljf5VRvJoJxba86Fnp26s/wYysIEIa5xazHM8R8s4F8UBJg== X-Received: by 10.223.150.58 with SMTP id b55mr8238731wra.192.1484246609090; Thu, 12 Jan 2017 10:43:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.10.69 with HTTP; Thu, 12 Jan 2017 10:43:08 -0800 (PST) In-Reply-To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

From: =?UTF-8?Q?Maciej_Borz=C4=99cki?= Date: Thu, 12 Jan 2017 19:43:08 +0100 Message-ID: To: Andrea Galbusera Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 18:43:43 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Jan 12, 2017 at 7:12 PM, Andrea Galbusera wrote: > On Thu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki > wrote: >> >> On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling >> wrote: >> > You can also build using Docker containers: >> > https://github.com/crops/docker-win-mac-docs/wiki >> >> IIRC docker on mac relies on docker-machine, which in turn spins up a >> virtualbox VM. > > > Not anymore! There's a native implementation [1] but still a linux kernel > around anyway! ;-) > > [1] > https://www.docker.com/docker-news-and-press/docker-released-native-mac-a= nd-windows-apps-optimize-developer-experience Good to know. There is still hope for mac users after all :) >> >> >> >> > >> > On Jan 12, 2017, at 7:34 AM, Burton, Ross wrot= e: >> > >> > >> > On 12 January 2017 at 15:14, Roger Smith wrot= e: >> >> >> >> Is there any documentation for running the Yocto build system on Mac = OS >> >> X >> >> or macOS as Apple now calls it? I am working with the Intel Aero boar= d. >> >> Before I go down the rabbit hole of fixing issues like this one (and = I >> >> am >> >> using the bash shell), I=E2=80=99d like to know if anyone has build i= t on os x >> >> before. >> > >> > >> > If you install all of the GNU tools using brew or similar and put them >> > first >> > on $PATH then you can get bitbake started. Then you need to stub out >> > the >> > linux-specific bits in bitbake. I've previously started on this work >> > already >> > >> > (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/= darwin). >> > The next step is figuring out how to configure OE to build and link >> > natively >> > on OSX using LLVM instead of GCC. >> > >> > However all of this is mostly academic because in Sierra (iirc) onward= s >> > there is tighter security on processes, which means that pseudo won't >> > work >> > even if you port it to macOS. >> > >> > So unless you fancy some non-trivial engineering the short version is >> > just >> > use something like Docker to run a Linux system on your Mac. >> > >> > Ross >> > -- >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> > >> > >> > >> > -- >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> > >> >> >> >> -- >> Maciej Borzecki >> RnDity >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > --=20 Maciej Borzecki RnDity From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4C18DE00C93; Thu, 12 Jan 2017 14:16:53 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [192.55.52.115 listed in list.dnswl.org] Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F32A7E00C88 for ; Thu, 12 Jan 2017 14:16:41 -0800 (PST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 12 Jan 2017 14:16:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,220,1477983600"; d="scan'208,217";a="1093399825" Received: from ttorling-mac01.jf.intel.com ([10.24.10.84]) by fmsmga001.fm.intel.com with ESMTP; 12 Jan 2017 14:16:40 -0800 From: Tim Orling Message-Id: <400C69D6-2DE9-4994-AB53-AA216FD44C79@linux.intel.com> Mime-Version: 1.0 (Mac OS X Mail 10.2 $3259$) Date: Thu, 12 Jan 2017 14:16:40 -0800 In-Reply-To: To: =?utf-8?Q?Maciej_Borz=C4=99cki?= References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

On Jan 12, 2017, at 10:43 AM, Maciej Borz=C4=99cki <maciej.borzecki@rndity.com> wrote:

On Thu, Jan 12, 2017 at 7:12 PM, Andrea = Galbusera <gizero@gmail.com> wrote:
On Thu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki
<maciej.borzecki@rndity.com> wrote:

On Thu, = Jan 12, 2017 at 4:39 PM, Tim Orling
<timothy.t.orling@linux.intel.com> wrote:
You can also build using = Docker containers:
https://github.com/crops/docker-win-mac-docs/wiki

IIRC docker on mac relies on = docker-machine, which in turn spins up a
virtualbox VM.

Not anymore! = There's a native implementation [1] but still a linux kernel
around anyway! ;-)

[1]
https://www.docker.com/docker-news-an.d-press/docker-released-n= ative-mac-and-windows-apps-optimize-developer-experience

Good to know. There is still hope for mac users = after all :)

My main = development machine is Mac OS X 10.12.2 (Sierra). I stay up to date with = the latest Docker for Mac beta. It is a very pleasant = experience.

On Jan 12, 2017, at 7:34 AM, = Burton, Ross <ross.burton@intel.com> wrote:

On 12 January 2017 at 15:14, Roger Smith = <roger@sentientblue.com> wrote:

Is there any documentation for = running the Yocto build system on Mac OS
X
or = macOS as Apple now calls it? I am working with the Intel Aero board.
Before I go down the rabbit hole of fixing issues like this = one (and I
am
using the bash shell), I=E2=80=99= d like to know if anyone has build it on os x
before.

If you install all = of the GNU tools using brew or similar and put them
firston $PATH then you can get bitbake started. Then you = need to stub out
the
linux-specific bits in = bitbake. I've previously started on this work
already

(http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=3D= ross/darwin).
The next step is figuring out how to = configure OE to build and link
natively
on = OSX using LLVM instead of GCC.

However all = of this is mostly academic because in Sierra (iirc) onwards
there is tighter security on processes, which means that = pseudo won't
work
even if you port it to = macOS.

So unless you fancy some non-trivial = engineering the short version is
just
use = something like Docker to run a Linux system on your Mac.
Ross
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
Maciej Borzecki
RnDity
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
Maciej = Borzecki
RnDity

= --Apple-Mail=_1EFDECF2-7114-40CF-8797-876DD74B15C6-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7423BE00CB0; Thu, 12 Jan 2017 14:33:13 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [134.134.136.100 listed in list.dnswl.org] Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9C240E00C7D for ; Thu, 12 Jan 2017 14:32:59 -0800 (PST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga105.jf.intel.com with ESMTP; 12 Jan 2017 14:32:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,220,1477983600"; d="scan'208,217";a="53228156" Received: from ttorling-mac01.jf.intel.com ([10.24.10.84]) by fmsmga006.fm.intel.com with ESMTP; 12 Jan 2017 14:32:58 -0800 From: Tim Orling Message-Id: Mime-Version: 1.0 (Mac OS X Mail 10.2 $3259$) Date: Thu, 12 Jan 2017 14:32:57 -0800 In-Reply-To: To: Andrea Galbusera References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

X-Mailer: Apple Mail (2.3259) Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 22:33:13 -0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_04A610AE-336C-45CF-9477-60C61275153A" --Apple-Mail=_04A610AE-336C-45CF-9477-60C61275153A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 12, 2017, at 8:50 AM, Andrea Galbusera = wrote: >=20 > On Thu, Jan 12, 2017 at 5:21 PM, Belisko Marek = > wrote: > On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling > > wrote: > > You can also build using Docker containers: > > https://github.com/crops/docker-win-mac-docs/wiki = > Well the re is other limitation about slow filesystem access from > docker on osx. There is workaround to use nfs but it's not possible to > use nfs for building yocto - so it's kind of chicken-egg problem ;) >=20 > I shortly tested the CROPS docker-based setup after watching some = presentation at ELCE 2016 in Berlin. It basically worked but I = experienced the filesystem slowness your are talking about. I ended up = waiting hours to see a simple core-image-minimal build complete (even = after giving more cores to docker). One more point is that slightly more = complex build scenarios, i.e. building resin.os, also required tweaking = docker run parameters for the build container in order to give bitbake = access to features like loop devices it needed (not always easily = debuggable issues indeed). Turned out I decided to stick with more = canonical linux based environments for the moment. >=20 Depending on your hardware, it will take hours to build a simple image = for the first time. This is no different on native Linux, if the = hardware is only 1-4 cores, 4-8 GB RAM and especially if you are using a = spinning harddrive. Server class systems with 72+ cores and 128+ GB of = RAM will have a significantly faster build time. Almost all my YP/OE = builds are now run in containers. We will run some tests and get back to you about the real speed = differences. Assuming you are running on the same hardware, we have seen = builds on Windows be slightly *faster* than on native Linux. We need to = collect data for our latest Mac OS X builds to address your concern. > Anyway, the technology behind CROPS is *very* interesting to me, and = I'd like to hear from people closely involved (Tim?) what the state of = the art is and what we can expect to see in the near future. IIRC, the = roadmap for Yocto 2.3 release was supposed to resurrect the Eclipse = plugin and adopt CROPS as an alternative for running eSDK in a seamless = way on different development host OSs. Beside from the images on docker = hub and the github projects that didn't have high activity in the latest = months, I hardly find discussions and documentation on the whole = approach. Isn't this hot enough anymore or are there big issues that = will prevent this technology from taking off. I often manage SDKs for = Windows-minded developers and I strongly yearn to find a better approach = to help them feel at home while building stuff for OE/Yocto based = systems...=20 >=20 This work is being done by a very small team. It is no less hot than = since it was first announced. However, the state of the Eclipse plugin = at the initial announcement was experimental and the perception was that = it was production ready. That is a risk of developing a project in the = open. Both the Docker technology and the Eclipse technologies that we = are using are rapidly changing. Our current work is hosted on GitHub = (https://github.com/crops/eclipse-crops = ). We had to rethink some of the = approach that we demoed at ELC San Diego. We are still targeting 2.3 for = the =E2=80=9Cstandard SDK=E2=80=9D approach (e.g. no =E2=80=9Cdevtool=E2=80= =9D integration). > =20 > > > > On Jan 12, 2017, at 7:34 AM, Burton, Ross > wrote: > > > > > > On 12 January 2017 at 15:14, Roger Smith > wrote: > >> > >> Is there any documentation for running the Yocto build system on = Mac OS X > >> or macOS as Apple now calls it? I am working with the Intel Aero = board. > >> Before I go down the rabbit hole of fixing issues like this one = (and I am > >> using the bash shell), I=E2=80=99d like to know if anyone has build = it on os x > >> before. > > > > > > If you install all of the GNU tools using brew or similar and put = them first > > on $PATH then you can get bitbake started. Then you need to stub = out the > > linux-specific bits in bitbake. I've previously started on this = work > > already > > = (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/darw= in = ). > > The next step is figuring out how to configure OE to build and link = natively > > on OSX using LLVM instead of GCC. > > > > However all of this is mostly academic because in Sierra (iirc) = onwards > > there is tighter security on processes, which means that pseudo = won't work > > even if you port it to macOS. > > > > So unless you fancy some non-trivial engineering the short version = is just > > use something like Docker to run a Linux system on your Mac. > > > > Ross > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto = > > > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto = > > >=20 > marek >=20 > -- > as simple and primitive as possible > ------------------------------------------------- > Marek Belisko - OPEN-NANDRA > Freelance Developer >=20 > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > Tel: +421 915 052 184 > skype: marekwhite > twitter: #opennandra > web: http://open-nandra.com > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto = --Apple-Mail=_04A610AE-336C-45CF-9477-60C61275153A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Jan 12, 2017, at 8:50 AM, Andrea Galbusera <gizero@gmail.com> = wrote:

On Thu, Jan 12, 2017 at = 5:21 PM, Belisko Marek <marek.belisko@gmail.com> wrote:
On = Thu, Jan 12, 2017 at 4:39 PM, Tim Orling
<timothy.t.orling@linux.intel.com> = wrote:
> You can also build using Docker containers:
> https://github.com/crops/docker-win-mac-docs/wiki
Well the re = is other limitation about slow filesystem access from
docker= on osx. There is workaround to use nfs but it's not possible to
use nfs for building yocto - so it's kind of chicken-egg = problem ;)

I shortly tested the CROPS docker-based = setup after watching some presentation at ELCE 2016 in Berlin. It = basically worked but I experienced the filesystem slowness your are = talking about. I ended up waiting hours to see a simple = core-image-minimal build complete (even after giving more cores to = docker). One more point is that slightly more complex build scenarios, = i.e. building resin.os, also required tweaking docker run parameters for = the build container in order to give bitbake access to features like = loop devices it needed (not always easily debuggable issues indeed). = Turned out I decided to stick with more canonical linux based = environments for the moment.

Depending on your hardware, it will take hours to = build a simple image for the first time. This is no different on native = Linux, if the hardware is only 1-4 cores, 4-8 GB RAM and especially if = you are using a spinning harddrive. Server class systems with 72+ cores = and 128+ GB of RAM will have a significantly faster build time. Almost = all my YP/OE builds are now run in containers.

We will run some tests and get back to you about the = real speed differences. Assuming you are running on the same hardware, = we have seen builds on Windows be slightly *faster* than on native = Linux. We need to collect data for our latest Mac OS X builds to address = your concern.

Anyway, the technology behind = CROPS is *very* interesting to me, and I'd like to hear from people = closely involved (Tim?) what the state of the art is and what we can = expect to see in the near future. IIRC, the roadmap for Yocto 2.3 = release was supposed to resurrect the Eclipse plugin and adopt CROPS as = an alternative for running eSDK in a seamless way on different = development host OSs. Beside from the images on docker hub and the = github projects that didn't have high activity in the latest months, I = hardly find discussions and documentation on the whole approach. Isn't = this hot enough anymore or are there big issues that will prevent this = technology from taking off. I often manage SDKs for Windows-minded = developers and I strongly yearn to find a better approach to help them = feel at home while building stuff for OE/Yocto based = systems...

This work is being done by a very small team. It = is no less hot than since it was first announced. However, the state of = the Eclipse plugin at the initial announcement was experimental and the = perception was that it was production ready. That is a risk of = developing a project in the open. Both the Docker technology and the = Eclipse technologies that we are using are rapidly = changing.

Our current work is hosted on = GitHub (https://github.com/crops/eclipse-crops). We had to = rethink some of the approach that we demoed at ELC San Diego. We are = still targeting 2.3 for the =E2=80=9Cstandard SDK=E2=80=9D approach = (e.g. no =E2=80=9Cdevtool=E2=80=9D integration).

>
> On Jan 12, = 2017, at 7:34 AM, Burton, Ross <ross.burton@intel.com> wrote:
>
>
> On 12 January 2017 at 15:14, Roger = Smith <roger@sentientblue.com> wrote:
>>>> Is there any documentation for running the Yocto = build system on Mac OS X
>> or macOS as Apple now = calls it? I am working with the Intel Aero board.
>> = Before I go down the rabbit hole of fixing issues like this one (and I = am
>> using the bash shell), I=E2=80=99d like to = know if anyone has build it on os x
>> before.
>
>
> If you install all = of the GNU tools using brew or similar and put them first
> on $PATH then you can get bitbake started. Then = you need to stub out the
> linux-specific bits in = bitbake. I've previously started on this work
> = already
> (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/darwin).
> The next step = is figuring out how to configure OE to build and link natively
> on OSX using LLVM instead of GCC.
>
> However all of this is mostly academic because in Sierra = (iirc) onwards
> there is tighter security on = processes, which means that pseudo won't work
> even if = you port it to macOS.
>
> So unless = you fancy some non-trivial engineering the short version is just
> use something like Docker to run a Linux system on your = Mac.
>
> Ross
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>>
> --
> = _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

marek

--
as simple = and primitive as possible
-------------------------------------------------
Marek Belisko - = OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

= --Apple-Mail=_04A610AE-336C-45CF-9477-60C61275153A-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id CA0FAE00C78; Thu, 12 Jan 2017 14:59:07 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [147.11.146.13 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 37AA6E00C65 for ; Thu, 12 Jan 2017 14:59:05 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id v0CMx4nO028005 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 12 Jan 2017 14:59:04 -0800 (PST) Received: from soho-mhatle-m.local (172.25.36.235) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.294.0; Thu, 12 Jan 2017 14:59:03 -0800 To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

<448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> From: Mark Hatle Organization: Wind River Systems Message-ID: Date: Thu, 12 Jan 2017 16:59:03 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 22:59:07 -0000 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit On 1/12/17 11:41 AM, Roger Smith wrote: > I have Parallels (running on El Capitan the one before Sierra) and ubuntu 14 > running my current build environment on a MacBook Pro, but boy is the build > slow… I also worked at Apple for 19 years on drivers inside MacOS X/iOS, so I am > more than motivated to have this working natively rather than inside any > container or disk space hogging environment. As I mentioned I am working with > the Intel Aero compute board, so slogging though all this fat to build an image > is a productivity killer. So take from this.. there is desire for oe/bitbake to work natively. Most people don't have the skill or free time to do the work. A number of us started it at one time or another and made enough progress to say "ya I think it's possible" and then ran out of time. 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". --Mark > I think most of the incompatibilities between Linux and os x (which btw is > coming from the ios side of the fence unfortunately), can be mitigated with boot > args or via the command line . Apple’s compiler team had to make llvm compatible > with gcc, so I am surprised if in 2017, there are compiler issues to building > for an x86_64 platform with llvm on the Mac . That’s the kind of bug Apple likes > to fix promptly.. > > As I mentioned, I tried to simply source the oe-init-build-env, and got an error > that the readlink command that yocto is using is incompatible with the bsd > version of readlink built into os x. > > i.e when I run . > > source oe-init-build-env > > I get the error > > readlink: illegal option -- f > > Which is because on OS X readlink doesn’t specify -f > > YNOPSIS > stat [-FLnq] [-f format| -l | -r | -s | -x] [-t timefmt] [file...] > readlink [-n] [file...] > > I didn’t want to go through this level of change in the Yocto sources if (1) > people don’t care to take changes or (2) it had already been done before.. I was > curious how far down this rabbit hole people had gone before.. > > Roger > > >> On Jan 12, 2017, at 8:50 AM, Andrea Galbusera > > wrote: >> >> On Thu, Jan 12, 2017 at 5:21 PM, Belisko Marek > > wrote: >> >> On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling >> > > wrote: >> > You can also build using Docker containers: >> > https://github.com/crops/docker-win-mac-docs/wiki >> >> Well the re is other limitation about slow filesystem access from >> docker on osx. There is workaround to use nfs but it's not possible to >> use nfs for building yocto - so it's kind of chicken-egg problem ;) >> >> >> I shortly tested the CROPS docker-based setup after watching some presentation >> at ELCE 2016 in Berlin. It basically worked but I experienced the filesystem >> slowness your are talking about. I ended up waiting hours to see a simple >> core-image-minimal build complete (even after giving more cores to docker). >> One more point is that slightly more complex build scenarios, i.e. building >> resin.os, also required tweaking docker run parameters for the build container >> in order to give bitbake access to features like loop devices it needed (not >> always easily debuggable issues indeed). Turned out I decided to stick with >> more canonical linux based environments for the moment. >> >> Anyway, the technology behind CROPS is *very* interesting to me, and I'd like >> to hear from people closely involved (Tim?) what the state of the art is and >> what we can expect to see in the near future. IIRC, the roadmap for Yocto 2.3 >> release was supposed to resurrect the Eclipse plugin and adopt CROPS as an >> alternative for running eSDK in a seamless way on different development host >> OSs. Beside from the images on docker hub and the github projects that didn't >> have high activity in the latest months, I hardly find discussions and >> documentation on the whole approach. Isn't this hot enough anymore or are >> there big issues that will prevent this technology from taking off. I often >> manage SDKs for Windows-minded developers and I strongly yearn to find a >> better approach to help them feel at home while building stuff for OE/Yocto >> based systems... >> >> >> >> > >> > On Jan 12, 2017, at 7:34 AM, Burton, Ross > > wrote: >> > >> > >> > On 12 January 2017 at 15:14, Roger Smith > > wrote: >> >> >> >> Is there any documentation for running the Yocto build system on Mac OS X >> >> or macOS as Apple now calls it? I am working with the Intel Aero board. >> >> Before I go down the rabbit hole of fixing issues like this one (and I am >> >> using the bash shell), I’d like to know if anyone has build it on os x >> >> before. >> > >> > >> > If you install all of the GNU tools using brew or similar and put them first >> > on $PATH then you can get bitbake started. Then you need to stub out the >> > linux-specific bits in bitbake. I've previously started on this work >> > already >> > >> (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/darwin >> ). >> > The next step is figuring out how to configure OE to build and link natively >> > on OSX using LLVM instead of GCC. >> > >> > However all of this is mostly academic because in Sierra (iirc) onwards >> > there is tighter security on processes, which means that pseudo won't work >> > even if you port it to macOS. >> > >> > So unless you fancy some non-trivial engineering the short version is just >> > use something like Docker to run a Linux system on your Mac. >> > >> > Ross >> > -- >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> >> > >> > >> > >> > -- >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> >> > >> >> marek >> >> -- >> as simple and primitive as possible >> ------------------------------------------------- >> Marek Belisko - OPEN-NANDRA >> Freelance Developer >> >> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic >> Tel: +421 915 052 184 >> skype: marekwhite >> twitter: #opennandra >> web: http://open-nandra.com >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2B922E003DB; Fri, 13 Jan 2017 00:54:06 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] X-Greylist: delayed 177 seconds by postgrey-1.32 at yocto-www; Fri, 13 Jan 2017 00:54:00 PST Received: from cit-hm8-gw01.bmw-carit.de (cit-hm8-mail01.bmw-carit.de [212.118.206.84]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D2F75E0034A for ; Fri, 13 Jan 2017 00:54:00 -0800 (PST) Received: from [172.20.0.50] (port=61153 helo=cit-hm8-mail01.bmw-carit.de) by cit-hm8-gw01.bmw-carit.de with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1cRxZc-0002Zy-0y for yocto@yoctoproject.org; Fri, 13 Jan 2017 09:51:00 +0100 Received: from ULM-DC01.bmw-carit.intra ([fe80::41cf:62be:aacc:1aad]) by ULM-DC01.bmw-carit.intra ([fe80::41cf:62be:aacc:1aad%11]) with mapi id 14.03.0123.003; Fri, 13 Jan 2017 09:50:59 +0100 X-CTCH-RefID: str=0001.0A0C0206.587894F4.012F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 From: Clemens Lang To: "yocto@yoctoproject.org" Thread-Topic: [yocto] Building on MacOS X Thread-Index: AQHSbOfagOCkOJDQWUevakFI4lbOJKE06B2AgAABWYCAAAvGgIAACAsAgAAORACAAFjRgIAApWEA Date: Fri, 13 Jan 2017 08:50:58 +0000 Message-ID: <23A9A636-C738-4FF6-962F-DCDC107A7AA8@bmw-carit.de> References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

<448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> In-Reply-To: Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.20.20.80] MIME-Version: 1.0 Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 08:54:06 -0000 Content-Language: en-US Content-Type: text/plain; charset="utf-8" Content-ID: <5F4E8B03ABFF1541BB7078004AED2A0B@bmw-carit.de> Content-Transfer-Encoding: base64 SGksDQoNCg0KPiBPbiAxMiBKYW4gMjAxNywgYXQgMjM6NTksIE1hcmsgSGF0bGUgPG1hcmsuaGF0 bGVAd2luZHJpdmVyLmNvbT4gd3JvdGU6DQo+IA0KPiBBcyBmYXIgYXMgSSBrbm93IHBzZXVkbyBh bmQgdGhlIHNlY3VyaXR5IGludHJvZHVjZWQgaW4gMTAuMTEgdGhhdCBhZmZlY3QNCj4gcHJlbG9h ZGluZyBpcyBsaWtlbHkgdGhlIGJpZ2dlc3QgdGVjaG5pY2FsIHByb2JsZW0uLi4gIGV2ZXJ5dGhp bmcgZWxzZSBpcyBqdXN0DQo+ICJpdCdzIG5vdCBMaW51eOKAnS4NCg0KV2l0aCBTeXN0ZW0gSW50 ZWdyaXR5IFByb3RlY3Rpb24gZGlzYWJsZWQsIHBzZXVkbyBzaG91bGQgc3RpbGwgd29yayBhcyBp dCBkaWQgYmVmb3JlLCBpZiB0aGF04oCZcyBhbiBhY2NlcHRhYmxlIHN0ZXAgZm9yIHlvdS4NCg0K SWYgaXQgaXNu4oCZdCwgQXBwbGXigJlzIG5ldyBsaW1pdGF0aW9ucyBjYW4gYWxzbyBiZSB3b3Jr ZWQgYXJvdW5kIGluIHBzZXVkbyBieSBob29raW5nIHRoZSBleGVjKDIpIGFuZCBwb3NpeF9zcGF3 bigyKSBzeXNjYWxscywgY2hlY2tpbmcgaWYgdGhlIGJpbmFyeSB0byBiZSBleGVjdXRlZCBpcyB1 bmRlciBzeXN0ZW0gaW50ZWdyaXR5IHByb3RlY3Rpb24sIG1ha2luZyBhIGNvcHkgd2l0aG91dCB0 aGUgU0lQLWJpdCBpZiBpdCBpcyBhbmQgdHJhbnNwYXJlbnRseSBydW5uaW5nIHRoYXQgY29weSBp bnN0ZWFkLiBUaGF0IGNvZGUgd291bGQgbmVlZCB0byBiZSB3cml0dGVuLCB0aG91Z2ggKExldCBt ZSBrbm93IGlmIHlvdSB3YW50IHRvIGRvIHRoYXQsIEkgaGF2ZSB0aGUgY29kZSBmb3IgYSBkaWZm ZXJlbnQgcHJvamVjdC4pLiBJdOKAmXMgcHJvYmFibHkgb25seSBhIG1hdHRlciBvZiB0aW1lIHVu dGlsIEFwcGxlIHByZXZlbnRzIHRoYXQgZnJvbSB3b3JraW5nLCB0b28sIHRob3VnaCwgZS5nLiBi eSBtYWtpbmcgc29tZSBzdGFuZGFyZCBzeXN0ZW0gdG9vbHMgc2lnbmVkIGJpbmFyaWVzIHRoYXQg bm8gbG9uZ2VyIGxvYWQgcHJlbG9hZGVkIGxpYnJhcmllcy4NCg0KDQpIVEgsDQpDbGVtZW5zDQot LSANCkNsZW1lbnMgTGFuZyDigKIgRGV2ZWxvcG1lbnQgU3BlY2lhbGlzdA0KQk1XIENhciBJVCBH bWJIIOKAoiBMaXNlLU1laXRuZXItU3RyLiAxNCDigKIgODkwODEgVWxtIOKAoiBodHRwOi8vYm13 LWNhcml0LmNvbQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KQk1XIENhciBJVCBHbWJIDQpHZXNjaMOkZnRz ZsO8aHJlcjogTWljaGFlbCBXw7xydGVuYmVyZ2VyIHVuZCBBbGV4aXMgVHJvbGluDQpTaXR6IHVu ZCBSZWdpc3RlcmdlcmljaHQ6IE3DvG5jaGVuIEhSQiAxMzQ4MTANCi0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N Cg0K From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 853FEE00655; Sat, 14 Jan 2017 11:45:51 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [109.224.233.103 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from pamail.gradwell.com (linmainlb.pa.thw.gradwell.net [109.224.233.103]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E9327E004E5 for ; Sat, 14 Jan 2017 11:45:47 -0800 (PST) Received: (qmail 18598 invoked from network); 14 Jan 2017 19:45:45 -0000 Received: from unknown (HELO ?10.0.1.192?) (roger@sentientblue.com@[73.231.167.180]) by 192.168.50.232 with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 14 Jan 2017 19:45:44 -0000 Mime-Version: 1.0 (Mac OS X Mail 9.3 $3124$) From: Roger Smith In-Reply-To: <23A9A636-C738-4FF6-962F-DCDC107A7AA8@bmw-carit.de> Date: Sat, 14 Jan 2017 11:45:42 -0800 Message-Id: <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com> References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

<448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> <23A9A636-C738-4FF6-962F-DCDC107A7AA8@bmw-carit.de> To: Clemens Lang X-Mailer: Apple Mail (2.3124) Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 19:45:51 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Jan 13, 2017, at 12:50 AM, Clemens Lang = wrote: >=20 > Hi, >=20 >=20 >> On 12 Jan 2017, at 23:59, Mark Hatle = wrote: >>=20 >> 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=E2=80=9D. >=20 > With System Integrity Protection disabled, pseudo should still work as = it did before, if that=E2=80=99s an acceptable step for you. >=20 > If it isn=E2=80=99t, Apple=E2=80=99s 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=E2=80=99s 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. >=20 >=20 This topic could have been clarified better, since there are multiple = ways to =E2=80=9Cbuild=E2=80=9D 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=E2=80=99s including = macOS 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..=20 Replacing a platforms POSIX version of tools with gnu versions because = your build environment didn=E2=80=99t like it, seems like a step = backwards for these types of initiatives.=20 Curious to know about long term support for POSIX systems.=20 Apple spent alot of time and effor years ago to vertify OS X as POSIX = compliant. Roger From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E928AE006EA; Sat, 14 Jan 2017 11:49:55 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [134.134.136.65 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 16EDFE004E5 for ; Sat, 14 Jan 2017 11:49:54 -0800 (PST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP; 14 Jan 2017 11:49:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,229,1477983600"; d="scan'208,217";a="53058968" Received: from oamoraso-mobl.amr.corp.intel.com ([10.254.1.5]) by orsmga005.jf.intel.com with ESMTP; 14 Jan 2017 11:49:53 -0800 From: Tim Orling Message-Id: <6694C76C-B48D-48A1-AEFB-A3B458279EC6@linux.intel.com> Mime-Version: 1.0 (Mac OS X Mail 10.2 $3259$) Date: Sat, 14 Jan 2017 11:49:55 -0800 In-Reply-To: <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com> To: Roger Smith References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

<448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> <23A9A636-C738-4FF6-962F-DCDC107A7AA8@bmw-carit.de> <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com> X-Mailer: Apple Mail (2.3259) Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 19:49:56 -0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_81776E31-6926-4FF8-851C-B9BC80B26162" --Apple-Mail=_81776E31-6926-4FF8-851C-B9BC80B26162 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 14, 2017, at 11:45 AM, Roger Smith = wrote: >=20 >>=20 >> On Jan 13, 2017, at 12:50 AM, Clemens Lang = wrote: >>=20 >> Hi, >>=20 >>=20 >>> On 12 Jan 2017, at 23:59, Mark Hatle = wrote: >>>=20 >>> 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=E2=80=9D. >>=20 >> With System Integrity Protection disabled, pseudo should still work = as it did before, if that=E2=80=99s an acceptable step for you. >>=20 >> If it isn=E2=80=99t, Apple=E2=80=99s 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=E2=80=99s 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. >>=20 >>=20 >=20 >=20 > This topic could have been clarified better, since there are multiple = ways to =E2=80=9Cbuild=E2=80=9D Yocto Project in MacOS X, >=20 > Is Building Yocto project on a POSIX system, a desire for the Yocto = project? It would allow support on all bsd UNIX=E2=80=99s including = macOS >=20 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 :) >=20 > 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..=20 >=20 > Replacing a platforms POSIX version of tools with gnu versions = because your build environment didn=E2=80=99t like it, seems like a step = backwards for these types of initiatives.=20 >=20 > Curious to know about long term support for POSIX systems.=20 >=20 > Apple spent alot of time and effor years ago to vertify OS X as POSIX = compliant. >=20 > Roger >=20 > --=20 > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto = --Apple-Mail=_81776E31-6926-4FF8-851C-B9BC80B26162 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

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=E2=80=9D.=

With System Integrity = Protection disabled, pseudo should still work as it did before, if = that=E2=80=99s an acceptable step for you.

If= it isn=E2=80=99t, Apple=E2=80=99s 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=E2=80=99s 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 =E2=80=9Cbuild=E2=80=9D 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=E2=80= =99s 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=E2=80=99= 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
https://lists.yoctoproject.org/listinfo/yocto

= --Apple-Mail=_81776E31-6926-4FF8-851C-B9BC80B26162-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 2931BE0082A; Mon, 16 Jan 2017 03:19:33 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [209.85.216.169 listed in dnsbl.sorbs.net] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.216.169 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com [209.85.216.169]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E3136E00805 for ; Mon, 16 Jan 2017 03:19:29 -0800 (PST) Received: by mail-qt0-f169.google.com with SMTP id x49so100832126qtc.2 for ; Mon, 16 Jan 2017 03:19:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rZHKP4emsKgL9br0p9Dmr6MQCLtvfsYUSxky7GJ/0XY=; b=NbVvvNriQ0V/dN1B6R1E+V6SM/tZCgujg+sjm6DQsPm1ZkV3JgYkmjld4YC8fLyo4H X+FmfHJ5MxpoC/zjBRJBL9oS2Q2Jp1BOs4RPaeqhJuOvKHFq3kzTl2e+Vv0ELyeC24/G lgCC/BgP7nHAGjPurobzLMaF8ujE3LW6qEDvrphNJ5ZiftoUn+Vv/TAEB9v341EJpPXf RuWud/lw1zYF3sVVNS00QhLMR4jYZd0FNyoE5Ir4R92JfgG8TlcdQwt4dxZbuF3/6z/q ffrerPFMUhru4Dj/xxzUz+IsE/zItOoH+LMoX/i16dlObfSC0SBIXFvdRoFlDLLpOY9l 9Cqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rZHKP4emsKgL9br0p9Dmr6MQCLtvfsYUSxky7GJ/0XY=; b=lSG/eOx22PPPX3aoZwU5uqudG6rXNZkTDs/XsRHGemzhQ3H3GKjLmwEcYXk8L1D3rr +db7KObPDc7EuH5UlO46zZyyMpY/01zo0IXcoC2QurBWUP5USDWZ5ST6/W93kEVyeo+w nHXDCfUwdgBio5l26USh3V2YBoBvqE5irwBzKcaMExVt3PgomaG9PO4rVfo+Kyjwodf2 9BMLWpVDYoZ1PL41Ue3AfUOzUm3RpVlUslMO4zFLk19381LlyFAzuDevIcMJZ4jFF9Pi 7RT7kM4rEXvdzdvWly/ztyan2EwRNmVq7yRcNzFy/VctW8EC2LSDa9Ai5xqVCfq967Zw QlcA== X-Gm-Message-State: AIkVDXKgzm9PFeHZD63fAJ2PhQjs1vdeuZui5vVTrXtJVjuZjCewXBz0udtObUD+zuwMxu+kXZWsKadsVERMvmXg X-Received: by 10.200.45.247 with SMTP id q52mr31190762qta.197.1484565568857; Mon, 16 Jan 2017 03:19:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.103.233 with HTTP; Mon, 16 Jan 2017 03:19:08 -0800 (PST) In-Reply-To: <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com> References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

= On 14 January 2017 at 19:45, Roger Smith <roger@sentientblue.com&= gt; wrote:

Is Building Yocto project on a POSIX syste= m, a desire for the Yocto project? It would allow support on all bsd UNIX= =E2=80=99s including macOS

Making OE itself= work isn't rocket science - fix a few Linuxisms in bitbake, port pseud= o to macOS.

The hard bit is then convincing the hundred-odd recipes that are ofte= n Linux-centric if not Linux specific to build under something that isn'= ;t Linux.=C2=A0 My ross/darwin branch (from before the security changes) ha= s a patch to gmp as 'echo' has different semantics. unlink() has di= fferent error codes between macOS and Linux.=C2=A0 There's a very long = tail of differences that will need patching and testing.

But if this is something= you care about, patches welcome!

Ross

--001a1139cdf060bf070546345b9e-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id CAB40E008D3; Mon, 16 Jan 2017 18:33:45 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (avery.brian[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.217.195 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [209.85.217.195 listed in dnsbl.sorbs.net] Received: from mail-ua0-f195.google.com (mail-ua0-f195.google.com [209.85.217.195]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 75DA8E007C2 for ; Mon, 16 Jan 2017 18:33:41 -0800 (PST) Received: by mail-ua0-f195.google.com with SMTP id i68so11223139uad.1 for ; Mon, 16 Jan 2017 18:33:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QPXyC67UWoAR8f5G0eo0uSOBMR9EMS3+5kESyEvw63k=; b=Gzv1A6OPvceZURe8QbhHQIbgOk6OEEhcR6dikq9uB4vFzEobA9PtPUfAH0+yKHPvDN 3Y68WjB59ichqzROU470jMbzlOJ6NG3K2//3XuAVGPhXkexaQf9932iZqHZmsJF3rPV8 6WOeTupFZoDgwBAqgP8tNFje4zT8NWJAvaMcHIId+BHqu01iMybWnDmksBM6QIi2Ugg4 I1Dvp3RIP+paF2gNs8Z43z5LiMYc9Dh/4nFjWMHMBjwTw22Y8H/KI9W9TpJovEqV1yYj tTacrhW/Ut3yXATfvKbBLApx7V6kG+kGrbbC7WohO8SV67YRAlUDHf8+1Dd4VsIWcXmY jU1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QPXyC67UWoAR8f5G0eo0uSOBMR9EMS3+5kESyEvw63k=; b=Vb7T86e02ZftnVUzTz+PZLDeH2YB6e302njTOpfxTmqfYrV+fx7QbY3A8CuobGUZEk Mioe6580SK0iZUv/CzomwLQqoVz61Ug8iLTLuYPmZE5kaWgg1emKb2IRESwLlC+cAbCl KCvhPBYlbosPQN0dN8vN3PV9mZcd/JUDGfYCN1KuHpFz2uEYYTzQxCAZdopDeSF0P8gC kCALGZFaSo/q2tyq/ZCMjmzbcfEHgdr1YEpqDVGeteamaUps101TxdlT60QJVQLvxu1N ehwHjXUmy5Fa4iQbig8hVOB/1DPR00z9AKfT7avhIFtfIE0uZTcXguk5eppIZdDrfrik zoZw== X-Gm-Message-State: AIkVDXKBj5Bx/7CYhn+QBcDuu5CfmyMlKx9Yxvum8LG/g2TzGE1vnBUwwKt+RRIRGnXgXDYNpAtLCunpDJCNjg== X-Received: by 10.176.92.153 with SMTP id s25mr8582855uaf.177.1484620421101; Mon, 16 Jan 2017 18:33:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.60.199 with HTTP; Mon, 16 Jan 2017 18:33:40 -0800 (PST) In-Reply-To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com>

<448FE605-0D5E-4057-BF49-9EFFBC5CB8DD@sentientblue.com> <23A9A636-C738-4FF6-962F-DCDC107A7AA8@bmw-carit.de> <656A5471-015B-4BE2-BEDA-7B9C98423EB8@sentientblue.com> From: Brian Avery Date: Mon, 16 Jan 2017 18:33:40 -0800 Message-ID: To: "Burton, Ross" Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 02:33:45 -0000 Content-Type: multipart/alternative; boundary=f403045e2366d37dd40546412038 --f403045e2366d37dd40546412038 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, A couple of comments even though I'm coming late to the discussion. So, from what I've understood from the above, the main issue with the docker approach to building a yocto/oe image on the mac is that it was much slower... Here's some numbers that don=E2=80=99t quite agree with that as= sertion: I ran a couple of tests, some on my linux box and some on my mac laptop. The tests involved building core-image-minimal for a qemux86 target. All the downloads were in place. There was no sstate, parse cache, nor was there an existing tmp directory before the tests were run. My linux box has a Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz , 36 cores. My mac laptop has a Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz. The test is "$ time bitbake core-image-minimal" Here are the results of the tests: Linux box Ubuntu 14.04 clock : 30m24.024 user : 229m12.324 sys : 20m10.188 =E2=80=94- Linux box Ubuntu 14.04 running inside docker 1.12.3 using crops/poky:latest clock : 30m37.66 user : 231m35.984 sys : 31m20.204 =E2=80=94=E2=80=94 Linux box Ubuntu 14.04 running inside docker 1.12.3 using crops/poky:latest I set the following in my local.conf file: BB_NUMBER_THREADS=3D=E2=80=9C2=E2=80=9D BB_NUMBER_PARSE_THREADS=3D=E2=80=9C2=E2=80=9D PARALLEL_MAKE=3D=E2=80=9C-j 2=E2=80=9D AND I constrained docker to 2 cpu cores and 8 gb of ram (This is what I have my mac laptop set to). clock : 127m8.523 user : 201m32.468 sys : 19m54.052 =E2=80=94 Mac OSX laptop - running docker 1.12.5 2 cpus, 8gb ram I set the following in my local.conf file: BB_NUMBER_THREADS=3D=E2=80=9C2=E2=80=9D BB_NUMBER_PARSE_THREADS=3D=E2=80=9C2=E2=80=9D PARALLEL_MAKE=3D=E2=80=9C-j 2=E2=80=9D clock : 99m31.190 user : 137m40.400 sys : 18m38.650 =E2=80=94=E2=80=94 So, from the above, it looks like my mac is actually faster when it has the same number of cores and memory. I haven=E2=80=99t seen any particular slo= wdown with running docker linux programs on the mac other than those caused by the difference in horsepower between my build server and my laptop. Thanks, Brian Avery an Intel employee p.s. Andrea, would you mind replying with how you changed the docker run to make loopback work? I=E2=80=99d like to add it to the docs. Also, if you co= uld point me at what layers you used to make resin, I=E2=80=99d like to give th= at a try as well. Right now, we are providing a bare bones environment but I=E2=80= =99d be happy to write up a howto for inheriting from our images to customize your own for special purposes (like doing builds that require loopback mounts, for instance). On Mon, Jan 16, 2017 at 3:19 AM, Burton, Ross wrote= : > > On 14 January 2017 at 19:45, Roger Smith wrote: > >> Is Building Yocto project on a POSIX system, a desire for the Yocto >> project? It would allow support on all bsd UNIX=E2=80=99s including macO= S >> > > Making OE itself work isn't rocket science - fix a few Linuxisms in > bitbake, port pseudo to macOS. > > The hard bit is then convincing the hundred-odd recipes that are often > Linux-centric if not Linux specific to build under something that isn't > Linux. My ross/darwin branch (from before the security changes) has a > patch to gmp as 'echo' has different semantics. unlink() has different > error codes between macOS and Linux. There's a very long tail of > differences that will need patching and testing. > > But if this is something you care about, patches welcome! > > Ross > > > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > --f403045e2366d37dd40546412038 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi,

A couple of comments even though I'm coming late = to the discussion.

So, from what I've understood from the above, the= main issue with the docker approach to building a yocto/oe image on the ma= c is that it was much slower...=C2=A0 Here's =C2=A0some numbers that do= n=E2=80=99t quite agree with that assertion:

I ran a couple of tests, some on my linux box and som= e on my mac laptop.=C2=A0 The tests involved building core-image-minimal fo= r a qemux86 target. All the downloads were in place. There was no sstate, p= arse cache, nor was there an existing tmp directory before the tests were r= un.

My linux box has a Intel(R) = Xeon(R) CPU E5-2699 v3 @ 2.30GHz=C2=A0, 36 cores.=C2=A0 My mac laptop has a= Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz.

The test is "$ time bitbake core-image-minim= al"

Here are the results of the tests:=

Linux box Ubuntu 14.04

clock : 30m24.024=C2=A0

user =C2=A0: 229m12.324=C2= =A0

sys =C2=A0 =C2=A0: 20m10.188=

=E2=80=94-

Linux box Ubuntu 14.04 runni= ng inside docker 1.12.3 using crops/poky:latest

clock : 30m37.66=C2=A0

user =C2=A0: 231m35.984=C2= =A0

sys =C2=A0 =C2=A0: 31m20.204=

=E2=80=94=E2=80=94

Linux box Ubuntu 14.04 runni= ng inside docker 1.12.3 using crops/poky:latest=C2=A0

I set the following in my lo= cal.conf file:

BB_NUMBER_THREADS=3D=E2=80= =9C2=E2=80=9D

BB_NUMBER_PARSE_THREADS=3D= =E2=80=9C2=E2=80=9D

PARALLEL_MAKE=3D=E2=80=9C-j = 2=E2=80=9D

AND I constrained docker to = 2 cpu cores and 8 gb of ram (This is what I have my mac laptop set to).

clock :=C2=A0127m8.523

user =C2=A0:=C2=A0201m32.468

sys =C2=A0 =C2=A0:=C2=A019m54.052

=E2=80=94

Mac OSX laptop - running doc= ker 1.12.5 2 cpus, 8gb ram=C2=A0

I set the following in my local.conf file:

BB_NUMBER_THREADS=3D=E2=80= =9C2=E2=80=9D

BB_NUMBER_PARSE_THREADS=3D= =E2=80=9C2=E2=80=9D

PARALLEL_MAKE=3D=E2=80=9C-j = 2=E2=80=9D

clock : 99m31.190

user =C2=A0:=C2=A0137m40.400=

sys =C2=A0 =C2=A0:=C2=A018m3= 8.650

=E2=80=94=E2=80=94

So, from the above, it looks= like my mac is actually faster when it has the same number of cores and me= mory.=C2=A0 I haven=E2=80=99t seen any particular slowdown with running doc= ker linux programs on the mac other than those caused by the difference in = horsepower between my build server and my laptop.

Thanks,=C2=A0

Brian Avery

an Intel employee

p.s. Andrea, would you mind = replying with how you changed the docker run to make loopback work? I=E2=80= =99d like to add it to the docs. Also, if you could point me at what layers= you used to make resin, I=E2=80=99d like to give that a try as well.=C2=A0= Right now, we are providing a bare bones environment but I=E2=80=99d be ha= ppy to write up a howto for inheriting from our images to customize your ow= n for special purposes (like doing builds that require loopback mounts, for= instance).

On Mon, Jan 16, 2017 at = 3:19 AM, Burton, Ross <ross.burton@intel.com> wrote:
=

=
On 14 January 2017 at 19:45= , Roger Smith <roger@sentientblue.com> wrote:
Is Building Yocto project on a POSIX system, a desire for the Yoc= to project? It would allow support on all bsd UNIX=E2=80=99s including macO= S

Making OE itself work isn't ro= cket science - fix a few Linuxisms in bitbake, port pseudo to macOS.

<= div class=3D"gmail_extra">

The hard bit= is then convincing the hundred-odd recipes that are often Linux-centric if= not Linux specific to build under something that isn't Linux.=C2=A0 My= ross/darwin branch (from before the security changes) has a patch to gmp a= s 'echo' has different semantics. unlink() has different error code= s between macOS and Linux.=C2=A0 There's a very long tail of difference= s that will need patching and testing.

But if this is something you care about, p= atches welcome!

Ross