From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot using glibc
Date: Wed, 10 Dec 2008 09:23:32 +0100 [thread overview]
Message-ID: <20081210092332.0f9e74bd@surf> (raw)
In-Reply-To: <008a01c95a00$53f2a300$4d01a8c0@signet>
Le Tue, 9 Dec 2008 18:46:20 +0530,
"P Jagadeesh Maiya" <pjmaiya@signal-networks.com> a ?crit :
> I want to use buildroot built using glibc instead of ulibc. I have
> gone through entire mailing list archeive, but nowhere I am not
> getting any information or link to get patch for glibc. Can anyone
> provide any refernce for the patch so that buildroot can be used with
> glibc.
The simplest solution is to use an external toolchain. I already used a
Codesource glibc-based toolchain with Buildroot, and it worked nicely.
The only needed modification were :
* Modifications to get external toolchains to work (I have sent a
patch recently for this)
* Specifying the proper values for the BR2_TOOLCHAIN_EXTERNAL_LIB_C and
BR2_TOOLCHAIN_EXTERNAL_LIBS configuration variables.
If you want to *generate* a glibc-toolchain with Buildroot, it is
probably going to be a more tedious work. But if you happen to do that,
please submit patches!
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-12-10 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 13:16 [Buildroot] buildroot using glibc P Jagadeesh Maiya
2008-12-10 8:23 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-09 20:31 Tim Barr
2008-12-09 23:39 ` Hamish Moffatt
2008-12-10 12:16 P Jagadeesh Maiya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081210092332.0f9e74bd@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox