Nothing. But similar to what Robert said. Linaro is a "known quantity". Just like picking a name brand when buying hardware based on prior experience. I have experience with various aspects of Debian dating back to the 90's. From then until now I have experienced a lot of grief trying to set many thing up. So, when I find something that works, and works well enough. I tend to stick with it. This is one aspect of why I refused to use Angstrom.
When I first started with the BBB last year, which coincidentally is when I first started learning about embedded Linux *and* had zero experience writing code on the same. I had a lot to learn all at the same time, and I still have a lot to learn. So this is not about zealotry for me, but a very fine balancing act of what works, and what I can live with to achieve my own end goals. In this same context, there are many things which I may prefer to do / use, but have a very steep learning curve. This is the only real problem I have with crosstool-ng. Not that it is bad, or would take too long to learn how to use. I just do not have the time to mess with it. Not while getting the other things done which I hold higher in priority. Enter Linaro . . . I started using Robert's build guide a week after we got our BBB's. I was reading about various toolchains at the time trying to decide which one was best for me, when I had a sudden realization. "Hey, I already have a tool chain here . . ." 15 minutes later I wrote a very simple CPU load test - test application and had it loading my CPU at 60%. Knowing hardly anything about the toolchain, writing C for Linux, or the prepackaged libc. Granted, I did bring some prior experience with gcc with me. On Mon, Jul 28, 2014 at 5:21 AM, Robert Nelson <[email protected]> wrote: > On Mon, Jul 28, 2014 at 6:44 AM, Lucas Tanure <[email protected]> wrote: > > Hi, > > > > I will add a page only for toolchains, so the user can know about the > options. > > The wiki needs more information on how build root filesystem, > > toolchain options, yocto, etc. So, I still have a lot of stuff to dig > > and writ about it. > > > > @Robert/William, > > Could explain me what is the problems that you run into with others > > toolchains rather than linaro toolchain ? > > So I can put this info in the new page. > > Lucas, it's more of the old saying: > > Fool me once, shame on you; fool me twice, shame on me. > > http://elinux.org/ARMCompilers#Limitations > > Otherwise, you should use the search feature of this list, it goes back 6 > years. > > Anywho, ever since Linaro started putting resources into fixing gcc > for arm/arm64, like 3-4 years ago. GCC mostly just works now days. > > Why a new page? At this point mainline gcc-4.9 is fine. (and really > everything after gcc-4.6).. You'd just be creating a revisionist > history of gcc page. > > Regards, > > -- > Robert Nelson > http://www.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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
