nephen commented on issue #1328:
URL: https://github.com/apache/incubator-brpc/issues/1328#issuecomment-953488234


   src/brpc/policy/thrift_protocol.cpp: 在函数‘bool 
brpc::policy::ReadThriftStruct(const butil::IOBuf&, brpc::ThriftMessageBase*, 
int16_t)’中:
   src/brpc/policy/thrift_protocol.cpp:133:105: 
错误:对‘apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>::TBinaryProtocolT(boost::shared_ptr<apache::thrift::transport::TMemoryBuffer>&)’的调用没有匹配的函数
        
apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>
 iprot(in_buffer);
                                                                                
                            ^
   src/brpc/policy/thrift_protocol.cpp:133:105: 附注:备选是:
   In file included from src/brpc/policy/thrift_protocol.cpp:39:0:
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:52:3: 
附注:apache::thrift::protocol::TBinaryProtocolT<Transport_, 
ByteOrder_>::TBinaryProtocolT(std::shared_ptr<_Tp1>, int32_t, int32_t, bool, 
bool) [with Transport_ = apache::thrift::transport::TMemoryBuffer; ByteOrder_ = 
apache::thrift::protocol::TNetworkBigEndian; int32_t = int]
      TBinaryProtocolT(std::shared_ptr<Transport_> trans,
      ^
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:52:3: 附注: 备选需要 5 
实参,但提供了 1 个
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:44:3: 
附注:apache::thrift::protocol::TBinaryProtocolT<Transport_, 
ByteOrder_>::TBinaryProtocolT(std::shared_ptr<_Tp1>) [with Transport_ = 
apache::thrift::transport::TMemoryBuffer; ByteOrder_ = 
apache::thrift::protocol::TNetworkBigEndian]
      TBinaryProtocolT(std::shared_ptr<Transport_> trans)
      ^
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:44:3: 附注:  no known 
conversion for argument 1 from 
‘boost::shared_ptr<apache::thrift::transport::TMemoryBuffer>’ to 
‘std::shared_ptr<apache::thrift::transport::TMemoryBuffer>’
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:38:7: 
附注:apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>::TBinaryProtocolT(const
 
apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>&)
    class TBinaryProtocolT : public 
TVirtualProtocol<TBinaryProtocolT<Transport_, ByteOrder_> > {
          ^
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:38:7: 附注:  no known 
conversion for argument 1 from 
‘boost::shared_ptr<apache::thrift::transport::TMemoryBuffer>’ to ‘const 
apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>&’
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:38:7: 
附注:apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>::TBinaryProtocolT(apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>&&)
   /usr/local/include/thrift/protocol/TBinaryProtocol.h:38:7: 附注:  no known 
conversion for argument 1 from 
‘boost::shared_ptr<apache::thrift::transport::TMemoryBuffer>’ to 
‘apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>&&’
   src/brpc/policy/thrift_protocol.cpp: 在函数‘void 
brpc::policy::ReadThriftException(const butil::IOBuf&, 
apache::thrift::TApplicationException*)’中:
   src/brpc/policy/thrift_protocol.cpp:176:105: 
错误:对‘apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>::TBinaryProtocolT(boost::shared_ptr<apache::thrift::transport::TMemoryBuffer>&)’的调用没有匹配的函数
        
apache::thrift::protocol::TBinaryProtocolT<apache::thrift::transport::TMemoryBuffer>
 iprot(in_buffer);
                                                                                
                            ^
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to