From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package: protobuf/python-protobuf: bump to v3.2.0.
Date: Thu, 20 Apr 2017 22:25:37 +0200 [thread overview]
Message-ID: <20170420222537.4226afcc@free-electrons.com> (raw)
In-Reply-To: <20170420140614.25998-1-mrugiero@gmail.com>
Hello,
On Thu, 20 Apr 2017 11:06:14 -0300, mrugiero at gmail.com wrote:
> From: "Mario J. Rugiero" <mrugiero@gmail.com>
>
> Both packages are coupled, so both were bumped and build-tested.
> The atomics' support patch is no longer needed, and neither is
> the autoreconf option, and SPARC64 is no longer broken.
> To make sure of this, one config of each of the following archs
> was tested (base defconfig in parens):
> PowerPC (qemu_ppc_g3beige_defconfig)
> SPARC (qemu_sparc_ss10_defconfig)
> SPARC64 (qemu_sparc64_sun4u_defconfig)
Thanks for this patch. Overall it looks good, but I have one
question/comment.
> -# On PowerPC, the __atomic_*() built-ins for 1-byte, 2-byte and 4-byte
> -# types are available built-in. However, the __atomic_*() built-ins for
> -# 8-byte types is implemented via libatomic, so only available since gcc
> -# 4.8.
> -#
> -# In Buildroot, to simplify things, we've decided to simply require gcc
> -# 4.8 as soon as the architectures has at least one __atomic_*() built-in
> -# variant that requires libatomic.
> -#
> -# Since protobuf most likely only uses the 1, 2 and 4-byte variants, it
> -# *could* technically build with gcc 4.7. This is probably not a big deal,
> -# and we can live with requiring gcc 4.8 on PowerPC to build protobuf.
What makes you think all of the above is no longer relevant?
There is still a "default y if BR2_TOOLCHAIN_HAS_ATOMIC", which allows
to build protobuf on all architectures that provide the __atomic_*()
built-ins.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-20 20:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 17:22 [Buildroot] [PATCH 1/2] package: protobuf: bump to v3.2.0 mrugiero at gmail.com
2017-04-17 17:22 ` [Buildroot] [PATCH 2/2] new package: grpc mrugiero at gmail.com
2017-04-18 18:26 ` Arnout Vandecappelle
[not found] ` <CAKKQwLQOR_PXG-yLLCn5UxY5dX1wQCs3VNxpkWk_NLSBuY_KCA@mail.gmail.com>
2017-04-19 2:24 ` [Buildroot] Fwd: " Mario Rugiero
2017-04-18 12:08 ` [Buildroot] [PATCH 1/2] package: protobuf: bump to v3.2.0 Arnout Vandecappelle
2017-04-18 12:36 ` Mario Rugiero
2017-04-20 4:41 ` Mario Rugiero
2017-04-20 11:14 ` Arnout Vandecappelle
2017-04-20 14:06 ` [Buildroot] [PATCH v2] package: protobuf/python-protobuf: " mrugiero at gmail.com
2017-04-20 20:25 ` Thomas Petazzoni [this message]
2017-04-21 16:06 ` [Buildroot] [PATCH v3] " mrugiero at gmail.com
2017-04-22 13:32 ` Thomas Petazzoni
2017-04-23 11:59 ` Yann E. MORIN
2017-04-23 13:51 ` Rahul Bedarkar
2017-04-24 11:48 ` Mario Rugiero
2017-04-24 14:03 ` Mario Rugiero
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=20170420222537.4226afcc@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