From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] glibc
Date: Tue, 30 Sep 2008 19:20:54 -0700 [thread overview]
Message-ID: <1222827654.6792.0.camel@kokopelli> (raw)
has anybody built buildroot with glibc support? or is it in there and I
just missed it?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
next reply other threads:[~2008-10-01 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:20 Brian Beattie [this message]
2008-10-01 7:53 ` [Buildroot] glibc Bernhard Reutner-Fischer
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=1222827654.6792.0.camel@kokopelli \
--to=beattie@beattie-home.net \
--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.