Robert, I use the Linaro toolchain for exactly the same reasons as you. Aside from the fact that I follow your guide as closely as possible, and deviating from that would cause more headaches than it is worth. All one has to do is read all the half fast copied blog postings out there to realize this . . . that lead to "HALP ITS BROKED" posts on these groups . . .heh.
As far as the crosstool-ng aspect. I just mean that you get eaxctly what *you* want when you build your own toolchain. On the other side of that coin. For me personally, I probably do not know everything I need to know to build a proper toolchain for the BBB. After that, failed attempts would get old fast, or worse yet seemingly good attempts that could turn "tragic" in a hurry. On Sat, Jul 26, 2014 at 8:15 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > > On Jul 26, 2014 6:33 PM, "William Hermans" <yyrk...@gmail.com> wrote: > > > > Everything being equal I think crosstool-ng is the way to go. There are > a few things I do not like about the Linaro toolchain, and the prepackaged > libc is the main one on my mind. > > If you dig into linaro's build script for those binaries, it is actually > crosstool-ng.. Its just tied with a later ubunutu/Linaro specific libc. > > It just works, is why I use it exclusively now. Some of us remember the > code soucery days when they'd magically break stuff between releases. > Thankfully Angstroms cross compiler was around back then. Eventually those > guys went to Linaro and fixed GCC. > > > > > Personally, for various things, I prefer building things from *scratch*. > This is the side of me that also loves this concept of Gentoo. But the > practicalities of every day business almost always get in the way. Now, I > have a time investment spent learning about the Linaro toolchain. Which > admitedly is not a huge amount. Not like Debian versus Gentoo ( for me ), > where I've been using Debian since the mid 90's. > > > > > > > > > > On Sat, Jul 26, 2014 at 3:59 PM, Douglas Jerome <doug...@ttylinux.org> > wrote: > >> > >> On 07/26/14 15:10, Lucas Tanure wrote: > >>> > >>> Jerome, > >>> > >>> Sorry I didn't understand what you want, or complain about that page. > >>> Feel free to edit and add what you think is important. > >>> I can only write about things I know, and understand. That tip about > >>> Linaro toolchain was very good thanks, I will take a look. > >>> The wiki is for anyone, from anyone. So add your way, so people can > know of. > >> > >> > >> Whoa, I really don't mean to sound cross about anything. > >> For that page, my critique is: from the terseness of the > >> crosstool-ng part it lacks usefulness and I'm willing to > >> help. > >> My first name is Douglas, not Jerome. > >> > >> > >>> > >>> Willian, > >>> > >>> I feel the same way, I just want to build my kernel, boot and use. I'm > >>> not a expert, I'm a newbie, so I need first a easier and faster way to > >>> get where I want. > >>> For me, what I know about crosstool-ng is that you can choose many > >>> variables and build a perfect compiler for you, using uLibc, gLibc > >>> what ever you need. And I don't see yet why "In that case perhaps > >>> crosstool-ng may be the way to go." . What I'm missing in this case ? > >>> What crosstool-ng is so much better than a preconfigured gcc from > >>> ubuntu servers ? > >> > >> > >> For what it's worth, from someone who uses crosstool-ng but not > >> a pre-built cross tool chain, I don't think it's fair to say > >> crosstool-ng is so much better in an open ended way. > >> > >> When you build code for a Linux system the tool chain supplies > >> the glibc interface (header files and library files) which has > >> the Linux kernel system call interface; if you want some > >> particular version of those, then building your own cross-tool > >> chain with those versions can be so much better than using a > >> pre-built cross tool chain. If you use a pre-built cross tool > >> chain, what versions of glibc and Linuc kernel is your > >> cross-built code targeted to? I am being glibc-centric > >> here, I know. > >> > >> Cheers. > >> > >> > >> -- > >> 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.
