Bug 2021974

Summary: libwebsockets: FTBFS with OpenSSL 3.0.0
Product: [Fedora] Fedora Reporter: Sahana Prasad <sahana>
Component: libwebsocketsAssignee: Fabian Affolter <mail>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: mail, pbrobinson, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libwebsockets-4.3.1-1.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-20 12:17:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1825937, 1992484, 2045102    

Description Sahana Prasad 2021-11-10 13:40:35 UTC
This bug is used to track the readiness of libwebsockets with OpenSSL 3.0.0.

Currently the build fails to build with OpenSSL 3.0.0 with the following logs
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=78020201

Kindly fix them to ensure this package builds with OpenSSL 3.0.0

You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later.

To not treat deprecated warnings as errors, you may use
-Wno-error=deprecated-declarations

To port to new APIs, kindly refer to the OpenSSL upstream migration guide:
https://www.openssl.org/docs/manmaster/man7/migration_guide.html

Thank you

Comment 1 Robert Scheck 2022-01-15 22:04:56 UTC
Applying upstream's https://github.com/warmcat/libwebsockets/commit/132833a25b9db9f92c6589d027ba66f27b0099a2 would address is, but the build practically fails then due to another issue, for which I've filed https://github.com/warmcat/libwebsockets/issues/2537 at upstream.

Comment 2 Ben Cotton 2022-02-08 21:11:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.