-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS Linker Problem #87
Comments
I don't think I'll be upgrading to Catalina for a long time. Can you install openssl / |
I already had openssl installed so I run I have encountered so many problems with libraries and 32-bit apps and I can agree that you should not upgrade yet. Have a nice day |
We should at least update the code to explain the Catalina workaround. |
I am not sure I understand what you mean. I did not make any changes to the code. I just upgraded openssl using the above command and then re-installed s2 using your build instructions. Now I can run the same code I was running on Linux on macOS. |
If it works with brew upgrade, then it's ok. I thought there might be extra, special steps for Cataline. |
It appears that this issue might be back. Brew removed openssl 1.0 in brew 2.2.0, see aisingapore/TagUI#635 which links to the brew changelog. I attempt to run the following:
and get:
on MacOS Catalina, brew 2.2.10, openssl@1.1: 1.1.1d. As above, xcode tools were already installed with |
It worked for me using these steps:
macOS Catalina |
Hello,
make
command fails with the following errorld: cannot link directly with dylib/framework, your binary is not an allowed client of /usr/lib/libcrypto.dylib for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [libs2.dylib] Error 1 make[1]: *** [CMakeFiles/s2.dir/all] Error 2 make: *** [all] Error 2
That is not the first time i encounter this error after upgrading and I suppose it is a Catalina error. I have already tried
xcode-select --install
but it is not working.Any suggestions?
Thank you in advance
The text was updated successfully, but these errors were encountered: