Fix issue of having both x86-64 and arm64 Homebrew installation and running lisp with arm64 architecture #180
Conversation
…unning lisp with arm64 architecture
When you are having both x86 and arm Homebrews, and running LISP with arm architecture,
attempt to load cl+ssl fails with error:
```
Unable to load foreign library (LIBCRYPTO).
Error opening shared object "/usr/local/Cellar/openssl@1.1/1.1.1s/lib/libcrypto.1.1.dylib":
dlopen(/usr/local/Cellar/openssl@1.1/1.1.1s/lib/libcrypto.1.1.dylib, 10): no suitable image found. Did find:
/usr/local/Cellar/openssl@1.1/1.1.1s/lib/libcrypto.1.1.dylib: mach-o, but wrong architecture
/usr/local/Cellar/openssl@1.1/1.1.1s/lib/libcrypto.1.1.dylib: stat() failed with errno=4.
[Condition of type CFFI:LOAD-FOREIGN-LIBRARY-ERROR]
```
This is because [this code](https://github.com/cl-plus-ssl/cl-plus-ssl/blob/13d824e27cf7f6085086458daea1514b605b3980/src/reload.lisp#L105-L106)
tries to load x86 version of the library first and fails.
My patch fixes this by removing one or another path depending on current Lisp architecture.
|
@svetlyak40wt, does mac have 32-bit version? I mean, shouldn't we do |
|
I don't know. Maybe some old OSX versions can run on some old hardware? I think we could make |
|
The Homebrew installation doc has a footnote 1, saying "For 32-bit or PPC support see Tigerbrew" https://docs.brew.sh/Installation#1 And the Tigerbrew install script says "This script installs to /usr/local only": But I do not understand whether it installs to /usr/local/opt/openssl/lib/ |
|
I don't have such old hardware to check. |
|
Probably we could merge as |
|
I lean towards I hope to add this with a coment and merge in the evening today. |
|
Cool! Thank you! |
…d PPC will work if Tigerview installs the libraries to the /usr/local/opt/openssl prefix.
|
Merged, thank you. |
When you are having both x86-64 and ARM Homebrew, and running LISP with arm architecture, attempt to load cl+ssl fails with error:
This is because this code tries to load x86 version of the library first and fails.
My patch fixes this by removing one or another path depending on current Lisp architecture.