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: remove version choice
Date: Sat, 10 Jun 2017 13:33:53 +0200	[thread overview]
Message-ID: <20170610133353.068831eb@free-electrons.com> (raw)
In-Reply-To: <d6af409f-8318-d97e-9193-cb07f94de67a@mind.be>

Hello,

On Sat, 10 Jun 2017 11:19:32 +0200, Arnout Vandecappelle wrote:

>  I think there is in fact more reason to have multiple versions for uClibc-ng
> than for glibc. Multiple versions are useful in any situation when there are ABI
> changes in the newer version so that binaries linked with the older version no
> longer work. glibc is very careful about ABI changes, uClibc-ng somewhat less so.
> 
>  So yes, I'm in favour of removing this version choice. Also for binutils, by
> the way. Yes, there may be regressions, but then those should be fixed, not
> swept under the carpet for some time until the new version becomes the default.
> 
>  GCC is different, because newer GCC versions do break compatibility with older
> libraries, and they do break existing (badly written) source code. In that sense
> I think it was a bad idea to remove GCC 4.9, because GCC 5 did break binary
> compatibility for C++... But I wasn't here at the time and that ship has sailed now.

I haven't merged https://patchwork.ozlabs.org/patch/767087/, so gcc 4.9
is still there:

$ grep 4_9_X package/gcc/Config.in.host 
config BR2_GCC_VERSION_4_9_X
	default "4.9.4"     if BR2_GCC_VERSION_4_9_X

I was waiting for feedback (such as yours) before merging this patch.

Best regards,

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

  reply	other threads:[~2017-06-10 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 17:56 [Buildroot] [PATCH] glibc: remove version choice Waldemar Brodkorb
2017-06-06 19:35 ` Thomas Petazzoni
2017-06-07 21:27   ` Yann E. MORIN
2017-06-08 19:44     ` Waldemar Brodkorb
2017-06-08 19:48       ` Thomas Petazzoni
2017-06-08 20:10     ` Peter Korsgaard
2017-06-10  9:19       ` Arnout Vandecappelle
2017-06-10 11:33         ` Thomas Petazzoni [this message]
2017-06-10 10:46 ` 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=20170610133353.068831eb@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