that when you build shared libs on solaris at least that you create a library
with not all of its symbols resolved... if you do a ldd libldap.so and
see file not found, then you would have your problem found.
aix will by default attempt to resolve every symbol before it can create
an executable/shared object, but can be changed with some
php error... do ldd libphp.so, and look for file not found. do not
if you do the same on liblber.so, you may see
__eprintf is missing (depending on -lgcc was included in your linked
using the ldap libs, you should have to use -lldap -llber for any program
that needs ldap libs then you shouldnt have any problems (i
place my libs in /usr/local/lib and pass to gcc/ld -R, which tells the linker
to search in the colon separated path for libraries. i had to use GNU
binutils to get openssl0.9.6b to build correctly, but removed it for all other
apache or php crash on calls to ldap functions? we also have
apache1.3.20+php4.0.6+mod_ssl+mod_perl+auth_ldap and its all working...
configure options for php included the path to your openldap install base
>----- Original Message -----
>Sent: Tuesday, August 28, 2001 3:23
>Subject: RE: solaris-8 and
>are you using gnu binutils to create the shared
libraries? i have solaris 8 with openldap 2.0.11 and no problems with
yes I've tried to use the GNU-binutils from
But the binutils were not so tolerant to symbol
not found errors.
The executable wasn't an executable
Actually I am using gcc-2.95.3. The rest is all
And therefore I am getting symbol not found
errors with ldd -d / -r
It is software-indendent. Either apache-13.20
nor openldap-2.0.x has been built properly.
What can I do to solve this kind of problem ?
Did you use the gnu-binutils ?
Is ldd -r libldap.so without any symbol not
found errors ? How did you do ? Which enviroment flags did you set for gcc,
ld etc. ?