Switching from uClibc to glibc as the default in Buildroot?

[Thomas Petazzoni]

Dear Khem Raj,

On Tue, 18 Feb 2014 18:43:41 -0800, Khem Raj wrote:

> > There are a great number of fixes since the last numbered release and I for one would greatly appreciate having at least a "testing" release with a bumped version number to use. Other than the ldso stat call problem I reported a couple of weeks ago, uClibc trunk has been working fairly well, and most bugs I run into are the typical growing pains of toolchain building from scratch rather than uClibc problems.
> 
> so get going start testing git/master and report issues or successes you have.
> help in testing it out, run uclibc test suites or any others you have setups for

Please break the chicken-and-egg problem, and release 2014.02-rc1 right
now, spit out a call for testing, and release 2014.02 at the end of the
month. (Or pick any other date you want, those are just suggestions).

It's by creating rhythm and cadence in the release schedule that you
will encourage people to test the release candidates and report bugs.
Nobody wants to test a moving git/master.

> > I don't think that a "Git release" is appropriate for these reasons. Besides, if you did tag a Git commit with a version number, there's also no reason not to put out a tarball to go with it, right?
> 
> it needs some work whereas with git you can download the tars from cgit, but not a big issue. We can release tar balls too.

As I said earlier, I believe tarballs are still useful today.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com