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] [autobuild.buildroot.net] Build results for 2013-12-03
Date: Wed, 4 Dec 2013 16:39:30 +0000	[thread overview]
Message-ID: <529F5AC2.1020700@imgtec.com> (raw)
In-Reply-To: <20131204133500.2f99e067@skate>

On 12/04/2013 12:35 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Wed, 4 Dec 2013 10:58:21 +0000, Vicente Olivert Riera wrote:
>
>>>       mipsel |                  rt-tests-0.83 | NOK | http://autobuild.buildroot.net/results/35406e2aa9210f436c750b889a79c65fd8f5ded1/
>>
>> This is a problem with certain arches (IA64, MIPS and SPARC) in uClibc.
>> The file "uClibc/libc/sysdeps/linux/${ARCH}/bits/siginfo.h" has a struct
>> called sigevent. That struct has "__pid_t _tid;" in some arches, but not
>> on IA64, MIPS and SPARC, that's why it fails. glibc, for instance, has
>> that member on all arches.
>
> What can we do to fix this?
Just add the missing lines to the siginfo.h of the affected arches.

> Is there a fix upstream in uClibc?
I have seen the uClibc git repository today and the siginfo.h files for 
the affected arches haven't been modified yet. However, they have made 
some changes on the other arches and now those arches don't have a 
siginfo.h file, so I guess uClibc upstream will do the same for the 
affected arches sooner or later.

> Should we report the problem to them?
I think that will not hurt anyone :-)

> Thomas
>


-- 
Vincent

  reply	other threads:[~2013-12-04 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-03 Thomas Petazzoni
2013-12-04 10:58 ` Vicente Olivert Riera
2013-12-04 12:35   ` Thomas Petazzoni
2013-12-04 16:39     ` Vicente Olivert Riera [this message]
2013-12-05 15:59 ` Thomas De Schampheleire
2013-12-05 16:07   ` Thomas Petazzoni
2013-12-05 22:05     ` 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=529F5AC2.1020700@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