[SSSD] having trouble building master

Yassir Elley yelley at redhat.com
Wed Jul 30 12:47:32 UTC 2014



----- Original Message -----
> On Tue, Jul 29, 2014 at 04:36:38PM -0400, Yassir Elley wrote:
> > Is anyone else having trouble building master?
> > 
> > I pulled the latest bits from master. I am able to successfully "reconfig",
> > but when I "chmake", I am getting the following error:
> > 
> >   CCLD     libsss_autofs.la
> >   CCLD     libsss_idmap.la
> >   CCLD     libsss_nss_idmap.la
> >   CCLD     sssd_krb5_locator_plugin.la
> >   CCLD     memberof.la
> >   CCLD     libipa_hbac.la
> >   CCLD     libsss_crypt.la
> >   CCLD     libsss_util.la
> >   CCLD     libsss_krb5_common.la
> >   CCLD     libsss_ad_common.la
> >   CCLD     pyhbac.la
> >   CCLD     pysss_nss_idmap.la
> >   CCLD     libsss_proxy.la
> >   CCLD     libsss_simple.la
> >   CCLD     libsss_sudo.la
> >   CCLD     sss_sudo_cli
> >   CCLD     krb5_child
> >   CCLD     ldap_child
> >   CCLD     proxy_child
> > src/sss_client/krb5_child-common.o: file not recognized: File truncated
> > collect2: error: ld returned 1 exit status
> > make[2]: *** [krb5_child] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > make[2]: Leaving directory `/home/yelley/git/sssd-gpo/x86_64'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/yelley/git/sssd-gpo/x86_64'
> > make: *** [all] Error 2
> > 
> > Regards,
> > Yassir.
> 
> Can't reproduce here (F-20, 64bit), sorry..
> 
> Does it also happen with non-parallel build? Can you try hardcoding the
> $PROCESSORS variable in contrib/fedora/bashrc_sssd to 1 ?

Hardcoding the $PROCESSORS variable to 1 didn't help. I wasn't getting chmake to successfully perform the build (even after doing a "make clean"), and it would sometimes give other file names as "not recognized: File truncated". There must have been something wrong with my machine environment. When I finally tried running "make" (as opposed to "chmake"), the build was successful. I am now able to use "chmake" again successfully, so the environment seems to have reset itself to a good state.

Thanks,
Yassir.




More information about the sssd-devel mailing list