The short answer is no. We've been using 2.4.1 for at least two years with
no issues, even if we came up with an upgrade path we would still need a
working 2.4.1 to transition successfully. What I don't understand is what
could possibly have changed in the archive on pypi since we used to be able
to compile it just fine. Unless we had some local version of it cached, but
then I don't know where we would have gotten it from since the version on
googlecode doesn't compile.
On Fri, Jul 8, 2016 at 11:53 AM, Feng Xiao <xiaof...@google.com> wrote:
> On Tue, Jul 5, 2016 at 2:47 PM, joyce wu <joyce.t...@gmail.com> wrote:
>> There are actually two problems:
>> 1) The source of protoc on pypi here:
>> is missing a lot of the files that are found here:
>> 2) I get a compile error when trying to build the source from the second
>> Editing src/google/protobuf/message.cc and add #include <istream>
>> before the other #includes fixed the compile error
>> Can someone fix these things?
> Can you try some newer releases? We won't be able to change already
> released versions like protobuf-2.4.1.
>> 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...@googlegroups.com.
>> To post to this group, send email to email@example.com.
>> Visit this group at https://groups.google.com/group/protobuf.
>> For more options, visit https://groups.google.com/d/optout.
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 post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.