From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] uclibc: add patch fixing non-threaded build on Xtensa for uClibc-ng 1.0.0
Date: Sun, 8 Mar 2015 08:35:51 +0100 [thread overview]
Message-ID: <20150308083551.4e3409fa@free-electrons.com> (raw)
In-Reply-To: <20150307175651.GJ3937@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Sat, 7 Mar 2015 18:56:51 +0100, Waldemar Brodkorb wrote:
> > No, I'm still not convinced we need separate packages at this point.
> > Maybe in the future if uClibc and uClibc-ng diverge significantly, but
> > it's not the case right now.
>
> To clear things up, I am happy with the version stuff and we don't
> need an extra package. I just thought whenever we get the situation
> that uClibc 1.0.0 is released _and_ uClibc-ng is still using 1.0.x
> ;)
Ah, yes indeed. If/when this situation arises, having separate packages
would be a solution.
Again, I guess it's too early to really draw a plan about what will
happen between uClibc and uClibc-ng. It really all depends on how both
projects will be maintained: if you continue to be active on uClibc-ng
or not, if the original uClibc project moves again or not, etc. So
let's not make too much plans, and see what happens :-)
However, one plan I'd like to make is to make uClibc-ng the default
uClibc version. Maybe for 2015.05, if not for 2015.08.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-08 7:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 13:39 [Buildroot] [PATCH 0/3] uClibc-ng related fixes Thomas Petazzoni
2015-03-07 13:39 ` [Buildroot] [PATCH 1/3] uclibc: adapt thread implementation selection to uClibc-ng Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 16:41 ` Thomas Petazzoni
2015-03-07 17:20 ` Waldemar Brodkorb
2015-03-08 7:41 ` Thomas Petazzoni
2015-03-09 8:27 ` Alexey Brodkin
2015-03-09 9:46 ` Thomas Petazzoni
2015-03-07 17:39 ` Yann E. MORIN
2015-03-08 7:40 ` Thomas Petazzoni
2015-03-08 8:45 ` Yann E. MORIN
2015-03-08 9:13 ` Waldemar Brodkorb
2015-03-07 13:39 ` [Buildroot] [PATCH 2/3] uclibc: remove bogus comment about thread implementation selection Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 13:40 ` [Buildroot] [PATCH 3/3] uclibc: add patch fixing non-threaded build on Xtensa for uClibc-ng 1.0.0 Thomas Petazzoni
2015-03-07 14:40 ` Yann E. MORIN
2015-03-07 15:43 ` Waldemar Brodkorb
2015-03-07 15:50 ` Yann E. MORIN
2015-03-07 16:30 ` Thomas Petazzoni
2015-03-07 17:56 ` Waldemar Brodkorb
2015-03-08 7:35 ` Thomas Petazzoni [this message]
2015-03-07 16:29 ` Thomas Petazzoni
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=20150308083551.4e3409fa@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 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.