On Wednesday, October 9, 2002, at 01:27 PM, Martin Costabel wrote:
>
> /usr/bin/ld: Undefined symbols:
> _ldap_url_search
>
> It seems that -lldap is satisfied from /usr/lib/libldap.dylib, not
> from
> /sw/src/openldap-ssl-2.0.23-5/openldap-2.0.23/libraries/libldap.a, and
> the former doesn't have this symbol. The libldap.dylib that is being
> build is hidden in some subdirectory
> /sw/src/openldap-ssl-2.0.23-5/openldap-2.0.23/libraries/libldap/.libs/
> that is not searched.
Yeah, this lets it compile (dynamically)
cc -fno-common -I../../include -I../../include -I/sw/include/db3
-I/sw/include/cyrus-sasl -no-cpp-precomp -I/sw/include
-L/sw/src/openldap-ssl-2.0.23-5/openldap-2.0.23/libraries
-L/sw/src/openldap-ssl-2.0.23-5/openldap-2.0.23/libraries/libldap/.libs
-L/sw/src/openldap-ssl-2.0.23-5/openldap-2.0.23/libraries/liblber/.libs
-L/sw/lib -o ltest test.o -lldap -llber -llutil -lsasl -lssl -lcrypto
-lssl -lcrypto -ldl
Mac OS X does not pick up static libraries if there is a dynamic
alternative. On linux it would probably just link against the .a
symlink that is there in the "libraries" dir.
I'm confused as to why it works at all without those .libs paths.
After linking ltest, what is it linked to for you jfm? I get:
% otool -L ltest
ltest:
/sw/lib/libldap.2.dylib (compatibility version 3.0.0, current
version 3.15.0)
/sw/lib/liblber.2.dylib (compatibility version 3.0.0, current
version 3.15.0)
/sw/lib/libsasl.7.dylib (compatibility version 9.0.0, current
version 9.10.0)
/sw/lib/libssl.0.9.6.dylib (compatibility version 0.9.6,
current version 0.9.6)
/sw/lib/libcrypto.0.9.6.dylib (compatibility version 0.9.6,
current version 0.9.6)
/sw/lib/libdl.0.dylib (compatibility version 0.0.0, current
version 0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 60.2.0)
Also while looking in to this I found a bug in one of apple's libraries:
% otool -L /usr/lib/libsasl2.2.0.1.dylib
/usr/lib/libsasl2.2.0.1.dylib:
/usr/lib/libsasl2.2.0.1.dylib (compatibility version 3.0.0,
current version 1.0.0)
/usr/lib/libcrypto.0.9.dylib (compatibility version 0.9.0,
current version 0.9.6)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 60.0.0)
They have future compatibility. :) I wonder if that could be causing
any problems?
-Ben
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
