Re: (ITS#5967) build failure with openssl : error: structure has no member named `ldo_tls_crlcheck'

[adrien.futschik@atosorigin.com]

Le dimanche 22 février 2009 19:36:31, Quanah Gibson-Mount a écrit :
> --On Sunday, February 22, 2009 6:56 PM +0100 Adrien Futschik
>
> <adrien.futschik@atosorigin.com> wrote:
> > I have just used OpenLDAP 2.4.13, with BDB 4.7.25 & OpenSSL 0.9.8j and it
> > worked fine. I used the same options.
> >
> >
> > I guess there really is a problem with Openldap 2.4.14.
>
> Or, your OpenSSL build is missing required features. ;)
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> --------------------
> Zimbra ::  the leader in open source messaging and collaboration

There seems to be a big change between OpenLDAP 2.4.13 and OpenLDAP 2.4.14 in 
the way configure script chooses OpenSSL or gnutls.

They used to be only on file in OpenLDAP 2.4.13 and lower handeling tls support 
: tls.c in librairies/libldap directory.

In OpenLDAP 2.4.14 we now have : tls2.c, tls_o.c, tls_g.c and tls_m.c
I guess tls_g.c should be used when specifying --with-tls=gnutls,
tls_o.c should be used when specifying --with-tls=openssl
tls_m.c referes to Mozilla (note sure what option trigeres this one).

tls2.c is used when ? 

I believe that configure doesn't care about my --with-tls=openssl option.

Can anyone explain to me why ?

Thanks in advance,

Adrien