From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-11-23
Date: Fri, 25 Nov 2016 10:47:34 +0000 [thread overview]
Message-ID: <1480070793.3217.9.camel@synopsys.com> (raw)
In-Reply-To: <20161124094429.4152c19b@free-electrons.com>
Hi Thomas, all
On Thu, 2016-11-24 at 09:44 +0100, Thomas Petazzoni wrote:
> Hello,
>
> Christian, Waldemar, Sam, Bernd, Alexey, Vlad, Vicente, J?rg, Fran?ois,
> please see below, there are some questions for you.
>
> Summary of the build failures:
>
> ?- musl related: 8
> ?- misc: 7
> ?- static linking: 4
> ?- PowerPC64le libtool: 2
> ?- ARC related: 2
> ?- uClibc-ng related: 1
> ?- unknown: 1
> >
> > ?????????arc |??????????????????????gpsd-3.16 | NOK | http://autobuild.buildroot.net/results/e8593a8ebf2f05cc93235a8
> > 129a2ba8b839d6d90
> > ?????????arc |??????????????????????gpsd-3.16 | NOK | http://autobuild.buildroot.net/results/ff766f4f514c9cb48918731
> > 67f4e9b7870051883
>
> error: 'memory_order_seq_cst' was not declared in this scope
>
> Alexey, Vlad, could you have a look?
This is upstream problem with gcc 6.x being discussed in this thread:
http://lists.nongnu.org/archive/html/gpsd-dev/2016-09/msg00082.html
That said on my Fedora 24 I'm easily seeing the same problem trying to build gpsd.
The only work-around for gcc 6.x now is adding "-std=gnu++98" to both CFLAGS and CXXFLAGS.
I'll try to come up with something for BR in the meantime.
-Alexey
prev parent reply other threads:[~2016-11-25 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-23 Thomas Petazzoni
2016-11-24 8:44 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-11-24 15:26 ` Waldemar Brodkorb
2016-11-24 19:24 ` Jörg Krause
2016-11-24 19:58 ` Christian Stewart
2016-11-24 22:12 ` Jörg Krause
2016-11-25 0:22 ` Sam Bobroff
2016-11-25 8:09 ` Thomas Petazzoni
2016-11-25 10:47 ` Alexey Brodkin [this message]
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=1480070793.3217.9.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