Re: building with TLS support

["Dane Foster" <dfoster@equitytg.com>]

Howard Chu wrote:
"Without seeing the exact commands that Dane used, and knowing the exact
paths
where the SSL headers and libraries reside, it's impossible to diagnose this
problem."

Dane writes
Below is the command issued:
env CPPFLAGS="-I/opt/openssl-0.9b/include" LIBS="-L/opt/openssl-0.9b/lib"
./configure

I've just re-'make' it and make completed without errors.  What I did
different this time around was change 'LIBS' to 'LDFLAGS'.

Unfortunately, I still can't get the configure to recognize my Cyrus SASL
library.  I'm guessing this doesn't work because I'm using the 2.0.4 BETA
and OpenLDAP 2.0.15 doesn't yet support the newer library.  Any word on when
the newer library will be supported?

Dane Foster
Equity Technology Group, Inc
http://www.equitytg.com.
954.360.9800
----- Original Message -----
From: "Howard Chu" <hyc@highlandsun.com>
To: "Marko Asplund" <aspa@kronodoc.fi>; "Dane Foster" <dfoster@equitytg.com>
Cc: <openldap-software@OpenLDAP.org>
Sent: Saturday, September 22, 2001 6:00 AM
Subject: RE: building with TLS support


> -----Original Message-----
> From: Marko Asplund [mailto:aspa@kronodoc.fi]
> On Fri, 21 Sep 2001, Dane Foster wrote:
> > I have a similar situation, where my OpenSSL filez are in a non standard
> > location.  I followed your instructions and './configure'
> worked without a
> > hitch.  When I finally got to make a get the following error:
> > <snip>
> > /usr/bin/ld: cannot find -lssl
> > collect2: ld returned 1 exit status
> > make[2]: *** [libldap.la] Error 1
> > make[2]: Leaving directory
> > `/usr/local/src/openldap-2.0.15/libraries/libldap'
> > make[1]: *** [all-common] Error 1
> > make[1]: Leaving directory `/usr/local/src/openldap-2.0.15/libraries'
> > make: *** [all-common] Error 1
> > </snip>
>
> try
> setenv LD_LIBRARY_PATH /my/openssl/path # if using a csh variant
> export LD_LIBRARY_PATH=/my/openssl/path # if using a bash variant
>
> or
> sudo su
> echo /my/openssl/path >> /etc/ld.so.conf
> /sbin/ldconfig

Those commands only affect the runtime dynamic linker. The error message
Dane listed
is from the compiler/linker. The proper fix will involve the use of
setenv LDFLAGS "-L/some/pathname"
before running configure.

Without seeing the exact commands that Dane used, and knowing the exact
paths
where the SSL headers and libraries reside, it's impossible to diagnose this
problem.
  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc