Hi! > > Static linking does not seem appropriate as I cant get my app to > > statically link against libssl/libcrypto (I get lots of undefined > > symbol errors) and statically linking tends to not work well across > > platforms that have different versions of underlying libraries. > > > > That seems strange, why would linking against libssl.a/libcrypto.a > give problems? What unresolved symbols do you get? You could still > link dynamically against system libraries while using > libssl.a/libcrypto.a (atleast i think so).
I havent figured out how to switch between static linking for libssl.a/libcrypto.a and dynamically linking the rest. If I link with -static, it links the whole thing statically and I havent figured out how to re-enable it. Also, since the libs are compiled on one platform and then the app is often moved to different systems, statically linking the library to external symbols could cause problems. I am working on munging the makefiles to remove the soname from the library build. Then, the linker simply looks for filename matches rather than soname matches. Thanks, Bobby ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
