From the_uhu@hotmail.com Tue Jun 14 01:13:03 2011
From: the_uhu@hotmail.com
To: openldap-bugs@openldap.org
Subject: RE: (ITS#6964) ./configure bug when specifying openssl as the TLS
library to use
Date: Tue, 14 Jun 2011 01:13:02 +0000
Message-ID: <201106140113.p5E1D2Nc039913@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7160619971600922464=="
--===============7160619971600922464==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
--_d1f53d59-c756-486d-94a1-c6fa39a61c52_
Content-Type: text/plain; charset=3D"iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi=3D2C
Am wondering what I am missing here? Because to get OpenLDAP to compile wit=3D
h openssl as the TLS library to use=3D2C I had change this line.
You said that line 19408 on your copy of configure is not the LIBS line bel=3D
ow even though I downloaded openldap fresh - could you offer an explanation=3D
please?
Paul.
From: the_uhu(a)hotmail.com
To: openldap-its(a)openldap.org
Subject: RE: (ITS#6964) ./configure bug when specifying openssl as the TLS =3D
library to use
Date: Thu=3D2C 9 Jun 2011 00:16:10 +0000
I've just downloaded openldap stable fresh=3D2C opened up configure and this =
=3D
is at line 19408 without an if check:
LIBS=3D3D"-lssl -lcrypto -lRSAglue -lrsaref $LIBS"
Also checked the source repository on the website and it's there also.
Can you please double check?
Paul.
> Date: Wed=3D2C 8 Jun 2011 22:13:55 +0000
> From: openldap-its(a)OpenLDAP.org
> To: the_uhu(a)hotmail.com
> Subject: Re: (ITS#6964) ./configure bug when specifying openssl as the TL=3D
S library to use
>=3D20
> I don't know where your configure script came from=3D2C but there's nothing=
=3D
related
> to OpenSSL at line 19408 of the current released configure script=3D2C and =
=3D
our
> script has had logic to detect -lrsaref since 1999.
>=3D20
> Closing this ITS. Use the actual configure script supplied by the OpenLDA=3D
P
> Project.
=3D
--_d1f53d59-c756-486d-94a1-c6fa39a61c52_
Content-Type: text/html; charset=3D"iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi=3D2C
Am wondering what I am missing here? Because to get OpenLDAP t=
=3D
o compile with openssl as the TLS library to use=3D2C I had change this line.=
=3D
You said that line 19408 on your copy of configure is not the LIBS =3D
line below even though I downloaded openldap fresh - could you offer an exp=3D
lanation please?
Paul.
From: the_uhu@=
=3D
hotmail.com
To: openldap-its(a)openldap.org
Subject: RE: (ITS#6964) ./c=
=3D
onfigure bug when specifying openssl as the TLS library to use
Date: Thu=3D
=3D2C 9 Jun 2011 00:16:10 +0000
I've just downloaded openldap stable fresh=3D2C opened up configure and this =
=3D
is at line 19408 without an if check:
LIBS=3D3D"-lssl -lcrypto -lRSAgl=
=3D
ue -lrsaref $LIBS"
Also checked the source repository on the website=3D
and it's there also.
Can you please double check?
Paul.
<=3D
br>
>=3D3B Date: Wed=3D2C 8 Jun 2011 22:13:55 +0000
>=3D3B From: op=
enld=3D
ap-its(a)OpenLDAP.org
>=3D3B To: the_uhu(a)hotmail.com
>=3D3B Subje=
ct: Re=3D
: (ITS#6964) ./configure bug when specifying openssl as the TLS library to =3D
use
>=3D3B
>=3D3B I don't know where your configure script came fr=
om=3D
=3D2C but there's nothing related
>=3D3B to OpenSSL at line 19408 of the=
c=3D
urrent released configure script=3D2C and our
>=3D3B script has had logi=
c =3D
to detect -lrsaref since 1999.
>=3D3B
>=3D3B Closing this ITS. Use=
t=3D
he actual configure script supplied by the OpenLDAP
>=3D3B Project.
=
=3D
=3D
--_d1f53d59-c756-486d-94a1-c6fa39a61c52_--
--===============7160619971600922464==--