From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] glibc
Date: Wed, 1 Oct 2008 09:53:03 +0200 [thread overview]
Message-ID: <20081001075303.GC18546@mx.loc> (raw)
In-Reply-To: <1222827654.6792.0.camel@kokopelli>
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.
Good luck.
next prev parent reply other threads:[~2008-10-01 7:53 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 [this message]
2008-10-04 22:55 ` Grant Likely
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=20081001075303.GC18546@mx.loc \
--to=rep.dot.nop@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.