I've compiled and installed
openssl-0.9.7-stable-snap-20020226, and tried to use
..\demos\x509\mkcert.c
I've compiled and installed mkcert.c, using the
..\out32dll\*.lib in order to build it.
Next I copied the ..\out32dll\*.dll onto
..\demos\x509\debug (the directory of mkcert.exe)
When
Just wondering. What are you compiling with that you are seeing
warnings?
I compile this code without any warnings without these modifications.
steve 12-Mar-2002 20:37:23
Modified:ssl kssl.c s3_srvr.c
Log:
Fix Kerberos warnings with VC++.
Revision Changes
When compiling a dynamic 64-bit library on Solaris (via
./Configure solaris64-sparcv9-cc shared), the -xarch=v9 compiler
flag gets dropped when linking the shared libraries. The
resulting libraries are thus 32 bit, and lacking the
lib{ssl,crypto}.a contents (which are 64 bit and thus ignored
by
Jeffrey Altman wrote:
Just wondering. What are you compiling with that you are seeing
warnings?
VC++ 6.0 SP1, Kerberos 1.2.3 headers. I couldn't get the Kerberos 1.2.3
distribution to compile under Windows though. Can 1.2.4 sources/binaries
be downloaded from anywhere outside the US?
The
From: Jeffrey Altman [EMAIL PROTECTED]
jaltman Just wondering. What are you compiling with that you are seeing
jaltman warnings?
jaltman
jaltman I compile this code without any warnings without these modifications.
On Linux, with the target debug-levitte-linux-elf, I got some of those
Richard Levitte - VMS Whacker wrote:
From: Jeffrey Altman [EMAIL PROTECTED]
jaltman Just wondering. What are you compiling with that you are seeing
jaltman warnings?
jaltman
jaltman I compile this code without any warnings without these modifications.
On Linux, with the target
