I was looking over the ldap code and found that it's using the incorrect
library file names when it loads the libldap and liblber libraries.
Rather than using the full libX.so.Y name, it's just loading libX.so.
This means that curl won't read ldap URLs unless the openldap-devel package
is installed.

This issue was discussed here a few weeks ago in relation to loading
libcurl at run time. The solution is to use the proper library
names (e.g. libldap.so.2 and liblber.so.2 on older Linux distributions or
libldap-2.2.so.7 and liblber-2.2.so.7 on more cutting-edge ones),
but these names are probably going to be platform- and version-specific.
That means a configure test is probably the most accurate way to determine
them, but a list of compatible versions could be hard-coded and tried at
run time instead.

Is there any particular reason ldap support was added by binding the
libraries at run time instead of load time like all the other protocols?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved