From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-04
Date: Tue, 7 Oct 2014 09:48:32 +0200 [thread overview]
Message-ID: <20141007094832.01c0f443@free-electrons.com> (raw)
In-Reply-To: <CANQCQpYkPJATN4b8hYwCWtLpz3XhO5ZtESWb9crSChA2jYgrjQ@mail.gmail.com>
Dear Matthew Weber,
On Mon, 6 Oct 2014 14:45:07 -0500, Matthew Weber wrote:
> > powerpc | protobuf-2.6.0 | NOK | http://autobuild.buildroot.net/results/3c1c620684a23b4cbb1cfa560096094cd9bf09ec/
> > powerpc | protobuf-2.6.0 | NOK | http://autobuild.buildroot.net/results/f1b70ebabd587987547424a21eefc530317026cd/
>
> These powerpc builds use a gcc 4.5 compiler which doesn't provide the
> generic atomicops implementation which is only exposed if GCC >= 4.7.
> I looked at the BR2_ARCH_HAS_ATOMICS option as a possible dependency
> to fix this but it seems like that option is always set if the ARCH
> supports it. Not necessarily based on if a toolchain provides a
> generic.
Gaah, yes. We knew that we introducing the BR2_ARCH_HAS_ATOMICS thing,
but making it a per-compiler version thing was really too annoying.
Is there a way to build protobuf without those atomic operations, or
not at all?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-07 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-04 Thomas Petazzoni
2014-10-06 19:45 ` Matthew Weber
2014-10-07 7:48 ` Thomas Petazzoni [this message]
2014-10-07 16:30 ` Matthew Weber
2014-10-08 1:52 ` Matthew Weber
2015-03-24 23:26 ` Thomas Petazzoni
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=20141007094832.01c0f443@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox