-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Compile against openssl 3 #18
Conversation
@conda-forge-admin, please rerender |
It is not using the correct openssl:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
No, actually it is the correct one for the |
|
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.05.03.00.58.55
The error is:
That is familiar as I had already discussed it in #14 . |
Indeed, the issue was the one described in openssl/openssl#18310 . While the proper solution is for openssl to avoid exposing in headers functions that are not on Windows, the problem that we had specifically in pcap is that |
Could you please update the build matrix to build for both versions of openssl? |
Do you have any specific motivation for this? conda-forge stopped supporting openssl 1.* once it completed the openssl3 migration (see conda-forge/conda-forge-pinning-feedstock#3892). Continuing to compile again openssl 1.* can work for some time, but at some point it can break once there is some ABI migration or similar that will not occur for openssl 1.* . |
Ah, I didn't know that. Thanks, merging. |
Perfect, thanks! |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)