Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h
Date: Thu, 9 Jan 2014 09:46:13 +0000	[thread overview]
Message-ID: <52CE6FE5.9070305@imgtec.com> (raw)
In-Reply-To: <20140109104043.02d07109@skate>

On 01/09/2014 02:40 AM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Wed, 8 Jan 2014 17:32:43 +0000, Vicente Olivert Riera wrote:
>> Applying an upstream patch to add a missing function member on ia64,
>> mips and sparc arches.
>>
>> Upstream patch URL:
>>     http://git.uclibc.org/uClibc/commit/libc/sysdeps/linux?id=b4e6e61e2f7c6fb4bf59f66efaa74591a2112912
>>
>> Fixes:
>>     http://autobuild.buildroot.net/results/fa0/fa03ecc087a4b30df8b0366bb238be3d167a56d9/
>>
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> Siggh. This is again the kind of things that will make package builds
> work with internal uClibc toolchain, but fail badly with external
> uClibc toolchains, which are likely to not contain the gazillions of
> backported uClibc patches that we carry around.
>
> I have the feeling that this is a growing problem, and I'm not sure how
> to handle it. To me, the fact that the uClibc community is completely
> inactive in terms of releases is really a major issue.
>
> A solution would be to not support any uClibc based external toolchain,
> but that means we would no longer support Blackfin external toolchains
> for example, which is really not desirable.
>
> Best regards,
>
> Thomas
>

Yes, I understand what you mean, but what do you want to do? I mean, if 
uClibc don't release new version, aren't you going to upgrade external 
toolchains anymore?

I think we should fix this for the Buildroot toolchain, because is "our" 
toolchain and is "our" problem. If external toolchains don't apply those 
patches, then that will be their problem. They can upgrade the toolchain 
packaging uClibc to a git version number, so no releases is needed. Of 
course I understand that having a release is better because that means 
that the state is consistent, it shouldn't fail, has been tested, etc., 
but if that's not happening, again, is not our problem.

Best regards,

-- 
Vincent

  reply	other threads:[~2014-01-09  9:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 17:32 [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h Vicente Olivert Riera
2014-01-08 17:32 ` [Buildroot] [PATCH 2/2] uclibc: Make __SIGEV_PAD_SIZE to take __WORDSIZE into account Vicente Olivert Riera
2014-10-12  7:46   ` Peter Korsgaard
2014-01-09  2:40 ` [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h Thomas Petazzoni
2014-01-09  9:46   ` Vicente Olivert Riera [this message]
2014-01-10  7:36     ` Thomas Petazzoni
2014-01-10 10:10       ` Vicente Olivert Riera
2014-01-28 21:25         ` Thomas Petazzoni
2014-10-11 15:16 ` [Buildroot] [PATCH] rt-tests: enable on MIPS uClibc again Arnout Vandecappelle
2014-10-12  7:47   ` Peter Korsgaard
2014-10-12  7:46 ` [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h 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=52CE6FE5.9070305@imgtec.com \
    --to=vincent.riera@imgtec.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