@Ross I've been building the kernel for the beaglebone black using Roberts eewiki instructions for around two years now. A lot of that was done from a virtualbox VM. I've even been using that same vm to load the rootfs for that A5A over our network.
Anyway, this is not meant as eWenus waggling, just trying to reinforce the fact that using a Virtualbox VM can work really well. For me, it has been pretty Rock solid. On Fri, May 29, 2015 at 3:15 PM, William Hermans <yyrk...@gmail.com> wrote: > Well, I use Windows for a Desktop, and have not really had much experience > with OSX hands on. But what I do know is that virtualbox works really well > on Windows, and Virtualbox has binaries for OSX. > > I have used those Linaro binaries for Windows by the way, and for simple > applications they seem to work fine *BUT* that whole avenue to me just > seems wrong. Not to mention that it would be very difficult to build the > kernel on Windows, but probably not impossible. > > Personally, I think all in all Debian is best for building Debian. But if > you just need to build / compile "simple" applications. Ubuntu 14.04 has > cross tools for armhf that seem to work fine. If needing help setting that > up, just watch DR. Molloy's Videos on youtube from a year or two ago. > Forthe original beaglebone ( white ) Substituting *armhf* tools for armel > tools. > > On Fri, May 29, 2015 at 1:00 PM, Ross Morrison <r...@buy-ei.com> wrote: > >> I concur, I'm building a 3.8.13-bone71-1 right now on my Macbook Pro OS >> X Yosemite system. I use a Transcend card reader for creating the uSD cards >> from the Linux console in the VM. I've been doing this for sometime and >> everything works fine. I haven't setup a cross dev system on the VM yet, >> but will and expect no problems. The dist/version of Linux in my VM is >> Kbuntu 14.04 32bit. The version of VirtualBox is 4.3.26 r98988. This is a >> great way to go if you don't run Windoze. I'm strictly a Linux and Apple >> person and very happy in that respect. >> >> >> >> On 05/29/2015 11:56 AM, William Hermans wrote: >> >> Probably the easiest way would be to do as Robert suggests and use a >> VM. Virtualbox, and debian works fine. The only obstacle you may run into >> is have an sdcard reader recognized in the VM. *if* even needed. >> >> Depending on what you're trying to do, and how you want to do it, a >> flash card reader may not even be needed. OSX should have access to better >> tools for "flashing" an sdcard than Windows. Then, one would / could just >> use various tools over the host only network to transfer files between the >> VM and OSX. If just simple executables, sshfs, netcat, and other standard >> UNIX tool would work fine to transfer files directly from one system to the >> other. >> >> On Fri, May 29, 2015 at 7:17 AM, Robert Nelson <robertcnel...@gmail.com> >> wrote: >> >>> On Fri, May 29, 2015 at 4:07 AM, rei_vilo via BeagleBoard >>> <beagleboard@googlegroups.com> wrote: >>> > I'm trying to cross-compile on my Mac against the BeagleBone. >>> > >>> > Surprisingly, the Linaro tool-chain is only available for Windows and >>> Linux, >>> > not Mac OS X. >>> > >>> > The only binary I've found so far comes from >>> > >>> http://www.welzels.de/blog/en/arm-cross-compiling-with-mac-os-x/comment-page-1/ >>> > , but debugging doesn't work. The sysroots files aren't provided. >>> > >>> > Other options include: >>> > >>> > Mentor Graphics —previously Sourcery Mentor— but the tool-chain is no >>> longer >>> > free, >>> > Carlson Minot but it doesn't feature hardware FPU, while Debian >>> requires it. >>> > >>> > Most blogs suggest to create and host a Linux virtual machine. >>> > >>> > But all tentatives to build the tool-chain myself end with error >>> messages >>> > and failures. >>> > >>> > Any plan to deliver a tool-chain binary for Mac OS X? >>> >>> We don't 'provide' any toolchains.. >>> >>> Feel free to ping linaro about mac os x support, or setup a vm.. >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
