From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] uclibc: add upstream 0.9.33 fixes
Date: Fri, 6 Sep 2013 16:35:51 +0200 [thread overview]
Message-ID: <20130906163551.571faf5c@skate> (raw)
In-Reply-To: <20130906133535.2BD969A98A@busybox.osuosl.org>
Dear Peter Korsgaard,
On Fri, 6 Sep 2013 15:28:51 +0200, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=055f1c02d35068d0b089f3b29ffdd4fb2717bb5c
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> Upstream has a large number of patches lined up for the next 0.9.33.x bugfix
> release;
>
> http://git.uclibc.org/uClibc/log/?h=0.9.33
>
> Add them here, as atleast some of them are quite critical (E.G. the eventfd
> issue gets triggered by recent glib versions).
>
> I've skipped the microblaze and xtensa fixes as we don't currently support
> those with 0.9.33.2.
>
> Drop uclibc-0002-Add-definition-of-MSG_WAITFORONE-and-MSG_CMSG_CMSG_CLOEXE.patch
> as that is a subset of uclibc-0035-socket.h-pull-socket_type.h-from-eglibc.patch
Shouldn't we switch to using the git version of uClibc instead of
carrying 40+ patches? The uClibc project seems to have issues getting
releases out, maybe we should just use their git version, and bump it
from time to time when appropriate?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-06 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 13:28 [Buildroot] [git commit] uclibc: add upstream 0.9.33 fixes Peter Korsgaard
2013-09-06 14:35 ` Thomas Petazzoni [this message]
2013-09-06 20:53 ` Peter Korsgaard
2013-09-09 16:26 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2012-02-16 11:20 [Buildroot] [git commit] uClibc: " 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=20130906163551.571faf5c@skate \
--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