On Tue, Jun 12, 2018 at 05:30:52PM +0000, Joakim Tjernlund wrote: > On Tue, 2018-06-12 at 15:35 +0200, Sumit Bose wrote: > > CAUTION: This email originated from outside of the organization. Do not > > click links or open attachments unless you recognize the sender and know > > the content is safe. > > > > > > On Mon, Jun 11, 2018 at 05:56:44PM +0200, Sumit Bose wrote: > > > On Mon, Jun 11, 2018 at 01:35:53PM +0000, Joakim Tjernlund wrote: > > > > On Mon, 2018-06-11 at 14:09 +0200, Sumit Bose wrote: > > > > > > > > > > > > > > > On Mon, Jun 11, 2018 at 10:50:09AM +0000, Joakim Tjernlund wrote: > > > > > > On Mon, 2018-06-11 at 10:33 +0000, Joakim Tjernlund wrote: > > > > > > > CAUTION: This email originated from outside of the organization. > > > > > > > Do not click links or open attachments unless you recognize the > > > > > > > sender and know the content is safe. > > > > > > > > > > > > > > > > > > > > > On Mon, 2018-06-11 at 11:35 +0200, Michael Ströder wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 06/08/2018 09:57 PM, Jakub Hrozek wrote: > > > > > > > > > SSSD 1.16.2 > > > > > > > > > =========== > > > > > > > > > > > > > > > > > > The SSSD team is proud to announce the release of version > > > > > > > > > 1.16.2 of the > > > > > > > > > System Security Services Daemon. > > > > > > > > > > > > > > > > I've added new build dependency p11-kit-devel but build fails > > > > > > > > and I > > > > > > > > > > > > I too noticed the new dependency on p11-kit, was that intentional ? > > > > > > > > > > p11-kit-devel is now needed if you use --with-crypto=libcrypto to > > > > > build > > > > > support for Smartcard authentication. So far this was only available > > > > > for > > > > > NSS. > > > > > > > > And Smartcard support is mandatory? Using NSS I don't need p11-kit(or > > > > did I misunderstand) ? > > > > > > Currently there is no option to disable the build of the Smartcard > > > helper tool p11_child. NSS has the functionality provided by p11-kit > > > (managing multiple PKCS#11 modules) integrated, hence p11-kit-devel is > > > not need for the NSS build. > > > > > > > Try building with -Wl,--no-allow-shlib-undefined and you will see the > > > > build problem below. > > > > > > The linking issue is not related to p11-kit but is related to some other > > > refactoring. I'm currently trying to reproduce the issue to see how to > > > fix it. > > > > Hi, > > > > please try to add the following patch and then to build SSSD again: > > > > diff --git a/Makefile.am b/Makefile.am > > index 9539b3c..8e76a03 100644 > > --- a/Makefile.am > > +++ b/Makefile.am > > @@ -975,6 +975,7 @@ libsss_cert_la_LIBADD = \ > > $(TALLOC_LIBS) \ > > $(TEVENT_LIBS) \ > > libsss_crypt.la \ > > + libsss_child.la \ > > libsss_debug.la \ > > libsss_certmap.la \ > > $(NULL) > > > > Builds for me.
Thanks for testing and the feedback. > Will there be a new release now? if not, can you mail a "proper" patch ? I will send a pull request to github with the patch. Since I originally had issues reproducing the error I just wanted to know if it really works in other environments as well. bye, Sumit > > Jocke > _______________________________________________ > sssd-users mailing list -- sssd-users@lists.fedorahosted.org > To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/sssd-users@lists.fedorahosted.org/message/42BCCJXAG3FGQE3NTF3244SB7GTN5LJX/ _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/sssd-users@lists.fedorahosted.org/message/PUZRCGQDYLEJERURLZWC2DAA3UJ2SSOC/