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.
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.
