xukeawsl opened a new issue, #1138:
URL: https://github.com/apache/rocketmq-clients/issues/1138

   ### Before Creating the Bug Report
   
   - [x] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions).
   
   - [x] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq-clients/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [x] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Programming Language of the Client
   
   C++
   
   ### Runtime Platform Environment
   
   Ubuntu20.04
   
   ### RocketMQ Version of the Client/Server
   
   version:cpp-5.0.3
   
   ### Run or Compiler Version
   
   complier:clang++-12
   os:ubuntu20.04
   
   ### Describe the Bug
   
   尝试使用cmake编译cpp的examples,按照流程先安装的 grpc,版本是 v1.76.0,使用的 cmake 版本是 
3.16.3,编译时先是报错/root/rocketmq-clients/cpp/source/scheduler/include/SchedulerImpl.h:55:27:
 error: expected ';' at end of declaration list
     void shutdown() override LOCKS_EXCLUDED(tasks_mtx_);
   然后我把 LOCKS_EXCLUDED(tasks_mtx_); 都注释掉了,可能是 clang++ 版本问题?后面再编译时报错 
/root/rocketmq-clients/cpp/source/base/CredentialsProvider.cpp:91:31: error: no 
type named 'Status' in namespace 'google::protobuf::util'
         google::protobuf::util::Status status = 
google::protobuf::util::JsonStringToMessage(content, &root);
   这个看着好像是因为 protobuf 的版本问题?
   
   ### Steps to Reproduce
   
   如果是因为版本问题,请问我应该使用什么版本的 clang 和什么版本的 grpc 才能成功编译呢
   
   ### What Did You Expect to See?
   
   期望能够编译通过
   
   ### What Did You See Instead?
   
   实际上编译报错
   
   ### Additional Context
   
   _No response_


-- 
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]

Reply via email to