All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-08-05
Date: Mon, 10 Aug 2015 11:54:52 +0000	[thread overview]
Message-ID: <1439207692.4848.27.camel@synopsys.com> (raw)
In-Reply-To: <20150810133656.53b015a1@free-electrons.com>

Hi Thomas,

On Mon, 2015-08-10 at 13:36 +0200, Thomas Petazzoni wrote:
> 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?

Well we may try but grep for __GLIBC_MINOR__ returns at least 10 files with matches.
That's why I'd prefer to just reuse existing code with __GLIBC__/__GLIBC_MINOR__.

If we may just say that  we're on par with say __GLIBC__=2 __GLIBC_MINOR__=10 that
will cure a problem with Boost.

Let's get Waldemar's opinion on that and if he says __UCLIBC__ is the way to go we'll
figure out who's going to create that patch :)

See I sent 2 emails to Boost mailing list:
http://lists.boost.org/Archives/boost/2015/07/224257.php
http://lists.boost.org/Archives/boost/2015/07/224404.php
and haven't heard back.

So it might take a while until these guys accept our patch if at all.

-Alexey

  reply	other threads:[~2015-08-10 11:54 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
2015-08-10 11:54       ` Alexey Brodkin [this message]
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=1439207692.4848.27.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.