From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-08-05
Date: Mon, 10 Aug 2015 13:36:56 +0200 [thread overview]
Message-ID: <20150810133656.53b015a1@free-electrons.com> (raw)
In-Reply-To: <1439205989.4848.16.camel@synopsys.com>
Dear Alexey Brodkin,
On Mon, 10 Aug 2015 11:26:29 +0000, Alexey Brodkin wrote:
> On Thu, 2015-08-06 at 11:30 +0200, Thomas Petazzoni wrote:
> > Hello all,
> > arc | gnuradio-3.7.5 | NOK |
> > > http://autobuild.buildroot.net/results/d44aec8c82ed6a315322726dd698e6b48990ba76/
> >
> > ARC toolchain problem:
> >
> > error: '__NR_eventfd' was not declared in this scope
> >
> > Alexey, I don't remember, do you have a fix for this one?
>
> I already commented on that one.
> Basically gnuradio includes source from boost and in boost itself they
> use syscall directly if (__GLIBC__ == 2 && __GLIBC_MINOR__ < 8) which
> is the case for uClibc, see http://git.uclibc.org/uClibc/tree/include/features.h#n395
> -------------->8--------------
> #define __GLIBC__ 2
> #define __GLIBC_MINOR__ 2
> -------------->8--------------
>
> From Boost standpoint this looks like some sort of backward compatibility for older
> glibc that didn;'t have eventfd() defined.
>
> So probably the best option here is to bump __GLIBC__/__GLIBC_MINOR__ in uClibc.
> Maybe Waldemar may comment on that?
Can't we instead patch boost to use a || defined(__UCLIBC__) or
something like that?
> > > arc | libselinux-2.1.13 | NOK |
> > > http://autobuild.buildroot.net/results/2fdea2bbcdff4a70ffaac1eecbc8faa81a44e90c/
> >
> > ARC toolchain problem:
> >
> > Error: internal error: fixup not contained within frag
> >
> > Alexey?
>
> On my to investigate list.
Thanks!
> Libsodium attempts to build as PIE.
> Should be fixed by http://patchwork.ozlabs.org/patch/505568/
Seen the patch, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-10 11:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-05 Thomas Petazzoni
2015-08-06 9:30 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-08-06 9:30 ` Vicente Olivert Riera
2015-08-17 10:02 ` Vicente Olivert Riera
2015-08-06 9:36 ` Vicente Olivert Riera
2015-08-17 10:00 ` Vicente Olivert Riera
2015-08-06 10:08 ` Julien CORJON
2015-08-06 11:57 ` Brendan Heading
2015-08-06 16:31 ` Bernd Kuhls
2015-08-07 4:07 ` Waldemar Brodkorb
2015-08-07 8:58 ` Thomas Petazzoni
2015-08-07 12:11 ` Max Filippov
2015-08-07 12:13 ` Thomas Petazzoni
2015-08-10 11:26 ` Alexey Brodkin
2015-08-10 11:36 ` Thomas Petazzoni [this message]
2015-08-10 11:54 ` Alexey Brodkin
2015-08-10 18:08 ` Waldemar Brodkorb
2015-08-10 18:49 ` Alexey Brodkin
2015-08-13 16:32 ` Alexey Brodkin
2015-08-14 21:48 ` Waldemar Brodkorb
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=20150810133656.53b015a1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.