Stop saying "it works properly." It links, it passes the test, but it's
missing the functionality.
Well, functionality which I don't need.
Sorry, bit for me it's either everything or nothing. In this particular
context Applink is either there, ready to be used or not there [in which
case I'd have to modify FAQ]. Also keep in mind that it's publicly
archived list, meaning that context of discussion gets fuzzy when people
start searching for keywords. Meaning that if you say something, it pays
off to explicitly mention particular context, at least "works for *my*
purposes," as failure to do so might give wrong impression about *us*.
I
only do these things and spend time on it to help you and others to make
openssl is the best.
But don't take the above rant personally, as it's pretty much just a
pedant's whine:-) As a matter of fact we are sincerely grateful for
feedback and will to resolve problems *our* way. Thank you.
As you can see there is multiple uses of uplink.obj. That is the reason
- I think - why it worked for me without adding to SHLIB_EX_OBJ .
Right!
As I see uplink is automatically compiled and included by the make file
without need to be added to SHLIB_EX_OBJ.
So that adding uptable.obj is sufficient. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
