Howdy,
I've built OpenSSL 0.9.6a under Windows 2000 SP1
using Visual C++ 6 (SP3) and MASM 6.11.
I wanted a debug version using a static library
rather than a DLL, so I modified do_masm.bat as
instructed, ran it and nmake -f nt.mak.
Whenever I link with the resulting libeay.lib debug
statis lib I get a linker warning. This also
happens in the OpenSSL build itself, such as when
openssl.exe is linked. Check this out:
link /nologo /subsystem:console /machine:I386 /opt:ref
/debug /out:out32.dbg\openssl.exe @F:\Temp\nmz02052.
libeay32.lib(s1-win32.obj) : warning LNK4200: corrupt
line number information in object file; ignored
I get this same warning when I link libeay32.lib
in my applications. If I ignore this problem and
continue, then in my application, I call
SSL_CTX_new(SSLv3_client_method());
but it returns NULL. When I link the shared library
version of libeay32, the SSL_CTX_new() call works
fine every time. This is leading me to believe that
I cannot actually ignore this linker problem.
It looks like I'm not the first person to run into
this issue. I found the following two messages
in the archives that refer to the same problem:
http://www.mail-archive.com/[email protected]/msg09532.html
http://www.mail-archive.com/[email protected]/msg04783.html
Does anyone have any clue as to what might be up
here?
Thanks,
Jeremy
------------------------
Jeremy Remington
[EMAIL PROTECTED]
Senior Software Engineer
BroadJump, Inc.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
