tuhaihe commented on issue #1432: URL: https://github.com/apache/cloudberry/issues/1432#issuecomment-4286702352
Hi @leborchuk thanks for your work to support building Cloudberry on Rocky Linux 10. Prerequest - installing the missing dependencies: ```bash sudo dnf install python3-setuptools sudo dnf install --enablerepo=crb python3-wheel ``` Then I can build the demo cluster successfully with your PR #1678, using the step-by-step way like [Rocky Linux 9](https://cloudberry.apache.org/docs/deployment/quick-build#for-apache-cloudberry-210), or the way [here](https://cloudberry.apache.org/docs/deployment/build-based-on-docker). For the question: > xercex-c should be placed directly under /usr/local/lib - does not know why /usr/local/xerces-c/lib does not rowk Yes, it works indeed. But if you build the cloudberry [this way](https://cloudberry.apache.org/docs/deployment/build-based-on-docker), we need a minor change to the file `/devops/build/automation/cloudberry/scripts/configure-cloudberry.sh`: ```diff diff --git a/devops/build/automation/cloudberry/scripts/configure-cloudberry.sh b/devops/build/automation/cloudberry/scripts/configure-cloudberry.sh index 80575309092..cc9e7376239 100755 --- a/devops/build/automation/cloudberry/scripts/configure-cloudberry.sh +++ b/devops/build/automation/cloudberry/scripts/configure-cloudberry.sh @@ -121,7 +121,7 @@ log_section "Initial Setup" execute_cmd sudo rm -rf ${BUILD_DESTINATION} || exit 2 execute_cmd sudo chmod a+w /usr/local || exit 2 execute_cmd sudo mkdir -p ${BUILD_DESTINATION}/lib || exit 2 -if [[ "$OS_ID" == "rocky" && "$OS_VERSION" =~ ^(8|9) ]]; then +if [[ "$OS_ID" == "rocky" && "$OS_VERSION" =~ ^(8|9|10) ]]; then execute_cmd sudo cp /usr/local/xerces-c/lib/libxerces-c.so \ /usr/local/xerces-c/lib/libxerces-c-3.3.so \ ${BUILD_DESTINATION}/lib || exit 3 ``` Thanks again! -- 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]
