hiroyuki-sato commented on PR #51635:
URL: https://github.com/apache/arrow/pull/51635#issuecomment-5903800121
Notes for myself (For future development)
My idea was below
```patch
diff --git a/.github/workflows/ruby.yml b/.github/workflows/ruby.yml
index 7feb8296a3..81de0e0aba 100644
--- a/.github/workflows/ruby.yml
+++ b/.github/workflows/ruby.yml
@@ -184,6 +184,17 @@ jobs:
for ruby_package_gemfile in ruby/*/Gemfile; do \
bundle install --gemfile ${ruby_package_gemfile}
done
+ # Homebrew on macOS now provides OpenSSL 4.x.
+ # However, google-cloud-cpp, which depends on OpenSSL,
+ # does not yet support OpenSSL 4.x.
+ # Therefore, explicitly prefer OpenSSL 3.x here.
+ #
+ # TODO: Once google-cloud-cpp supports OpenSSL 4.x, remove this part
+ # https://github.com/googleapis/google-cloud-cpp/issues/16510
+ - name: Link OpenSSL 3.x
+ run: |
+ brew unlink openssl@4
+ brew link openssl@3
- name: Setup ccache
run: |
ci/scripts/ccache_setup.sh
diff --git a/cpp/cmake_modules/FindOpenSSLAlt.cmake
b/cpp/cmake_modules/FindOpenSSLAlt.cmake
index 03c61e6ea2..e6f21f2d92 100644
--- a/cpp/cmake_modules/FindOpenSSLAlt.cmake
+++ b/cpp/cmake_modules/FindOpenSSLAlt.cmake
@@ -22,7 +22,14 @@ endif()
if(APPLE AND NOT OPENSSL_ROOT_DIR)
find_program(BREW brew)
if(BREW)
- foreach(BREW_OPENSSL_VERSION "" "3" "3.0" "1.1")
+ # Homebrew on macOS now provides OpenSSL 4.x.
+ # However, google-cloud-cpp, which depends on OpenSSL,
+ # does not yet support OpenSSL 4.x.
+ # Therefore, explicitly prefer OpenSSL 3.x here.
+ #
+ # TODO: Once google-cloud-cpp supports OpenSSL 4.x, add `""` before
`"3"`.
+ # https://github.com/googleapis/google-cloud-cpp/issues/16510
+ foreach(BREW_OPENSSL_VERSION "3" "3.0" "1.1")
set(BREW_OPENSSL_PACKAGE "openssl")
if(BREW_OPENSSL_VERSION)
string(APPEND BREW_OPENSSL_PACKAGE "@${BREW_OPENSSL_VERSION}")
```
--
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]
