Hi everyone,
I just started building OpenLDAP 2.4.48 (stable tarball from openldap.org) and realized that there are some autoconf options regarding SLAPD configuration that do not comply with the --help documentation.
Specifically: First I got errors regarding missing sql.h, then mysql_config. This led to the conclusion that autoconf tried to enable sql and ndb. However, in the documentation it says it'll default to 'no', which is why I didn't explicitly --disable-ndb and --disable-sql. When I do that, it acts as expected and configure is successful.
Unfortunately I'm completely unaware how the handling of these default values is accomplished for autoconf, so I dign't have a chance to look it up myself.
Thanks for any hints,
Dominique
--On Thursday, August 8, 2019 11:51 AM +0000 Dominique Fuchs d.fuchs91@icloud.com wrote:
Hi everyone,
I just started building OpenLDAP 2.4.48 (stable tarball from openldap.org) and realized that there are some autoconf options regarding SLAPD configuration that do not comply with the --help documentation.
Specifically: First I got errors regarding missing sql.h, then mysql_config. This led to the conclusion that autoconf tried to enable sql and ndb. However, in the documentation it says it'll default to 'no', which is why I didn't explicitly --disable-ndb and --disable-sql. When I do that, it acts as expected and configure is successful.
Did you use --enable-backends? If so, that will enable all backends including sql and ndb.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Ahhhh - From the docs I was assuming this is simply necessary to be able to enable specific backends, not automatically enabling all of them. :-/ Got it. Thanks again!
Am 08.08.2019 um 16:18 schrieb Quanah Gibson-Mount quanah@symas.com:
--On Thursday, August 8, 2019 11:51 AM +0000 Dominique Fuchs d.fuchs91@icloud.com wrote:
Hi everyone,
I just started building OpenLDAP 2.4.48 (stable tarball from openldap.org) and realized that there are some autoconf options regarding SLAPD configuration that do not comply with the --help documentation.
Specifically: First I got errors regarding missing sql.h, then mysql_config. This led to the conclusion that autoconf tried to enable sql and ndb. However, in the documentation it says it'll default to 'no', which is why I didn't explicitly --disable-ndb and --disable-sql. When I do that, it acts as expected and configure is successful.
Did you use --enable-backends? If so, that will enable all backends including sql and ndb.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Am 08.08.19 um 16:23 schrieb Dominique Fuchs:
Ahhhh - From the docs I was assuming this is simply necessary to be able to enable specific backends, not automatically enabling all of them.
Hello OpenLDAP Team,
just an idea: rename "--enable-backends" to "--enable-all-backends" in openldap-2.5 ...
Andreas
Hi Andreas,
--On Thursday, August 8, 2019 7:25 PM +0200 "A. Schulze" sca@andreasschulze.de wrote:
just an idea: rename "--enable-backends" to "--enable-all-backends" in openldap-2.5 ...
The help output from configure for the option already clearly states that it enables all backends:
--enable-backends enable all available backends
So maybe renaming the option would help, but it'd also break dozens of existing configuration setups and it's not clear to me that it would really solve anything.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount quanah@symas.com schrieb am 09.08.2019 um 01:28 in
Nachricht <4259D6D7F45C8D518FD13FEE@[192.168.1.144]>:
Hi Andreas,
‑‑On Thursday, August 8, 2019 7:25 PM +0200 "A. Schulze" sca@andreasschulze.de wrote:
just an idea: rename "‑‑enable‑backends" to "‑‑enable‑all‑backends" in openldap‑2.5 ...
The help output from configure for the option already clearly states that it enables all backends:
‑‑enable‑backends enable all available backends
So maybe renaming the option would help, but it'd also break dozens of existing configuration setups and it's not clear to me that it would really
solve anything.
I wonder whether the expectation "nothing was changed in v2.5" actually holds ;-)
Regards, Quanah
‑‑
Quanah Gibson‑Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org