buildroot/package/protobuf, branch 2016.05

protobuf: fix detection of __atomic_*() built-ins

2016-03-20T22:43:31+00:00

- Use the recently introduced BR2_TOOLCHAIN_HAS_ATOMIC boolean. - Import an upstream patch to fix error handling when atomic operations are not detected. Without this patch the build fails due to a syntax error instead of showing the proper message. - Add a patch to configure.ac to check if libatomic is needed and force linking to it (we will attempt to submit this upstream). - Disable build for SPARC64 because it fails due to a missing definition of Atomic64. On PowerPC, the __atomic_*() built-ins for 1-byte, 2-byte and 4-byte types are available built-in. The corresponding built-ins for 8-byte types, however, are implemented via libatomic, so requiring gcc >= 4.8. In Buildroot, to simplify things, it was decided to 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. The same restriction applies to SPARC. The build for SPARC64 breaks even using the master branch of protobuf due to undefined references to some NoBarrier_Atomic*() functions. Signed-off-by: Henrique Marks Signed-off-by: Carlos Santos Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

protobuf: introduce BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS

2016-02-04T22:04:13+00:00

The architecture dependencies of protobuf are going to change, and they are already duplicated between protobuf, ola and mosh. In order to factorize the expression of those dependencies, this commit introduces BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS. Note that we include in this hidden Config.in option both the target architecture dependency and the host architecture dependency. Finally, this commit also fixes a real mistake in the mosh Config.in file, where the condition on the architecture dependency for the Config.in comment was inverted: we only want to show the Config.in comment when we are on supported architectures. Signed-off-by: Thomas Petazzoni

protobuf: fix legal-info

2015-11-04T21:24:17+00:00

The file changed from COPYING.txt to LICENSE, fixes: http://autobuild.buildroot.net/results/c40/c40e9b6030584a4fd8b3e46f78f6d0702d1dc11e/ Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

protobuf: bump to 2.6.1

2015-11-04T17:38:26+00:00

Signed-off-by: Steven Noonan Signed-off-by: Thomas Petazzoni

package/protobuf: needs dynamic libraries

2015-08-18T19:41:12+00:00

Eventhough it should be theoretically possible to build protobuf in static-only, configure.ac includes an m4 macro, ACX_PTHREAD defined in m4/acx_pthread.m4, which forcibly checks for threads *with* shared libs, and is completely broken for static-only (as it forces -shared whatever the user selection), ending up with these configure results: checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking whether to check for GCC pthread/shared inconsistencies... yes checking whether -pthread is sufficient with -shared... no checking whether -lpthread fixes that... no checking whether -lc_r fixes that... no configure: WARNING: Impossible to determine how to use pthreads with shared libraries checking whether what we have so far is sufficient with -nostdlib... no checking whether -lpthread saves the day... no configure: WARNING: Impossible to determine how to use pthreads with shared libraries and -nostdlib Fixing this macro is far from trivial; protobuf in a static-only scenario is probably not too common. So, just disable protobuf for static-only builds. Fixes: http://autobuild.buildroot.org/results/3ef/3efb86c7e8ec2db5d953d634470cafae79bd34cf/ http://autobuild.buildroot.org/results/96a/96ae1108fc3193df2a93a779057130b774379655/ http://autobuild.buildroot.org/results/00c/00c29795980319d38823eec1301e9ebd860ebd2a/ ... Signed-off-by: "Yann E. MORIN" Cc: Nimai Mahajan Signed-off-by: Thomas Petazzoni

package/protobuf: autoreconf is now needed

2015-05-22T05:30:54+00:00

Since its update, the *_SITE points to the git repository, so configure script is not generated in this tarball. Fixes: http://autobuild.buildroot.org/results/ccb/ccba6d8c73b5e826b86065b77b3fe5077db7b99c/ http://autobuild.buildroot.org/results/57e/57ea34e9b48293075e10f0dd2331de2785730827/ and many more... [Peter: drop redundant HOST_*_AUTORECONF] Signed-off-by: Samuel Martin Signed-off-by: Peter Korsgaard

package/protobuf: Update site url

2015-05-21T21:22:52+00:00

Package moved to github: https://developers.google.com/protocol-buffers/docs/downloads "Our old Google Code repositiory is: https://code.google.com/p/protobuf/. We moved to github on Aug 26, 2014 [...]" Signed-off-by: Bernd Kuhls Signed-off-by: Peter Korsgaard

Revert "protobuf: bump version to 2.6.0"

2014-10-06T07:22:54+00:00

This reverts commit 7b6304af9d69d44ee3040c00b0670f19c02de7d2, since it causing too many build failures, with python-protobuf and host-protobuf-c. Signed-off-by: Thomas Petazzoni

packages: rename FOO_CONF_OPT into FOO_CONF_OPTS

2014-10-04T16:54:16+00:00

To be consistent with the recent change of FOO_MAKE_OPT into FOO_MAKE_OPTS, make the same change for FOO_CONF_OPT. Sed command used: find * -type f | xargs sed -i 's#_CONF_OPT\>#&S#g' Signed-off-by: Thomas De Schampheleire Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

protobuf: bump version to 2.6.0

2014-10-02T20:54:37+00:00

* Adds powerpc architecture support * Changes to the new github upstream site * Updates the license filename Signed-off-by: Matt Weber Signed-off-by: Peter Korsgaard