All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] Analysis of autobuild failures 18-19/11
Date: Mon, 21 Nov 2016 14:51:46 +0000	[thread overview]
Message-ID: <1479739849.4199.68.camel@synopsys.com> (raw)
In-Reply-To: <40bbe29b-2601-f710-970c-065f0b2c639f@mind.be>

Hi Arnout, all,

On Sat, 2016-11-19 at 20:23 +0100, Arnout Vandecappelle wrote:
> ?Hi all,
>?
> http://autobuild.buildroot.net/results/f2a001031af381388cff71b4de1103fc11e08239
> xtensa	jack2-v1.9.10	uclibc	
> 
> > 
> > ../dbus/sigsegv.c: In function 'signal_segv':
> > ../dbus/sigsegv.c:110:20: error: 'NGREG' undeclared (first use in this function)
> > ?????for(i = 0; i < NGREG; i++)
> > ????????????????????^
> > ../dbus/sigsegv.c:110:20: note: each undeclared identifier is reported only once for each function it appears in
> > ../dbus/sigsegv.c:119:38: error: 'mcontext_t {aka struct sigcontext}' has no member named 'gregs'
> > ?????????????????ucontext->uc_mcontext.gregs[i]
> 
> ?Lots of similar failures exist with uClibc, but only on xtensa and arc.
> Incomplete / incompatible struct sigcontext definition maybe? Waldemar?


That's a long-standing problem we discussed in quite a detail some time ago, see
http://lists.busybox.net/pipermail/buildroot/2016-May/161785.html?and
http://lists.busybox.net/pipermail/buildroot/2016-June/162461.html

I've just sent a patch with Thomas' solution to the problem at hand,
pls find it here -?http://patchwork.ozlabs.org/patch/697273/

-Alexey?

  parent reply	other threads:[~2016-11-21 14:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 19:23 [Buildroot] Analysis of autobuild failures 18-19/11 Arnout Vandecappelle
2016-11-19 20:55 ` Romain Naour
2016-11-20 15:24 ` Arnout Vandecappelle
2016-11-20 23:18 ` Sam Bobroff
2016-11-24 20:48   ` Arnout Vandecappelle
2016-11-25  0:51     ` Sam Bobroff
2016-11-21 11:21 ` Waldemar Brodkorb
2016-11-21 23:40   ` Arnout Vandecappelle
2016-11-23 11:37     ` Waldemar Brodkorb
2016-11-23 12:06       ` Arnout Vandecappelle
2016-11-25  0:26         ` Waldemar Brodkorb
2016-11-21 11:44 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2016-11-21 14:51 ` Alexey Brodkin [this message]
2016-11-21 22:08 ` [Buildroot] " Thomas Petazzoni
2016-11-21 23:38   ` Arnout Vandecappelle
2016-11-22  8:26     ` Thomas Petazzoni
2016-11-22 15:30       ` Arnout Vandecappelle
2016-11-22 15:38         ` Thomas Petazzoni
     [not found]           ` <CANLo3Ji8MiH29tYCwmpu4KMDJkcm7-75EUGK1mq3e8Tnih6aZQ@mail.gmail.com>
2016-11-22 19:08             ` Romain Naour

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=1479739849.4199.68.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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.