This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Steven, Quoting Steven Geerts <Steven.geerts@thomson.net>: > Buildroot isn't actually the thing that I want. I want to have my own > toolchain setup with all the options that we specify. > My toolchain is already built with newlib for an arm11 and it is > working. > Actually why I want to use uclibc is because busybox won't build with > newlib libraries. :-(. > I've been looking form information about gcc with uclibc and I always > get to the buildroot option, which I don't want. > Isn't there any option, just like newlib, where I can just say build gcc > with uclibc???? As stated by Steven J. Hill, there is crosstool which purpose is to built cross-toolchains (http://www.kegel.com/crosstool) without building a full root file system, which seems what you want. Recently, uClibc support was added to crosstool (I did that) as a patch against mainline. Look into the archives at http://sources.redhat.com/ml/crossgcc in late July. This is still WIP, but is fully functionnal for me: armv5{b,l}-xscale-linux-uclibc as targets. On a side note, would you share your build procedure using newlib? Regards, Yann E. MORIN. -- Yann E. MORIN Roaming in the world... ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |