-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Build error for version 2.0.3 and 2.1 #666
Comments
The missing function exists in OpenSSL 1.0.2 and above. https://www.openssl.org/docs/man1.0.2/ssl/SSL_get0_param.html Either
I don't recommend disabling just the code trying to use the OpenSSL apis that make trouble, by, eg, more #ifdef or whatever. Because it enforces OpenSSL to check the server hostname used to make the connection matches a valid name in the server cert, which you will want if you want client ssl connections at all. |
Regarding your points:
Thanks for your help! Maybe you have some more ideas? |
If I look for the api definition on my Fedora box, it's like this
If you go looking for it down Does it change anything if you move your native includes out of the way temporarily?
|
grep also finds it in my dir:
OpenSSL is not in my native includes, so there's nothing to move out of the way... |
Right, but
/home/developer/workspace_clion/dev/contrib/openssl/arm/include/openssl/ssl.h
OpenSSL include dir: /home/developer/workspace_clion/dev/contrib/openssl/arm/include/openssl Unless I miss the point somewhere, it seems not everything that you think is happening, is happening. How about
or so that isn't legal C, and see if the compiler chokes on it or not when you rebuild.
Then it seems it would expect the include path to just be
Can you try that? |
i found it! the previous developer defined the openssl path like this in the bash script:
The second line is the "evil" one. Now i erased it and everything is fine :) |
When I try to build version 2.0.3 or 2.1.0, I get this error:
what my build script does:
Do you have any idea how to solve this?
The text was updated successfully, but these errors were encountered: