From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] uclibc: add upstream 0.9.33 fixes
Date: Mon, 09 Sep 2013 18:26:42 +0200 [thread overview]
Message-ID: <522DF6C2.90402@mind.be> (raw)
In-Reply-To: <87ppsl1xjy.fsf@dell.be.48ers.dk>
On 06/09/13 22:53, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> Hi,
>
> >> 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
>
> Thomas> Shouldn't we switch to using the git version of uClibc instead of
> Thomas> carrying 40+ patches? The uClibc project seems to have issues getting
> Thomas> releases out, maybe we should just use their git version, and bump it
> Thomas> from time to time when appropriate?
>
> Yes, Perhaps. When I started this, I only thought I would add 2-3
> patches to fix the eventfd issue - but looking closer, the other patches
> seemed worthwhile as well.
>
> We do carry a few patches that aren't (yet?) part of upstream git on the
> 0.9.33 branch, so it wouldn't get rid of all patches (but most). Another
> potential issue is that git almost becomes a hard buildroot dependency,
> but that's probably not a big problem.
>
> What do others say?
I don't like the idea of using an unreleased version of something as
essential as the standard library... It kind of shifts the burden of
making sure that uclibc actually works to buildroot. If we do that, we
could just as well use git versions of all packages.
But of course, carrying such a large patchset is almost the same as
using an unreleased version anyway.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-09-09 16:26 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
2013-09-06 20:53 ` Peter Korsgaard
2013-09-09 16:26 ` Arnout Vandecappelle [this message]
-- 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=522DF6C2.90402@mind.be \
--to=arnout@mind.be \
--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