Just two days ago I was banging my head against this very problem. I
have a C# app that calls into a C++ DLL that utilizes OpenSSL. Adding
applink.c to the DLL project didn't get rid of the error like I hoped it
would, and after analyzing the OpenSSL code I discovered to my dismay
that it always looks in the EXE for the OPENSSL_Applink function. Since
this app is a C# project, adding applink.c to it is pretty much impossible.
I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
Why not BIO_new_file? A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
