Opened 3 years ago
Closed 3 years ago
#63854 closed defect (fixed)
ldns: error: incomplete definition of type 'struct evp_pkey_st'
Reported by: | marka63 | Owned by: | Schamschula (Marius Schamschula) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ShadSterling (Shad Sterling), Schamschula (Marius Schamschula), blair (Blair Zajac) | |
Port: | ldns |
Description
ldns fails to build against the latest openssl 3.0.0 package. Will most probably need OPENSSL_SUPPRESS_DEPRECATED to be defined when building.
Attachments (2)
Change History (15)
Changed 3 years ago by marka63
comment:1 Changed 3 years ago by reneeotten (Renee Otten)
comment:2 Changed 3 years ago by jmroot (Joshua Root)
Yes, the structs were already made opaque in 1.1.
comment:3 Changed 3 years ago by marka63
EVP_PKEY_base_id was a function prior to OpenSSL 3. It has been replaced with a #define which breaks configure.
comment:4 Changed 3 years ago by marka63
Adding a weak symbol for EVP_PKEY_base_id as an alias for EVP_PKEY_get_base_id would allow configure to work for existing programs.
comment:5 Changed 3 years ago by marka63
Patching dnssec_sign.c to look for OpenSSL's EVP_PKEY_base_id define or looking for HAVE_EVP_PKEY_BASE_ID will also work. See dnssec_sign.c patch and should work with both OpenSSL < 3.0 and OpenSSL 3.0
comment:6 Changed 3 years ago by danielluke (Daniel J. Luke)
Also reported upstream: https://github.com/NLnetLabs/ldns/issues/143
comment:7 Changed 3 years ago by ShadSterling (Shad Sterling)
Cc: | ShadSterling added |
---|
comment:8 Changed 3 years ago by Schamschula (Marius Schamschula)
Cc: | Schamschula added |
---|
comment:9 Changed 3 years ago by reneeotten (Renee Otten)
Summary: | ldns does not build against openssl-3.0.0 → ldns: error: incomplete definition of type 'struct evp_pkey_st' |
---|
comment:10 Changed 3 years ago by danielluke (Daniel J. Luke)
upstream v1.8.0 will include a configure change for EVP_PKEY_get_base_id - https://github.com/NLnetLabs/ldns/commit/5100d8546b1a9c3d08cf9e24cd7e30421033ec4c
comment:11 Changed 3 years ago by blair (Blair Zajac)
Cc: | blair added |
---|
comment:12 Changed 3 years ago by blair (Blair Zajac)
Can we use that patch for the current 1.7.1 release and get ldns unbroken?
comment:13 Changed 3 years ago by Schamschula (Marius Schamschula)
Owner: | set to Schamschula |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I am not convinced that these errors are related to OpenSSL v3 (the warnings indeed are). I just tried to have this port use the openssl PG and version 1.1, but it fails as well: