[protobuf] Re: Issue 295 in protobuf: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found
Comment #4 on issue 295 by mageb...@gmail.com: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found http://code.google.com/p/protobuf/issues/detail?id=295 Hi, I have the same problem. I can add that the problem concerns protobuf-2.4.1 and protobuf-2.4.0. In case of protobuf-2.3.0 everything builds well. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 295 in protobuf: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found
Comment #5 on issue 295 by liuj...@google.com: C++ Compilation of 2.4.1 fails GLIBCXX_3.4.11 Not found http://code.google.com/p/protobuf/issues/detail?id=295 From the previous logs, it looks like protoc was linked successfully. However, when the build script started the protoc to generate files, protoc complained that the libstdc++ version mismatched and failed to start. From gglentini's command, those GLIBCXX_3.4.10 are defined in the gcc-4.x, but not gcc-3.4. My guess is that protoc was linked to gcc-4.x successfully. However, in the runtime, gcc 3.4-stdc++ took precedence. Maybe you could try one of those: 1) Check ldconfig and let the gcc 4 take precedence. 2) Configure to let protobuf link against gcc 3 3) Make protoc link static. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
Re: [protobuf] Error: Byte size calculation and serialization were inconsistent
On Feb 6, 2012, at 21:54 , Robby Zinchak wrote: It turned out to be an uninitialized boolean. Properly setting the value in question seems to allow things to proceed normally. Ah! Interesting. So one of your .set_* properties is a boolean, and one of them was uninitialized? That would do it. This was discussed previously and dismissed as a wont fix problem, because it is hard/impossible to make portable code that will test for this: http://code.google.com/p/protobuf/issues/detail?id=234 Although its somewhat confusing since WireFormatLite::WriteBoolNoTag contains code to try to avoid this problem, which GCC helpfully optimizes away. I am not able to get the exact crash as the one you reported, but I can get it to crash in MessageLite::SerializeWithCachedSizesToArray by creating a boolean with a value of 0x80 (serializing to two bytes instead of one, causing it to create a message larger than it expects). I can't figure out how it could crash at the point you report the crash, but that doesn't really matter. Glad you got it working, Evan -- http://evanjones.ca/ -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 361 in protobuf: Fix warnings
Comment #1 on issue 361 by van...@gmail.com: Fix warnings http://code.google.com/p/protobuf/issues/detail?id=361 gcc also generates a lot of errors comparison between signed and unsigned integer expressions if protobuf is compiled with flags -Wall -w9 -Werror -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
[protobuf] Re: Issue 361 in protobuf: Fix warnings
Comment #2 on issue 361 by jacobgla...@yahoo.com: Fix warnings http://code.google.com/p/protobuf/issues/detail?id=361 There's also a bunch of size mismatches that I'd love to see fixed. -- You received this message because you are subscribed to the Google Groups Protocol Buffers group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
