All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] eglibc: bump to version 2.19 SVN R25243
Date: Tue, 08 Apr 2014 08:52:44 -0300	[thread overview]
Message-ID: <5343E30C.1090703@zacarias.com.ar> (raw)
In-Reply-To: <20140407154148.2b35dd34@skate>

On 04/07/2014 10:41 AM, Thomas Petazzoni wrote:

>> My opinion is that we should just keep it as simple as possible.
>> If there's a special need for some architecture (like microblaze) let it
>> be so, but really unless we know there's some issue or exception i don't
>> think there's much value in keeping multiple versions, specially since
>> *glibc is backwards ABI compatible.
> 
> Fine with me. My impression so far was that for critical components
> such as gcc/binutils/gdb/libc, we were keeping older versions a little
> bit longer to give it some time to test the newer version before
> forcing everyone to upgrade. Surely we need to continue to do this with
> gcc, where most of the 4.x.0 versions are typically broken on at least
> one architecture.

D'oh, eglibc 2.19 is broken for PowerPC SPE ABI.
So it seems we'll do two versions after all.
I'll send a revised patch shortly.
Regards.

  reply	other threads:[~2014-04-08 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 13:04 [Buildroot] [PATCH] eglibc: bump to version 2.19 SVN R25243 Gustavo Zacarias
2014-04-07 13:29 ` Thomas Petazzoni
2014-04-07 13:36   ` Gustavo Zacarias
2014-04-07 13:41     ` Thomas Petazzoni
2014-04-08 11:52       ` Gustavo Zacarias [this message]
2014-04-08 12:19         ` Peter Korsgaard

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=5343E30C.1090703@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.