thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nevo Hed <nhed+thrift...@aereo.com>
Subject Re: Errors while building thirft in OS X
Date Wed, 02 Apr 2014 21:18:51 GMT
Lenin
Can you reply with the output of "gem list" ?



On Wed, Apr 2, 2014 at 5:14 PM, Nevo Hed <nhed+thriftusr@aereo.com> wrote:

> Roger
>
> I think that may be too drastic of a step
> I think this is https://issues.apache.org/jira/browse/THRIFT-2184
>
> In which case he may just need to adjust the installed rspec gems (see my
> comments on 2184)
>
>
> On Wed, Apr 2, 2014 at 7:34 AM, Roger Meier <roger@bufferoverflow.ch>wrote:
>
>> please try this:
>>     rvm use ruby 1.9.3
>>
>> -roger
>>
>>
>> On 01.04.2014 14:39, Lenin Raj wrote:
>>
>>> All - I want to use Thrift to transport data between Python and Ruby.
>>>
>>> I have installed boost and libevent in /usr/local/lib already. I get few
>>> errors while building Thrift. I have attached the log of the output of
>>> make, make test and make install.
>>>
>>>
>>> Failures:
>>>
>>>    1) BinaryProtocolAccelerated it should behave like a binary protocol
>>> should write a byte
>>>       Failure/Error: @trans.rspec_verify
>>>       NoMethodError:
>>>         undefined method `rspec_verify' for
>>> #<Thrift::MemoryBufferTransport:0x007f816ba7b018>
>>>       Shared Example Group: "a binary protocol" called from
>>> ./spec/binary_protocol_accelerated_spec.rb:28
>>>       # ./spec/binary_protocol_spec_shared.rb:112:in `block (2 levels)
>>> in <top (required)>'
>>>
>>>    2) BinaryProtocol it should behave like a binary protocol should
>>> write a byte
>>>       Failure/Error: @trans.rspec_verify
>>>       NoMethodError:
>>>         undefined method `rspec_verify' for
>>> #<Thrift::MemoryBufferTransport:0x007f816bd8c978>
>>>       Shared Example Group: "a binary protocol" called from
>>> ./spec/binary_protocol_spec.rb:25
>>>       # ./spec/binary_protocol_spec_shared.rb:112:in `block (2 levels)
>>> in <top (required)>'
>>>
>>> Is there something I am missing?
>>>
>>> Thanks,
>>> Lenin
>>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message