-
Notifications
You must be signed in to change notification settings - Fork 8
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
ImportError: pycurl: libcurl link-time ssl backend (openssl) is different from compile-time ssl backend (none/other) #4
Comments
Hi @vmihalachi thank you for reporting this issue. This an error from one of the dependencies of tus-py-client, and it is new to me. I found this useful workaround though(not sure if you might have tried it) Basically execute the following steps:
I'll work on a fix in the meantime. |
Hi @ifedapoolarewaju, unfortunately on MacOS this seem to not work. Will try further. |
Hmm, that's weird, did you also try setting it to |
Okey, managed to fix the issue. I am using pipenv for the virtual enviroment https://docs.pipenv.org/. Activating the virtual enviroment:
Exporting two constants (as stated here pyca/cryptography#3489):
Installing with pip
Not sure that was the right way to fix the issue :) |
Apologies for the delay on this. I'll prioritize this some more and have a fix out for it soon. :) |
this issue is now fixed in |
please try the following: https://cscheng.info/2018/01/26/installing-pycurl-on-macos-high-sierra.html I went through similar problem when I upgraded my MAC OS to High-Sierra from El-Captain. install homebrew by and make sure you install openssl using homebrew |
@ifedapoolarewaju thanks!
|
@vmihalachi hey are you on high sierra? https://cscheng.info/2018/01/26/installing-pycurl-on-macos-high-sierra.html |
if you update to |
thanks to you both! 👍 :) |
@hyukkyulee |
use this with homebrew
|
If anyone is having the issue of the opposite on MAC libcurl link-time ssl backend (none/other) is different from compile-time ssl backend (openssl) you will need to reinstall curl with brew using brew reinstall curl --with-openssl In order to have curl built with openssl and not the native Apple OS ssl. You may even see the following error during compile time of pycurl ld: library not found for -lssl3 Once curl is reinstalled with openssl you can then use the above command from zhangheli to install pycurl. Make sure you follow the directions brew spits out for LD_LIBRARY and pkgconfig and the output for openssl |
Below worked for me: pip uninstall pycurl |
The Homebrew team has recently removed all install options for the cURL formula, which means you will not be able to do
|
Starting with @ifedapoolarewaju 's suggestion and by trial and error, the following worked for me:
|
After a couple of searches these steps worked for me on centos:
https://stackoverflow.com/questions/21487278/ssl-error-installing-pycurl-after-ssl-is-set |
for anyone coming in 2022+ for the same issue on mac. I had the same issue for a while trying to get wfuzz to work. when I tried to import pycurl manually, I had the aforementioned error. This is what solved it for me. these commands are taken from the quoted reply above but edited the paths to include the libraries installed in homebrew's directory. make sure all paths are valid on your machine and export PYCURL_CURL_CONFIG=/opt/homebrew/opt/curl/bin/curl-config;
export LDFLAGS='-L/opt/homebrew/opt/openssl@3/lib -L/opt/homebrew/opt/c-ares/lib -L/opt/homebrew/opt/nghttp2/lib -L/opt/homebrew/opt/libmetalink/lib -L/opt/homebrew/opt/rtmpdump/lib -L/opt/homebrew/opt/libssh2/lib -L/opt/homebrew/opt/openldap/lib -L/opt/homebrew/opt/brotli/lib';export CPPFLAGS=-I/opt/homebrew/opt/openssl@3/include;pip install pycurl --compile --no-cache-dir |
Hi, we are using trying to run the tutorial https://transloadit.com/demos/file-importing/import-a-file-over-http/.
When we start the server, an error occurs. Do you know what is causing it?
This is our setup:
Error:
ImportError: pycurl: libcurl link-time ssl backend (openssl) is different from compile-time ssl backend (none/other)
The text was updated successfully, but these errors were encountered: