Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: bump default to version 2.23
Date: Wed, 22 Jun 2016 17:13:17 +0200	[thread overview]
Message-ID: <20160622171317.79fbea7e@free-electrons.com> (raw)
In-Reply-To: <42d8119e5e64c7a67018770b3f029146@zacarias.com.ar>

Hello,

On Wed, 22 Jun 2016 12:02:15 -0300, Gustavo Zacarias wrote:
> On 2016-06-22 11:53, Peter Korsgaard wrote:
> 
> > Why? In the past we have defaulted to latest-1 and 2.24 isn't released
> > yet.  
> 
> Why not?

Default to n-1 has been our tradition for gcc/binutils/glibc for ages.

> We're using latest uclibc-ng if it's suitable/for example.

Cause uclibc-ng doesn't evolve much beyond bug fixes at the moment, so
there's not really a good reason to not use the latest version.

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

  reply	other threads:[~2016-06-22 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 10:09 [Buildroot] [PATCH] glibc: bump default to version 2.23 Gustavo Zacarias
2016-06-22 14:53 ` Peter Korsgaard
2016-06-22 15:02   ` Gustavo Zacarias
2016-06-22 15:13     ` Thomas Petazzoni [this message]
2016-06-22 15:18       ` Gustavo Zacarias
2016-06-22 15:27         ` Peter Korsgaard
2016-06-22 20:38           ` Arnout Vandecappelle
2016-06-22 22:58             ` Gustavo Zacarias
2016-06-27 20:00               ` Peter Korsgaard
2016-06-27 19:27             ` Peter Korsgaard
2016-06-27 20:56               ` Arnout Vandecappelle

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=20160622171317.79fbea7e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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