Hi again!
> Well, no multiple $lazyN is improvement, isn't it? The above error
> message doesn't make sense though. uplink.obj complains about symbol
> being already defined in itself... H-m-m-m... I have to ponder over
> this...
Thanks. But i have made some progress... see later in this mail.
> Stop saying "it works properly." It links, it passes the test, but it's
> missing the functionality. A.
Well, functionality which I don't need. It still works properly for my
purposes. I can link all my applications to these dlls so functionality
for my needs are enough :)) Also I always prefer static libraries. I
only do these things and spend time on it to help you and others to make
openssl is the best.
So I have done more research on this anomaly. I inspected the temporary
file which used to link the dll in the following command:
link /nologo /subsystem:console /opt:ref bufferoverflowU.lib /dll
/out:out32dll\libeay32.dll /def:ms/LIBEAY32.def
@C:\DOCUME~1\admin\LOCALS~1\Temp\nm1659.tmp
So nm1659.tmp contains the following:
uptable.obj uplink.obj tmp32dll\uplink.obj tmp32dll\cryptlib.obj
tmp32dll\mem.obj....... (I don't include the whole file)
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 .
As I see uplink is automatically compiled and included by the make file
without need to be added to SHLIB_EX_OBJ.
Thanks for your time,
--
Matyas Majzik
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
