On Wed, 25 Jul 2001, CJ Holmes wrote:
> ...
> prebind does a neat trick where is pre-resolves the location of all the
> symbols needed in the dynamic libraries used by a binary. This speeds up
> launch time dramatically. If you app is pre-bound to its dynamic libraries,
> and they are all pre-bound to their dynamic libs, then launching an app is
> much faster. But if the library is not the same as the one your app was
> pre-bound to, then the loader reverts to the normal linking procedures.
>
> Prebinding only works if the app and ALL of its dynamic libs have been
> prebound, so it isn't always possible to get it working for a specific app.
when i try to use the prebind linker flag i get the following warnings
when linking libssl:
[spatburgunder:~/tmp/openssl-0.9.6b] aspa% cc -prebind -dynamiclib -all_load -o
libssl.0.9.6.dylib -compatibility_version 0.9.6 -current_version 0.9.6 libssl.a -L.
-lcrypto
ld: warning prebinding disabled because (__TEXT segment (address = 0x0 size = 0x2f000)
of libssl.0.9.6.dylib overlaps with __TEXT segment (address = 0x0 size = 0xab000) of
libcrypto.0.9.6.dylib
ld: warning prebinding disabled because (__DATA segment (address = 0x2f000 size =
0x3000) of libssl.0.9.6.dylib overlaps with __TEXT segment (address = 0x0 size =
0xab000) of libcrypto.0.9.6.dylib
ld: warning prebinding disabled because (__LINKEDIT segment (address = 0x32000 size =
0xe000) of libssl.0.9.6.dylib overlaps with __TEXT segment (address = 0x0 size =
0xab000) of libcrypto.0.9.6.dylib
any ideas on how to get rid of these warnings?
--
aspa
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
