Bug 2008451

Summary: certmonger: FTBFS because EVP_PKEY_base_id is no longer detected
Product: Red Hat Enterprise Linux 9 Reporter: Florian Weimer <fweimer>
Component: certmongerAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer, ksiddiqu, myusuf
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: certmonger-0.79.14-4.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 13:13:50 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:
Attachments:
Description Flags
build.log none

Description Florian Weimer 2021-09-28 09:40:53 UTC 
Created attachment 1826919 [details]
build.log

A rebuild of certmonger-0.79.14-3.el9 fails:

util-o.c: In function 'util_EVP_PKEY_id':
util-o.c:335:20: error: invalid use of incomplete typedef 'EVP_PKEY' {aka 'const struct evp_pkey_st'}
  335 |         return pkey->type;
      |                    ^~

Context:

int
util_EVP_PKEY_id(const EVP_PKEY *pkey)
{
#ifdef HAVE_EVP_PKEY_ID
        return EVP_PKEY_id(pkey);
#else
        return pkey->type;
#endif
}

The check in configure.ac:

                AC_CHECK_FUNCS(EVP_PKEY_id)

fails:

checking for EVP_PKEY_id... no

EVP_PKEY_id is no longer available as a function, only as a preprocessor macro, so AC_CHECK_FUNCS cannot recognize it.
Comment 7 Mohammad Rizwan 2021-11-30 08:27:17 UTC 
Gating is done. Builds are in nightly. Hence marking the bug as verified.
Comment 9 errata-xmlrpc 2022-05-17 13:13:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: certmonger), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2478