[protobuf] protobuf build failures on certain compilers and architectures

This looks to be a genuine bug in the original generic atomicops implementation. These warnings appear to currently be harmless, since the affected functions do not appear to be used anywhere in protobuf or protobuf generated code. Thanks! -- Robert Edmonds -- You received this message

Re: [protobuf] Re: How to check empty message object

Thu Jan 1 00:00:00 UTC 1970, in this case). I don't see how default values enters into it. > and these "hazzers" logics have to go away. Google says, "we will continue to support proto2 for a long time." -- Robert Edmonds -- You received this message because you a

Re: [protobuf] Proto3 conversion growing pains: missing optional / has_foo() functionality.

s about proto3 support, but no one has actually volunteered to write any code for that yet, and I suspect if we ever do implement proto3 support we'll probably fork a separate 'protobuf3-c' project with separate SONAMEs, command-line utilities, etc. and leave the folks happy with prot

Re: [protobuf] Add link to rust protobuf implementation

f-c project? I opened https://code.google.com/p/protobuf/issues/detail?id=628 a while back... -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, s

Re: [protobuf] Port to PPC64 architecture

s. It would be much appreciated if the protobuf developers implemented a fall back using the standardized atomics support available in newer versions of gcc/clang. -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group

Re: [protobuf] 2.6.0 release candidate

maintainers, because we have to patch protobuf to make it compile on architectures beyond the limited set of architectures that are explicitly supported in src/google/protobuf/stubs/platform_macros.h. -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups

Re: [protobuf] 2.6.0 release candidate

Robert Edmonds wrote: > Hello, > > I'm disappointed at the lack of resolution to issue #488: > > https://code.google.com/p/protobuf/issues/detail?id=488 > > This puts a big burden on the Debian and Red Hat protobuf package > maintainers, because we have to patc

Re: [protobuf] 2.6.0 release candidate

uitable as-is for inclusion in the protobuf mainline. -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@g

Re: [protobuf] 2.6.0 release candidate

also attached a plain copy of the patch exported from my git repository. -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protob

Re: [protobuf] Re: protobuf-c zero allocation

on of protobuf. I'm wondering if there is a way to > > not allocate memory dynamically to serialize/deserialize a message. In > > other words, is there a "ZERO ALLOCATION" method to use it ? > > > > Best regards, > > > > Julien. -- Robert Edmonds

Re: [protobuf] How to install protobuf 2.6 for python 3?

on3.4/dist-packages/setuptools/sandbox.py", > > line 114, in run > > return func() > > File "/usr/local/lib/python3.4/dist-packages/setuptools/sandbox.py", > > line 67, in runner > > _execfile(setup_script, ns) > > File "/usr/local/lib/python

[protobuf] release tarballs on GitHub?

ls stuff) by clicking the "Edit" button next to the release as a project administrator. That's what I do for the protobuf-c releases: https://github.com/protobuf-c/protobuf-c/releases (The green buttons are the real tarballs, the grey buttons are the repository snapshots syn

Re: [protobuf] release tarballs on GitHub?

for these > tarballs? I think this information is only available from the API. https://help.github.com/articles/getting-the-download-count-for-your-releases -- Robert Edmonds -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" gro

Re: [protobuf] PIP install broken on 2.6.0 (out of date python-dateutil 1.5 dependency)

pypi/python-dateutil) > > > > The workaround is to downgrade to 1.5 (pip install -U python-dateutil==1.5) > > > > But this wasn't necessary for 2.5.0 > > > I don't think we have changed this in 2.6.0. Maybe it's due to a change of > the dateutil