https://bugs.openldap.org/show_bug.cgi?id=9778
Issue ID: 9778 Summary: Can't find the back-xxx.la libraries Product: OpenLDAP Version: 2.6.0 Hardware: Other OS: Linux Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: backends Assignee: bugs@openldap.org Reporter: burt.stampfl@amsc.com Target Milestone: ---
Created attachment 870 --> https://bugs.openldap.org/attachment.cgi?id=870&action=edit Output from the build steps I described in the 'description' above.
Hi, I'm new to OpenLDAP. Pulled down the current 2.6 release to a Debian target and am having trouble figuring out how to build the backend modules for dynamic use. What I did: 1. Downloaded openldap-2.6.0.tgz and extracted the source on my Debian target.
2. configured the 'build' via (output indicated it was successful) : ./configure --enable-sql=no --enable-wt=no --enable-spasswd=yes --enable-passwd=yes --enable-perl=yes --enable-crypt=yes --enable-ldap=yes --enable-slapd=yes --enable-ppolicy=yes --enable-otp=yes --enable-auditlog=yes --enable-modules=yes --with-cyrus-sasl=yes
3. ran 'make depend' (output indicated it was successful).
4. ran 'make' (output indicated it was successful).
5. ran the tests via 'env SLAPD_DEBUG=1 make test' (output indicated it was successful).
6. Installed it via 'su root -c 'make install'
I was able to pretty easily get the slapd server running, create a database (mdb) add users, etc, and access via a remote client.
Once I was able to do that I wanted to enable the ppolicy backend/overlay and have not been able to get this to work. Looking online it appears I need some 'backend' modules like back-mdb.la, ppolicy.la, etc and I cannot find them anywhere in my build tree. I had thought the --enable-xxx directives I used in the config step would have forced this to build them, but I guess not.
How do I create these dynamic backend modules and is there any documentation on how to use them in the newer dynamic configuration schema ?
I've attached a file with the output from the steps I performed above.
Thank you Burt
https://bugs.openldap.org/show_bug.cgi?id=9778
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #1 from Quanah Gibson-Mount quanah@openldap.org --- Hello,
The ITS systems is for reporting bugs, not for asking questions about how to build the software. You should direct your question to the openldap-technical@openldap.org software list.
Regards, Quanah
https://bugs.openldap.org/show_bug.cgi?id=9778
Quanah Gibson-Mount quanah@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED
https://bugs.openldap.org/show_bug.cgi?id=9778
--- Comment #2 from burt stampfl burt.stampfl@amsc.com --- Ok, thanks for the feedback and direction. But, you could consider this a bug in documentation if there are no instructions/guidance on how to accomplish this. I will try the other site you noted.
From: openldap-its@openldap.org openldap-its@openldap.org Sent: Thursday, January 6, 2022 2:13 PM To: Stampfl, Burt Burt.Stampfl@amsc.com Subject: [EXTERNAL] [Issue 9778] Can't find the back-xxx.la libraries
https://bugs.openldap.org/show_bug.cgi?id=9778https://bugs.openldap.org/show_bug.cgi?id=9778
Quanah Gibson-Mount <quanah@openldap.orgmailto:quanah@openldap.org> changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs_review | Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #1 from Quanah Gibson-Mount <quanah@openldap.orgmailto:quanah@openldap.org> --- Hello,
The ITS systems is for reporting bugs, not for asking questions about how to build the software. You should direct your question to the openldap-technical@openldap.orgmailto:openldap-technical@openldap.org software list.
Regards, Quanah
-- You are receiving this mail because: You reported the issue. "This e-mail message and any attachments are confidential and may be privileged. If you are not the intended recipient please notify AMSC immediately by replying to this message or by sending a message to postmaster@amsc.com and destroy all copies of this message and any attachments. Thank you."