ODBC can#39;t find correct OpenSSL version after upgrading OpenSSL(升级 OpenSSL 后 ODBC 找不到正确的 OpenSSL 版本)
问题描述
更新:如果您遇到同样的问题,正在讨论问题的根源
我该如何解决这个问题?对这个不是很熟悉.所以ODBC需要找到正确的OpenSSL版本,即1.1.
我试过了:
此外,当我运行 openssl
命令时,它会找到正确的版本:
输出 brew list openssl@1.1
ls -l/usr/local/opt/openssl/lib/libssl.dylib 的输出
同时运行 DYLD_PRINT_LIBRARIES=1 isql -v -k "<connection string"
给我以下内容.似乎它仍然链接到 openssl@3
在尝试了很多事情之后,我找到了一个(hacky)解决方案:
- 我删除了
/usr/local/opt/
中的链接:
- 创建了一个指向 openssl@1.1 的新链接
Update: if you have this same issue, the source of the problem is being discussed here
After upgrading to Python3.10 with homebrew, my OpenSSL was upgraded to version 3 as well.
Now I can't connect to my SQL Server anymore, since ODBC requires OpenSSL 1.1 or 1.0. So when I run:
I get the following error:
But when I look in /usr/local/etc/
I see that openssl@1.1
is installed:
How can I solve this problem? Not really familiar with this. So ODBC needs to find the correct OpenSSL version, which is 1.1.
I tried:
Also when I run openssl
command, it finds the correct version:
Output brew list openssl@1.1
Output of ls -l /usr/local/opt/openssl/lib/libssl.dylib
Also running DYLD_PRINT_LIBRARIES=1 isql -v -k "<connection string"
gives me the following. Seems like it is still linked to openssl@3
After trying many things, I found a (hacky) solution:
- I removed the link in
/usr/local/opt/
:
- Created a new link to openssl@1.1
这篇关于升级 OpenSSL 后 ODBC 找不到正确的 OpenSSL 版本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!