dongjoon-hyun opened a new pull request, #2386:
URL: https://github.com/apache/orc/pull/2386

   ### What changes were proposed in this pull request?
   
   This PR aims to use `int64_t` instead of `google::protobuf::int64` to follow 
ProtocolBuff v22.0 changes.
   
   - https://github.com/protocolbuffers/protobuf/releases/tag/v22.0
   
   > Fixed C++ code generation for protos that use int32_t, uint32_t, int64_t, 
uint64_t, size_t as field names.
   
   ### Why are the changes needed?
   
   Currently, `branch-2.1` branch CIs are broken like the following.
   
   ```
   /Users/runner/work/orc/orc/c++/src/io/InputStream.hh:76:31: error: no type 
named 'int64' in namespace 'google::protobuf'
       virtual google::protobuf::int64 ByteCount() const override;
               ~~~~~~~~~~~~~~~~~~^
   /Users/runner/work/orc/orc/c++/src/io/InputStream.cc:115:21: error: no type 
named 'int64' in namespace 'google::protobuf'
     google::protobuf::int64 SeekableArrayInputStream::ByteCount() const {
     ~~~~~~~~~~~~~~~~~~^
   /Users/runner/work/orc/orc/c++/src/io/InputStream.cc:116:42: error: no type 
named 'int64' in namespace 'google::protobuf'
       return static_cast<google::protobuf::int64>(position_);
                          ~~~~~~~~~~~~~~~~~~^
   3 errors generated.
   make[2]: *** [c++/src/CMakeFiles/orc.dir/io/InputStream.cc.o] Error 1
   ```
   
   ### How was this patch tested?
   
   Pass the CIs.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   No.


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