[SSSD] [PATCH] use proper Kerberos CFLAGS

Jakub Hrozek jhrozek at redhat.com
Thu Feb 6 15:23:19 UTC 2014


On Thu, Feb 06, 2014 at 04:17:50PM +0100, Lukas Slebodnik wrote:
> I was not able reproduce compilation failures with custom build of MIT Kerberos
> installed in /usr/local/. It could not be influenced by libraries installed
> from rpm, because I remove packages krb5-workstation, krb5-devel, krb5-libs
> (rpm -e --nodeps). I also tried build sssd on ubuntu (with custom build of MIT
> Kerberos) and there was not any problem.
> 
> I had to install MIT Kerberos into different directory
> (prefix /usr/local/extra/), but your patch did not solve all problem.
> 
> user at user-virtual-machine:/tmp/sssd$ krb5-config --libs
>    -L/usr/local/extra/lib -Wl,--enable-new-dtags -Wl,-rpath
>    -Wl,/usr/local/extra/lib -lkrb5 -lk5crypto -lcom_err
> user at user-virtual-machine:/tmp/sssd$ krb5-config --cflags
>    -I/usr/local/extra/include
> user at user-virtual-machine:/tmp/sssd$ krb5-config --version
>    Kerberos 5 release 1.12.1
> 
>   CCLD   sssd_pac_plugin.la
> /usr/bin/ld: cannot find -lkrb5
> collect2: error: ld returned 1 exit status
> make[2]: *** [sssd_pac_plugin.la] Error 1
> make[2]: Leaving directory `/tmp/sssd'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/tmp/sssd'
> make: *** [all] Error 2
> 
> There was hardcoded "-lkrb5" in Makefile, so I changed it into $(KRB5_LIBS)
> 
> But there was another problem.
> 
>   CC     src/providers/ldap/ldap_id.lo
> In file included from ./src/providers/krb5/krb5_common.h:34:0,
>                  from ./src/providers/ldap/ldap_common.h:29,
>                  from src/providers/ldap/ldap_id.c:32:
> ./src/util/sss_krb5.h:30:23: fatal error: krb5/krb5.h: No such file or directory
> compilation terminated.
> 
> 
> So I gave up to fix all problems.
> Do you want to fix them?
> 
> Thank you very much for your effort in improving sssd build system.
> 
> LS

I don't think we need to reproduce the failures per se. If the patch
helps their distribution while not breaking ours, that's good enough for
me.



More information about the sssd-devel mailing list