From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2016-05-31
Date: Wed, 1 Jun 2016 09:54:04 +0000 [thread overview]
Message-ID: <1464774805.3171.37.camel@synopsys.com> (raw)
In-Reply-To: <20160601101953.54e9e80d@free-electrons.com>
Hi Thomas,
On Wed, 2016-06-01 at 10:19 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 1 Jun 2016 08:17:21 +0000, Alexey Brodkin wrote:
>
> >
> > >
> > > ?????????arc |??????????????????jack2-v1.9.10 | NOK |
> > > http://autobuild.buildroot.net/results/c05e4a5280f34b2a1dff8a10adfd46f53344e13a/??
> > So this one is almost fixed by Bernd but given he has no time for the real fix
> > we'll take a look at proposed solution and hopefully will cook up a patch ourselves.
> Aah, good. I proposed a fix in a reply to Bernd, I believe it should
> work, it just needs to be tested a little bit on platforms where NGREG
> is really defined.
Hm I see that NGREG is defined in Linux kernel in "include/uapi/linux/elfcore.h" as:
----------------->8----------------
#ifndef __KERNEL__
...
#define NGREG ELF_NGREG
#endif
----------------->8----------------
Then in its turn ELF_NGREG is defined for ARC in "arch/arc/include/uapi/asm/elf.h" as:
----------------->8----------------
#define ELF_NGREG (sizeof(struct user_regs_struct) / sizeof(elf_greg_t))
----------------->8----------------
And since kernel's UAPI is meant to be exported to user-space I would expect NGREG to
be available for ARC and all other users of UAPI.
So might be a better solution would be to just include "elfcore.h" in jack's "dbus/sigsegv.c"?
I'll give it a try locally and if that works I'll send a patch upstream.
-Alexey
next prev parent reply other threads:[~2016-06-01 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160601063019.5D553101D2D@stock.ovh.net>
2016-06-01 8:17 ` [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2016-05-31 Alexey Brodkin
2016-06-01 8:19 ` Thomas Petazzoni
2016-06-01 9:54 ` Alexey Brodkin [this message]
2016-06-01 11:40 ` Alexey Brodkin
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=1464774805.3171.37.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox