Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-05
Date: Mon, 6 Oct 2014 21:44:08 +0200	[thread overview]
Message-ID: <20141006214408.2af48bbb@free-electrons.com> (raw)
In-Reply-To: <CANQCQpYH7XGPbR_p2-wZqrhLMu_-GyR0HBqiwEEtgK9GX60QVg@mail.gmail.com>

Dear Matthew Weber,

On Mon, 6 Oct 2014 14:22:29 -0500, Matthew Weber wrote:

> I've got the fixes captured and hope to have something tomorrow after
> testing.  I also noticed in the build results from the day before,
> protobuf 2.6 has some failures with a specific powerpc toolchain
> (looks like atomics). I should also have fixes for that in the next
> series.

Great, thanks!

Regarding the PowerPC result at
http://autobuild.buildroot.org/results/d45/d459457d0046cf96b56c5fc0660eca326d90401d/build-end.log,
it looks weird, because the code is:

#elif defined(__ppc__)
#define GOOGLE_PROTOBUF_ARCH_PPC 1
#define GOOGLE_PROTOBUF_ARCH_32_BIT 1
#elif defined(__GNUC__) && \
 (((__GNUC__ == 4) && (__GNUC_MINOR__ >= 7)) || (__GNUC__ > 4))
// We fallback to the generic GCC >= 4.7 implementation in atomicops.h
# if __LP64__
#  define GOOGLE_PROTOBUF_ARCH_64_BIT 1
# else
#  define GOOGLE_PROTOBUF_ARCH_32_BIT 1
# endif
#else
#error Host architecture was not detected as supported by protobuf
#endif

Since the failure is on PowerPC, __ppc__ should be defined, and we
shouldn't have the #error.

Maybe Gustavo, you know if __ppc__ is not defined on certain PPC platforms?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-06 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-05 Thomas Petazzoni
2014-10-06  7:15 ` Yegor Yefremov
2014-10-06  7:43 ` Thomas Petazzoni
2014-10-06 18:03   ` Alexey Brodkin
2014-10-06 18:13   ` Gustavo Zacarias
2014-10-06 19:14   ` Bernd Kuhls
2014-10-06 19:22   ` Matthew Weber
2014-10-06 19:44     ` Thomas Petazzoni [this message]
2014-10-06 19:47       ` Matthew Weber
2014-10-06 20:11         ` Alexey Brodkin
2014-10-06 20:20           ` Matthew Weber
2014-10-06 20:28             ` Alexey Brodkin
2014-10-06 20:41               ` Matthew Weber
2014-10-08  1:06                 ` Matthew Weber

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=20141006214408.2af48bbb@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