Quoting Geoff Thorpe ([EMAIL PROTECTED]):
> 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
I did this. Changed openldap's configure and was told that it was wrong to do
that. That openssl should know which shared libs it needs in order to link
appropriately.
Here is a snippet of the response I got from my patch to the openldap people:
> This patch is just plain wrong. libcrypto.so should be linked against
> whatever libraries it needs to satisfy it's own dependencies. It should
> not force other programs to guess what they are. That's counter
> intuitive to shared library linking.
<snip flame about how stupid I am for this patch>
> I thought the direction was obvious: libcrypto.so needs to link to -ldl
>
> Note, I was not stepping all over you, I was aiming more toward openssl
> for not building correctly :) Sorry if that wasn't apparent.
While the response was hostile, he does make a valid point. Using the official
Redhat RPMs I do not have to patch openldap's configure, somehow it
automatically figures things out on which libraries it needs to patch.
--
Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700
http://www.mn-linux.org | Fax : (952)943-8500
Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
