Indeed, if you downloaded the zip file, then all the text files have
windows-style newlines, including the text format golden files. And it
looks like the test code isn't dealing with this correctly. I wonder why
this never came up before...
I think this can be fixed by changing TestUtil.java
Environment:
protobuf 2.2.0
$ uname -a
SunOS arson 5.10 Generic_118833-23 sun4u sparc SUNW,Sun-Fire-280R
$ g++ -v
Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs
Configured with: ../configure --with-as=/usr/ccs/bin/as
--with-ld=/usr/ccs/bin/ld --enable-shared
Kenton Varda wrote:
I'm pretty sure #1 is not protobuf's fault. I've never heard of
libgcc_s which means it's probably something GCC links against
implicitly. And anyway, if libwhatever.so.1 exists, there should always
be a libwhatever.so symlink to it... right?
I *think* so, but calling
Hello,
I'm new to using Protocol Buffers and am debugging my program.
Is there a way to pretty print a Message? (I'm new to C++ too and have
tried reading the API but probably missed it).
Also if stepping through GDB and given
REXP *rxp = new REXP();
..
rxp filled in
...
how can i do something
I'm pretty sure #1 is not protobuf's fault. I've never heard of libgcc_s
which means it's probably something GCC links against implicitly. And
anyway, if libwhatever.so.1 exists, there should always be a libwhatever.so
symlink to it... right?
Monty, can you comment on #2?
On Fri, Aug 21, 2009
Kenton Varda wrote:
I'm pretty sure #1 is not protobuf's fault. I've never heard of
libgcc_s which means it's probably something GCC links against
implicitly. And anyway, if libwhatever.so.1 exists, there should always
be a libwhatever.so symlink to it... right?
Sorry - I haven't done any
