-
-
Notifications
You must be signed in to change notification settings - Fork 6.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
curl incorrectly reports openssl header/library version mismatch during configure #8279
Comments
That output is totally harmless though and doesn't actually do anything. |
It is more work to maintain that check than the (any?) benefit it brings. Fixes #8279 Reported-by: Satadru Pramanik
So it appears, but when you're debugging building a static curl, you check every error message! May just mention that it might be an issue, or that it might not be a problem? Just trying to save someone some time in the future... 😅 |
I guess this is a larger upstream question: openssl/openssl#17517 |
That refers to runtime checks and the macro purposely avoids that due to cross compiling. Ref: https://github.com/curl/curl/blob/curl-7_81_0/m4/curl-openssl.m4#L116 |
Yeah, that openssl issue is completely separate and independent from this configure check that I propose we simply remove (in #8280) |
I did this
Built curl with OpenSSL 3.0.1
I expected the following
Configure script should not warn about OpenSSL headers and library versions not matching in this case.
curl/libcurl version
[curl -V output]
operating system
(In a container so this isn't that relevant...
Linux cheekon-x86_64 5.16.0-051600-generic #202201092355 SMP PREEMPT Mon Jan 10 00:21:11 UTC 2022 x86_64 GNU/Linux
)Relevant configure output:
Looks like OpenSSL will report the library version as 3.0.0 for all minor version updates of OpenSSL as per: openssl/openssl#17516
The text was updated successfully, but these errors were encountered: