* [Buildroot] glibc vs. uclibc
@ 2006-08-28 17:51 Bill Somerville
2006-08-30 16:55 ` Rob Landley
0 siblings, 1 reply; 2+ messages in thread
From: Bill Somerville @ 2006-08-28 17:51 UTC (permalink / raw)
To: buildroot
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?
--
Bill Somerville
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] glibc vs. uclibc
2006-08-28 17:51 [Buildroot] glibc vs. uclibc Bill Somerville
@ 2006-08-30 16:55 ` Rob Landley
0 siblings, 0 replies; 2+ messages in thread
From: Rob Landley @ 2006-08-30 16:55 UTC (permalink / raw)
To: buildroot
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-08-30 16:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-28 17:51 [Buildroot] glibc vs. uclibc Bill Somerville
2006-08-30 16:55 ` Rob Landley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox