protocol buffer - compilation fails

2008-11-20 Thread Nimisha Mishra
Hello,

 

I have installed protocol buffer 2.0.2 version and trying to build it in
solaris environment. I get this error when I do a make check, Please note
- make ran fine. Please advise .

 

Making check in src

make  check-am

make  check-TESTS

Running main() from gtest_main.cc

[==] Running 557 tests from 85 test cases.

[--] Global test environment set-up.

[--] 1 test from GeneratedDescriptorTest

[ RUN  ] GeneratedDescriptorTest.IdenticalDescriptors

[   OK ] GeneratedDescriptorTest.IdenticalDescriptors

[--] 22 tests from GeneratedMessageTest

[ RUN  ] GeneratedMessageTest.Defaults

[   OK ] GeneratedMessageTest.Defaults

[ RUN  ] GeneratedMessageTest.Accessors

[   OK ] GeneratedMessageTest.Accessors

[ RUN  ] GeneratedMessageTest.MutableStringDefault

[   OK ] GeneratedMessageTest.MutableStringDefault

[ RUN  ] GeneratedMessageTest.Clear

[   OK ] GeneratedMessageTest.Clear

[ RUN  ] GeneratedMessageTest.EmbeddedNullsInBytesCharStar

[   OK ] GeneratedMessageTest.EmbeddedNullsInBytesCharStar

[ RUN  ] GeneratedMessageTest.ClearOneField

[   OK ] GeneratedMessageTest.ClearOneField

[ RUN  ] GeneratedMessageTest.CopyFrom

[   OK ] GeneratedMessageTest.CopyFrom

[ RUN  ] GeneratedMessageTest.CopyConstructor

[   OK ] GeneratedMessageTest.CopyConstructor

[ RUN  ] GeneratedMessageTest.CopyAssignmentOperator

[   OK ] GeneratedMessageTest.CopyAssignmentOperator

[ RUN  ] GeneratedMessageTest.UpcastCopyFrom

[   OK ] GeneratedMessageTest.UpcastCopyFrom

[ RUN  ] GeneratedMessageTest.DynamicMessageCopyFrom

bash: line 4: 15528 Bus Error   (core dumped) ${dir}$tst

FAIL: protobuf-test

==

1 of 1 tests failed

Please report to protobuf@googlegroups.com

==

*** Error code 1

The following command caused the error:

failed=0; all=0; xfail=0; xpass=0; skip=0; \

srcdir=.; export srcdir; \

list='protobuf-test'; \

if test -n $list; then \

  for tst in $list; do \

if test -f ./$tst; then dir=./; \

elif test -f $tst; then dir=; \

else dir=./; fi; \

if  ${dir}$tst; then \

  all=`expr $all + 1`; \

  casein \

  * $tst *) \

xpass=`expr $xpass + 1`; \

failed=`expr $failed + 1`; \

echo XPASS: $tst; \

  ;; \

  *) \

echo PASS: $tst; \

  ;; \

  esac; \

elif test $? -ne 77; then \

  all=`expr $all + 1`; \

  casein \

  * $tst *) \

xfail=`expr $xfail + 1`; \

echo XFAIL: $tst; \

  ;; \

  *) \

failed=`expr $failed + 1`; \

echo FAIL: $tst; \

  ;; \

  esac; \

else \

  skip=`expr $skip + 1`; \

  echo SKIP: $tst; \

fi; \

  done; \

  if test $failed -eq 0; then \

if test $xfail -eq 0; then \

  banner=All $all tests passed; \

else \

  banner=All $all tests behaved as expected ($xfail expected
failures); \

fi; \

  else \

if test $xpass -eq 0; then \

  banner=$failed of $all tests failed; \

else \

  banner=$failed of $all tests did not behave as expected ($xpass
unexpected passes); \

fi; \

  fi; \

  dashes=$banner; \

  skipped=; \

  if test $skip -ne 0; then \

skipped=($skip tests were not run); \

test `echo $skipped | wc -c` -le `echo $banner | wc -c` || \

  dashes=$skipped; \

  fi; \

  report=; \

  if test $failed -ne 0  test -n protobuf@googlegroups.com; then \

report=Please report to protobuf@googlegroups.com; \

test `echo $report | wc -c` -le `echo $banner | wc -c` || \

  dashes=$report; \

  fi; \

  dashes=`echo $dashes | sed s/./=/g`; \

  echo $dashes; \

  echo $banner; \

  test -z $skipped || echo $skipped; \

  test -z $report || echo $report; \

  echo $dashes; \

  test $failed -eq 0; \

else :; fi

make: Fatal error: Command failed for target `check-TESTS'

Current working directory
/var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

*** Error code 1

make: Fatal error: Command failed for target `check-am'

Current working directory
/var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

*** Error code 1

make: Fatal error: Command failed for target `check'

Current working directory
/var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

*** Error code 1

The following command caused the error:

failcom='exit 1'; \

for f in x $MAKEFLAGS; do \

  case $f in \

*=* | --[!k]*);; \

*k*) failcom='fail=yes';; \

  esac; \

done; \

dot_seen=no; \

target=`echo check-recursive | sed s/-recursive//`; \

list='src'; for subdir in $list; do \

  echo Making $target in $subdir; \

  if test $subdir = .; then \

dot_seen=yes; \

local_target=$target-am; \

  else \

local_target=$target; \

  fi; \

  (cd $subdir  make  $local_target) \

  || eval $failcom; \

done; \

if test $dot_seen = no; then \

  make  

Re: protocol buffer - compilation fails

2008-11-20 Thread Kenton Varda
This is a bug that has been fixed in SVN and will be fixed in the 2.0.3
release, which should happen soonish.  If you don't use DynamicMessage you
don't need to worry about it.

On Thu, Nov 20, 2008 at 11:34 AM, Nimisha Mishra 
[EMAIL PROTECTED] wrote:

  Hello,



 I have installed protocol buffer 2.0.2 version and trying to build it in
 solaris environment. I get this error when I do a make check, Please note
 – make ran fine. Please advise .



 Making check in src

 make  check-am

 make  check-TESTS

 Running main() from gtest_main.cc

 [==] Running 557 tests from 85 test cases.

 [--] Global test environment set-up.

 [--] 1 test from GeneratedDescriptorTest

 [ RUN  ] GeneratedDescriptorTest.IdenticalDescriptors

 [   OK ] GeneratedDescriptorTest.IdenticalDescriptors

 [--] 22 tests from GeneratedMessageTest

 [ RUN  ] GeneratedMessageTest.Defaults

 [   OK ] GeneratedMessageTest.Defaults

 [ RUN  ] GeneratedMessageTest.Accessors

 [   OK ] GeneratedMessageTest.Accessors

 [ RUN  ] GeneratedMessageTest.MutableStringDefault

 [   OK ] GeneratedMessageTest.MutableStringDefault

 [ RUN  ] GeneratedMessageTest.Clear

 [   OK ] GeneratedMessageTest.Clear

 [ RUN  ] GeneratedMessageTest.EmbeddedNullsInBytesCharStar

 [   OK ] GeneratedMessageTest.EmbeddedNullsInBytesCharStar

 [ RUN  ] GeneratedMessageTest.ClearOneField

 [   OK ] GeneratedMessageTest.ClearOneField

 [ RUN  ] GeneratedMessageTest.CopyFrom

 [   OK ] GeneratedMessageTest.CopyFrom

 [ RUN  ] GeneratedMessageTest.CopyConstructor

 [   OK ] GeneratedMessageTest.CopyConstructor

 [ RUN  ] GeneratedMessageTest.CopyAssignmentOperator

 [   OK ] GeneratedMessageTest.CopyAssignmentOperator

 [ RUN  ] GeneratedMessageTest.UpcastCopyFrom

 [   OK ] GeneratedMessageTest.UpcastCopyFrom

 [ RUN  ] GeneratedMessageTest.DynamicMessageCopyFrom

 bash: line 4: 15528 Bus Error   (core dumped) ${dir}$tst

 FAIL: protobuf-test

 ==

 1 of 1 tests failed

 Please report to protobuf@googlegroups.com

 ==

 *** Error code 1

 The following command caused the error:

 failed=0; all=0; xfail=0; xpass=0; skip=0; \

 srcdir=.; export srcdir; \

 list='protobuf-test'; \

 if test -n $list; then \

   for tst in $list; do \

 if test -f ./$tst; then dir=./; \

 elif test -f $tst; then dir=; \

 else dir=./; fi; \

 if  ${dir}$tst; then \

   all=`expr $all + 1`; \

   casein \

   * $tst *) \

 xpass=`expr $xpass + 1`; \

 failed=`expr $failed + 1`; \

 echo XPASS: $tst; \

   ;; \

   *) \

 echo PASS: $tst; \

   ;; \

   esac; \

 elif test $? -ne 77; then \

   all=`expr $all + 1`; \

   casein \

   * $tst *) \

 xfail=`expr $xfail + 1`; \

 echo XFAIL: $tst; \

   ;; \

   *) \

 failed=`expr $failed + 1`; \

 echo FAIL: $tst; \

   ;; \

   esac; \

 else \

   skip=`expr $skip + 1`; \

   echo SKIP: $tst; \

 fi; \

   done; \

   if test $failed -eq 0; then \

 if test $xfail -eq 0; then \

   banner=All $all tests passed; \

 else \

   banner=All $all tests behaved as expected ($xfail expected
 failures); \

 fi; \

   else \

 if test $xpass -eq 0; then \

   banner=$failed of $all tests failed; \

 else \

   banner=$failed of $all tests did not behave as expected ($xpass
 unexpected passes); \

 fi; \

   fi; \

   dashes=$banner; \

   skipped=; \

   if test $skip -ne 0; then \

 skipped=($skip tests were not run); \

 test `echo $skipped | wc -c` -le `echo $banner | wc -c` || \

   dashes=$skipped; \

   fi; \

   report=; \

   if test $failed -ne 0  test -n protobuf@googlegroups.com; then \

 report=Please report to protobuf@googlegroups.com; \

 test `echo $report | wc -c` -le `echo $banner | wc -c` || \

   dashes=$report; \

   fi; \

   dashes=`echo $dashes | sed s/./=/g`; \

   echo $dashes; \

   echo $banner; \

   test -z $skipped || echo $skipped; \

   test -z $report || echo $report; \

   echo $dashes; \

   test $failed -eq 0; \

 else :; fi

 make: Fatal error: Command failed for target `check-TESTS'

 Current working directory
 /var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

 *** Error code 1

 make: Fatal error: Command failed for target `check-am'

 Current working directory
 /var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

 *** Error code 1

 make: Fatal error: Command failed for target `check'

 Current working directory
 /var/home/nmishra/protocol_buffer/protobuf-2.0.2/src

 *** Error code 1

 The following command caused the error:

 failcom='exit 1'; \

 for f in x $MAKEFLAGS; do \

   case $f in \

 *=* | --[!k]*);; \

 *k*) failcom='fail=yes';; \

   esac; \

 done; \

 

Re: RPC Design Structure

2008-11-20 Thread codeazure

Thank you Kenton  Shane - it must have been a slow brain day for me
yesterday :-)

I confused the underlying implementation with what PB provides. The
RPC system doesn't know or care how data is transferred.

On Nov 20, 5:56 pm, Shane Green [EMAIL PROTECTED] wrote:
 It sounds like the system in question has a single public service with
 delegates calls to back-end services, distributed across machines
 available to it.  It seems as though the public service provides an
 interface which is essentially a composition of the interfaces provided
 by the services available to it.  

That's is exactly.

 The process of accepting requests for methods it provides on behalf of
 these back-end services, which it handles by delegating to the
 appropriate back-end service, is essentially multiplexing multiple
 services from a single network location.

 If this is at all accurate, then I believe that the API exported by the
 public service should be built, dynamically, based on the set of
 interfaces available to it.  Taking this approach would allow each
 service to define its own interface.  While all the functionality
 available on the network can be exposed as though it were all provided
 by a single entity, assuming there are no naming conflicts ;-)

That sounds like what I should be doing. I was just making it hard for
myself by thinking it was more complicated than it is.

 Or maybe I'm completely confused about the setup.

No, I think you've got it right.

Thanks,
Jeff
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~--~~~~--~~--~--~---



Update roll-up submitted

2008-11-20 Thread Kenton Varda
I just committed SVN revision 76 which integrates a bunch of changes from
our internal codebase (see below).  2.0.3 will probably be released next
week.

protoc
* Enum values may now have custom options, using syntax similar to field
  options.
* Fixed bug where .proto files which use custom options but don't actually
  define them (i.e. they import another .proto file defining the options)
  had to explicitly import descriptor.proto.
* Adjacent string literals in .proto files will now be concatenated, like in
  C.

C++
* Generated message classes now have a Swap() method which efficiently swaps
  the contents of two objects.
* All message classes now have a SpaceUsed() method which returns an
estimate
  of the number of bytes of allocated memory currently owned by the object.
  This is particularly useful when you are reusing a single message object
  to improve performance but want to make sure it doesn't bloat up too
large.
* New method Message::SerializeAsString() returns a string containing the
  serialized data.  May be more convenient than calling
  SerializeToString(string*).
* In debug mode, log error messages when string-type fields are found to
  contain bytes that are not valid UTF-8.
* Fixed bug where a message with multiple extension ranges couldn't parse
  extensions.
* Fixed bug where MergeFrom(const Message) didn't do anything if invoked on
  a message that contained no fields (but possibly contained extensions).
* Fixed ShortDebugString() to not be O(n^2).  Durr.
* Fixed crash in TextFormat parsing if the first token in the input caused a
  tokenization error.

Java
* New overload of mergeFrom() which parses a slice of a byte array instead
  of the whole thing.
* New method ByteString.asReadOnlyByteBuffer() does what it sounds like.
* Improved performance of isInitialized() when optimizing for code size.

Python
* Corrected ListFields() signature in Message base class to match what
  subclasses actually implement.
* Some minor refactoring.

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en
-~--~~~~--~~--~--~---