Learn more about these different git repos.
Other Git URLs
When i tried to build sssd-1.3.0 on my Gentoo Linux computer, i got some strange errors, which are solved with few number of simple patches:[[BR]] 1) Vanilla sssd source fails to build with error like "Unknown reference to [some function in ldap library]". This is solved by my first patch, 0001-Fix-building-sssd.patch.[[BR]] 2) While configuring, an errors happens while compiling test for ldb_init in -lldb and, as result, configure thinks that there is no ldb_init in -lldb. My second patch, 0002-Fix-configure-check-for-ldb.patch solves this problem[[BR]] 3) If i pass --without-python-bindings to configure script, i got error while running make. Cause of error is that Makefile.am runs python-related parts unconditionally, but when --without-python-bindings is passed, $(PYTHON) is not set and compilation fails. For this issue i wrote third patch, 0003-Fix-pythonless-building.patch. I hope you'll accept these to your upstream.
First patch (for building) 0001-Fix-building-sssd.patch
Second patch (for ldb check) 0002-Fix-configure-check-for-ldb.patch
Third patch (for build withou python support) 0003-Fix-pythonless-building.patch
Fields changed
cc: => spamslepnoga@inbox.ru
I will import patches 1 and 2. They seem just fine.
Patch 3 duplicates a fix I already have on the list awaiting code-review. See: https://fedorahosted.org/pipermail/sssd-devel/2010-August/004357.html
component: SSSD => Build Environment milestone: NEEDS_TRIAGE => SSSD 1.4.0 owner: somebody => sgallagh status: new => assigned
Fixed by: - 126c933 - c67e60f - bf5a808
fixedin: => 1.4.0 resolution: => fixed status: assigned => closed
Thanks for accepting my patches.
rhbz: => 0
Metadata Update from @maksbotan: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.4.0
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/1647
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.