From: Grant Likely <grant.likely@secretlab.ca>
To: buildroot@busybox.net
Subject: [Buildroot] glibc
Date: Sat, 4 Oct 2008 16:55:05 -0600 [thread overview]
Message-ID: <20081004225505.GA11515@secretlab.ca> (raw)
In-Reply-To: <20081001075303.GC18546@mx.loc>
On Wed, Oct 01, 2008 at 09:53:03AM +0200, Bernhard Reutner-Fischer wrote:
> On Tue, Sep 30, 2008 at 07:20:54PM -0700, Brian Beattie wrote:
> >has anybody built buildroot with glibc support? or is it in there and I
> >just missed it?
>
> You can theoretically use an "external toolchain" which uses glibc. Not
> sure what purpose such a thing would serve though.
I've done just such a thing. I've used the codesourcery toolchain for
powerpc which uses glibc. It works well for me.
The reason I did it was that I was having trouble getting buildroot to
produce a reliable crosscompiler for powerpc and wanted to use something
known-good and stable since gcc cross compilers still seem to have a bit
of black-magic associated with building one that works and what patches
are required, especially in PPC land.
g.
prev parent reply other threads:[~2008-10-04 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:20 [Buildroot] glibc Brian Beattie
2008-10-01 7:53 ` Bernhard Reutner-Fischer
2008-10-04 22:55 ` Grant Likely [this message]
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=20081004225505.GA11515@secretlab.ca \
--to=grant.likely@secretlab.ca \
--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