From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: remove version choice
Date: Thu, 8 Jun 2017 21:44:52 +0200 [thread overview]
Message-ID: <20170608194451.GT26922@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170607212720.GA23160@scaer>
Hi Yann,
Yann E. MORIN wrote,
> Waldemar, Thomas, All,
>
> On 2017-06-06 21:35 +0200, Thomas Petazzoni spake thusly:
> > On Tue, 6 Jun 2017 19:56:59 +0200, Waldemar Brodkorb wrote:
> > > We do not support uClibc-ng/musl C library version choice support,
> > > do the same for GNU C Library.
> > > Add me as Maintainer for the package.
> > >
> > > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> >
> > On this one, I'd like to have the opinion of others. Arnout? Peter?
> > Yann? What do you think about this?
> >
> > I don't have a very clear-cut opinion about this one.
>
> Neither do I.
>
> On principle, I agree that we should drop versions. But glibc is part of
> the toolchain, and the toolchain has always been special.
It is special, but if we can reduce the whole sum of combinations,
isn't that good? In case of C library, it seems to me that the
lastest version is always the best one. There are fewer regressions
then with changing binutils or gcc default.
> True, we do not have a version for uClibc-ng, but we do have some
> traction on the maintainer! ;-) So we know things are gonna be fixed
> soonish, or that we can grab a temporary backport, both very easily.
>
> Not so much for glibc in my experience...
>
> musl is another kind of thing, because it is (was?) moving relatively
> fast, and I am under the impression that the maintainers are somewhat
> amenable to some fixes.
>
> Not so much for glibc in my experience...
I am reading both mailinglists so at least I sometimes fishing
interesting bugfixes, as for the sh4 issue.
If Thomas don't mind I would take musl also over. (DEVELOPERS file)
best regards
Waldemar
next prev parent reply other threads:[~2017-06-08 19:44 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 [this message]
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
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=20170608194451.GT26922@waldemar-brodkorb.de \
--to=wbx@openadk.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 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.