iwasakims opened a new pull request, #896:
URL: https://github.com/apache/bigtop/pull/896

   https://issues.apache.org/jira/browse/BIGTOP-3677
   
   ```
   [ERROR] 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/src/main/protobuf/Cell.proto
 [0:0]: 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe:
 /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe)
   
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe:
 /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe)
   
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe:
 /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe)
   
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe:
 /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by 
/ws/build/hbase/rpm/BUILD/hbase-2.4.11/hbase-protocol/target/protoc-plugins/protoc-2.5.0.2-linux-aarch_64.exe)
   ```
   
   HBASE-26470(https://github.com/apache/hbase/pull/3860) brought fork of 
protobuf (org.openlabtesting.protobuf) to support aarch64 but the provided 
protoc is not enough portable. Since we are using patched protobuf on our own, 
overriding the `external.protobuf.groupid` and `external.protoc.version` should 
be the fix.


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