Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=802169 (Fedora)
Description of problem: In sssd-1.5.x, one could choose to either use libcrypto or mozilla-nss as crypto backend. In sssd-1.8.0, the respective PKG_CHECK_MODULE calls no longer have an else-case, which means both libcrypto and mozilla-nss are required for running configure, even though only one is going to be used during compilation. (Makefile.am still has if HAVE_NSS/...) Version-Release number of selected component (if applicable): sssd-1.8.0 How reproducible: Build sssd in an environment where Mozilla NSS is not installed. Actual results: checking for NSS... configure: error: Package requirements (nss) were not met: Expected results: Ignore NSS if not present and move on to attempt using libcrypto. Additional info:
Assigning to Jakub for triage.
blockedby: => blocking: => coverity: => feature_milestone: => owner: somebody => jhrozek tests: => 0 testsupdated: => 0 upgrade: => 0
This is on purpose, commit 505383e disabled libcrypto support, removed the --with-crypto option.
I believe that if you look at your config.log, you will see a warning about uknown option --with-crypto.
Closing as notabug.
resolution: => invalid status: new => closed
Metadata Update from @dpal: - Issue assigned to jhrozek - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2289
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.