Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Switching from uClibc to glibc as the default in Buildroot?
Date: Wed, 19 Feb 2014 09:32:02 +0100	[thread overview]
Message-ID: <87y5171p19.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140219092112.6f359a55@skate> (Thomas Petazzoni's message of "Wed, 19 Feb 2014 09:21:12 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > 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).

Inded. When Bernard suggested the same last year I did test and reported
issues, but never got any reply:

http://lists.uclibc.org/pipermail/uclibc/2013-November/048093.html

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-19  8:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 22:14 [Buildroot] Switching from uClibc to glibc as the default in Buildroot? Thomas Petazzoni
     [not found] ` <20140218231759.GS184@brightrain.aerifal.cx>
2014-02-18 23:26   ` Thomas Petazzoni
     [not found]     ` <20140219024634.GT184@brightrain.aerifal.cx>
2014-02-19  8:13       ` Thomas Petazzoni
     [not found] ` <CAMKF1soCcLba_EacJLe7f9fM9=gFsTJYj0kaz6YzoXzEY1rx2A@mail.gmail.com>
2014-02-19  8:18   ` Thomas Petazzoni
2014-02-19  8:29     ` Peter Korsgaard
     [not found]   ` <fd7802bd-3f37-4d70-ad22-2e46fc452b4b@email.android.com>
     [not found]     ` <66DCE5C2-E7A6-4634-8C79-441DA9FC46FB@gmail.com>
2014-02-19  8:21       ` Thomas Petazzoni
2014-02-19  8:32         ` Peter Korsgaard [this message]
2014-02-19 13:21           ` Mike Zick
2014-03-07  8:07           ` Thomas De Schampheleire
2014-03-12 20:24             ` Bernhard Reutner-Fischer
2014-03-13 10:45               ` Vineet Gupta

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=87y5171p19.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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