> > configure:6206: cc -o conftest -I/usr/kerberos/include -O2 -m32
> > -mtune=ultrasparc -D_REENTRANT -fPIC -I/usr/kerberos/include -L/usr/kerberos/lib
> > conftest.c -lssl -lcrypto -lresolv 1>&5
> > /usr/lib/libcrypto.so: undefined reference to `dlclose'
> > /usr/lib/libcrypto.so: undefined reference to `dlopen'
> > /usr/lib/libcrypto.so: undefined reference to `dlsym'
> >
> > What do I need to do to tell openssl that when a program wants libcrypto it must
> > also link libdl?
>
> You could ask the OpenLDAP developers to add some logic to their configuration
> to either guess shared-library linker flags on each platform, or perhaps parse
> them out of OpenSSL's makefile (probably not possible if building against an
> OpenSSL installation rather than a source tree). This can't be handled in
> OpenSSL libraries, which is what you're asking for.
Yes, it can (at least on Solaris, Linux and IRIX as far as I know) and
it actually is ment to be taken care of. Shared libraries can be linked
with other shared libraries the way programs are linked with shared
libraries. libcrypto.so.0.9.6 does get linked with libdl (at least on my
Intel Redhat box, verify with 'ldd libcrypto.so') and you actually
shouldn't have to compliment -lcrypto with -ldl whenever you want to
link your favorite application with the toolkit.
Could you (Bob) run 'make clean; make' and verify last lines when it
creates those shared libraries? What does 'ldd libcrypto.so' print?
Andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
