From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] glibc vs. uclibc
Date: Wed, 30 Aug 2006 12:55:52 -0400 [thread overview]
Message-ID: <200608301255.53182.rob@landley.net> (raw)
In-Reply-To: <1156787482.30424.16.camel@wallace.classdesign.local>
On Monday 28 August 2006 1:51 pm, Bill Somerville wrote:
> Hi
>
> I am forced to use glibc by a closed source package from Intel (IPP) so
> I am having to use a rather dated patch from the crosstool project to
> hack with the buildroot package. This is very unsatisfactory as the
> patch only applies cleanly to a very old revision of buildroot.
>
> Is there fresher way of using buildroot with glibc?
Buildroot started life as a test harness for uClibc. It's maintained by the
uClibc developers as a way of generating uClibc toolchains for various
platforms, and building packages against uClibc. It was only about a month
ago that buildroot got its own mailing list rather than using the uclibc
mailing list, and said mailing list is still "buildroot at uclibc.org".
Did this answer your question?
Rob
--
Never bet against the cheap plastic solution.
prev parent reply other threads:[~2006-08-30 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 17:51 [Buildroot] glibc vs. uclibc Bill Somerville
2006-08-30 16:55 ` Rob Landley [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=200608301255.53182.rob@landley.net \
--to=rob@landley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox