[Date Prev][Date Next]
Re: (ITS#5945) --enable-backends=auto support
On Feb 13, 2009, at 5:55 PM, firstname.lastname@example.org wrote:
> quanah@OpenLDAP.org wrote:
>> Full_Name: Quanah Gibson-Mount
>> Version: 2.4.13
>> OS: NA
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (126.96.36.199)
>> It would be handy to allow --enable-backends to have auto support
>> so that all
>> available backends can be selected. The current behavior is "yes",
>> which means
>> that if you don't have the requisites for a given backend,
>> configure stops.
> Accommodating this request would make other things much more
> Currently the backends and overlay options toggle between "no | yes
> | mod"
> where "yes" means "yes+static" and "mod" means "yes+dynamic". An
> "auto" option
> here doesn't allow you to select static vs dynamic.
We could have auto => yes+static and automod => yes+dyanmic.
But that might be too cumbersome as well.
> Adding "auto" would revert
> us back to OpenLDAP 2.0's behavior, where every backend required two
> switches "--enable-bdb" and "--enable-bdb-mod=static" (or dynamic)
> which IMO
> was far too cumbersome.
> Likewise it would require rewriting most of the backends' detection
> tests in
> configure.in, which currently use AC_MSG_ERROR when a prereq isn't
> found. All
> of those would have to be turned into warnings/bailouts in the
> "auto" case,
> instead of aborting the configure run.
There's still a lot of old auto tests in configure.in, even for new
things like ndb. :-)
> IMO, seems like more effort than it's worth.
I just noting that for testing, it kind of nice to just be able to do
./configure --enable-backends=auto --enable-overlays=auto
To test everything that available on the box.
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/