* [Buildroot] glibc vs uclibc @ 2011-03-17 14:37 Charles Krinke 2011-03-17 18:33 ` Diego Iastrubni 2011-03-19 7:42 ` Thomas Petazzoni 0 siblings, 2 replies; 5+ messages in thread From: Charles Krinke @ 2011-03-17 14:37 UTC (permalink / raw) To: buildroot Gentlemen: I have a request to provide our MPC8323E build with both uclibc and glibc support in seperate builds so this leads to a question or at least an education of my naivety. Can we build glibc as well as uclibc with buildroot? If so, how is it done? I *did* go looking for this switch and did not find it, so this is the opportunity for someone to say "its right there in file x, Charles" -- Charles Krinke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110317/1b5a57ad/attachment.html> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] glibc vs uclibc 2011-03-17 14:37 [Buildroot] glibc vs uclibc Charles Krinke @ 2011-03-17 18:33 ` Diego Iastrubni 2011-03-17 21:57 ` Charles Krinke 2011-03-19 7:42 ` Thomas Petazzoni 1 sibling, 1 reply; 5+ messages in thread From: Diego Iastrubni @ 2011-03-17 18:33 UTC (permalink / raw) To: buildroot You need now different configurations. Since rebuild of the whole target is pretty heavy - I suggest using tow different checkouts. On Thu, Mar 17, 2011 at 4:37 PM, Charles Krinke <charles.krinke@gmail.com>wrote: > Gentlemen: > > I have a request to provide our MPC8323E build with both uclibc and glibc > support in seperate builds so this leads to a question or at least an > education of my naivety. > > Can we build glibc as well as uclibc with buildroot? If so, how is it done? > I *did* go looking for this switch and did not find it, so this is the > opportunity for someone to say "its right there in file x, Charles" > > -- > Charles Krinke > > > > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110317/c2d0b6ce/attachment-0001.html> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] glibc vs uclibc 2011-03-17 18:33 ` Diego Iastrubni @ 2011-03-17 21:57 ` Charles Krinke 2011-03-17 22:06 ` Yann E. MORIN 0 siblings, 1 reply; 5+ messages in thread From: Charles Krinke @ 2011-03-17 21:57 UTC (permalink / raw) To: buildroot I'm sorry, I don't understand. Can you give me a few details on 'how one builds a root filesystsm with glibc instead of uclibc, please? On Mar 17, 2011 11:33 AM, "Diego Iastrubni" <diegoiast@gmail.com> wrote: > You need now different configurations. Since rebuild of the whole target is > pretty heavy - I suggest using tow different checkouts. > > On Thu, Mar 17, 2011 at 4:37 PM, Charles Krinke <charles.krinke@gmail.com >wrote: > >> Gentlemen: >> >> I have a request to provide our MPC8323E build with both uclibc and glibc >> support in seperate builds so this leads to a question or at least an >> education of my naivety. >> >> Can we build glibc as well as uclibc with buildroot? If so, how is it done? >> I *did* go looking for this switch and did not find it, so this is the >> opportunity for someone to say "its right there in file x, Charles" >> >> -- >> Charles Krinke >> >> >> >> _______________________________________________ >> buildroot mailing list >> buildroot at busybox.net >> http://lists.busybox.net/mailman/listinfo/buildroot >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110317/6e515dca/attachment.html> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] glibc vs uclibc 2011-03-17 21:57 ` Charles Krinke @ 2011-03-17 22:06 ` Yann E. MORIN 0 siblings, 0 replies; 5+ messages in thread From: Yann E. MORIN @ 2011-03-17 22:06 UTC (permalink / raw) To: buildroot Charles, All, On Thursday 17 March 2011 22:57:42 Charles Krinke wrote: > I'm sorry, I don't understand. Can you give me a few details on 'how one > builds a root filesystsm with glibc instead of uclibc, please? You have to use an external toolchain. First, either build your own toolchain, or get a pre-built one. Second, configure buildroot to use that toolchain. In menuconfig: Toolchain ---> Toolchain type (External toolchain) And then enter appropriate location and prefix. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] glibc vs uclibc 2011-03-17 14:37 [Buildroot] glibc vs uclibc Charles Krinke 2011-03-17 18:33 ` Diego Iastrubni @ 2011-03-19 7:42 ` Thomas Petazzoni 1 sibling, 0 replies; 5+ messages in thread From: Thomas Petazzoni @ 2011-03-19 7:42 UTC (permalink / raw) To: buildroot Hello Charles, On Thu, 17 Mar 2011 07:37:20 -0700 Charles Krinke <charles.krinke@gmail.com> wrote: > I have a request to provide our MPC8323E build with both uclibc and > glibc support in seperate builds so this leads to a question or at > least an education of my naivety. > > Can we build glibc as well as uclibc with buildroot? If so, how is it > done? I *did* go looking for this switch and did not find it, so this > is the opportunity for someone to say "its right there in file x, > Charles" In Buildroot, there are three ways to handle the toolchain "problem" : * Let Buildroot generate a toolchain. This has been the traditional and default Buildroot configuration for years, but is limited to uClibc based toolchains. * Let Buildroot use an external toolchain. In that case, Buildroot does not build the toolchain, it relies on an already existing one. You can get existing pre-built external toolchains from CodeSourcery for example, but you can also build your own with Yann E. Morin's Crosstool-NG project. Since Buildroot is no longer responsible for the toolchain, it's up to the existing toolchain to be glibc or uclibc based. CodeSourcery toolchains are generally glibc-based, but Crosstool-NG allows to build glibc, eglibc or uclibc based toolchains. * Let Buildroot use Crosstool-NG as a backend to compile the toolchain. In that case Buildroot will build the toolchain and not rely on an existing one, but instead of using internal code to do so, it uses Crosstool-NG to do the work. As Crosstool-NG is used, you can also build glibc, eglibc or uclibc based toolchains here. To sum up: with the two last options, yes, you can produce and use glibc and uclibc based toolchains. I am regularly using both. Regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-03-19 7:42 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-03-17 14:37 [Buildroot] glibc vs uclibc Charles Krinke 2011-03-17 18:33 ` Diego Iastrubni 2011-03-17 21:57 ` Charles Krinke 2011-03-17 22:06 ` Yann E. MORIN 2011-03-19 7:42 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox