[openssl.org #499] - request for status update?
Dear OpenSSL Development Team, Richard, and Ben, Thank you for giving a review ticket number #499 for our patch request. We understand that you are all very busy. Could you kindly review our patch request and give us approval to call our port as VOS OpenSSL or OpenSSL for VOS? We very much appreciate your help to us. Our customers are very anxious to receive the OpenSSL product. Please help us here. Could you at least let us know when the team expect to complete the review? This information helps us to share this with our customers and plan accordingly. We are hopeful that you will review our changes shortly. Thank you, Bose __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [CVS] OpenSSL: openssl/crypto/evp/ Makefile.ssl
In message [EMAIL PROTECTED] on Sat, 22 Feb 2003 23:19:49 +0100 (CET), Ulf Moeller [EMAIL PROTECTED] said: Why? mklink.pl will test if symlink is possible, and if not, it will do a copy instead... ulf Log: ulf Copy rather than symlink the test data. ulf This is needed because Windows doesn't support symlinks. ulf ulf The Cygwin/MinGW build now passes make test. ulf ulf Summary: ulf RevisionChanges Path ulf 1.75+1 -1 openssl/crypto/evp/Makefile.ssl ulf ulf ulf patch -p0 ' .' ulf Index: openssl/crypto/evp/Makefile.ssl ulf ulf $ cvs diff -u -r1.74 -r1.75 Makefile.ssl ulf --- openssl/crypto/evp/Makefile.ssl 6 Feb 2003 19:25:11 - 1.74 ulf +++ openssl/crypto/evp/Makefile.ssl 22 Feb 2003 22:19:48 - 1.75 ulf-70,7 +70,7 ulf$(TOP)/util/point.sh Makefile.ssl Makefile ulf$(PERL) $(TOP)/util/mklink.pl ../../include/openssl $(EXHEADER) ulf$(PERL) $(TOP)/util/mklink.pl ../../test $(TEST) ulf -$(PERL) $(TOP)/util/mklink.pl ../../test $(TESTDATA) ulf +cp $(TESTDATA) ../../test ulf$(PERL) $(TOP)/util/mklink.pl ../../apps $(APPS) ulf ulfinstall: ulf. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #425] Build error on Windows NT4?
So I've read this thread, and had a look at the code. What do I have to do
to fix this error? (exactly)
Thank you!
Brendan Law
original thread
The ticket #425 is indeed closable.
That note #define OPENSSL_EXPORT_VAR_AS_FUNCTION made me check my own
doings again (with a magnifying glass)... That error ended up being my
careless mistake :-( Sorry for all the trouble. OpenSSL is doing everything
right. Combination: NT4 + SP6a + VC++(12.00.8804) passed all the tests.
Yours VW
-Original Message-
From: Stephen Henson via RT [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 02, 2003 2:53 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [openssl.org #425] Build error on Windows NT4?
[EMAIL PROTECTED] - Wed Jan 1 18:40:53 2003]:
cl ... -c .\crypto\asn1\n_pkey.c
.\crypto\asn1\n_pkey.c(96) : error C2370:
'NETSCAPE_ENCRYPTED_PKEY_it' :
redefinition; different storage class
.\crypto\asn1\n_pkey.c(93) : see declaration of
'NETSCAPE_ENCRYPTED_PKEY_it'
Strange, I checked VC++ 6.0 SP3 and had no problems. What version of
VC++ are you using?
First of all I want to make it clear that I do *not* have environment
for VC-WIN32 build. All I say here is based on experinence not related
to OpenSSL.
How does one tell VC++SP level? I couldn't find a way. It's probably
more appropriate to ask for version number returned by cl. Mine says
12.00.8804...
Well the version is in the about box of visual studio. Not sure about
the SP level, I just know I installed SP3 on this box and I'll try SP5
when I can find time to download the 100Mb or so of it...
I also have cl version 12.00.8804 BTW
In either case I believe it's OPENSSL_EXTERN which is responsible
for
this. On Windows OPENSLL_EXTERN is[?]/can be defined as extern
_declspec(dllimport) and the problem must be that n_pkey.c refers to
same variable as both local and OPENSSL_EXTERN. The catch is that
_decspec(dllimport) is [and has to be] treated differently. Most
notably
_declspec(dllimport) int i; int foo(){return i;} effectively
compiles
as int *_i; int foo() {return *_i;}. As you can see generated
machine
code has to be substantially different from one generated for plain
int
i; int foo(){return i;} and this is what the compiler must be
complaining about. At the very least if I try to compile int
i;_declspec(dllimport) int i; I get the very same error code, C2370.
A.
I was a little puzzled by the original report. Because it seems to be
complaining about the NETSCAPE_ENCRYPTED_PKEY_it variable whereas under
Win32 this should in fact be a function.
Win32 should #define OPENSSL_EXPORT_VAR_AS_FUNCTION which causes a
different part of asn1t.h to be used. This should end up being written
to opensslconf.h when perl Configure VC-WIN32 is initially called.
So the original poster might want to check to see if this is the case...
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
[openssl.org #425] Build error on Windows NT4?
[EMAIL PROTECTED] - Sun Feb 23 22:17:03 2003]: So I've read this thread, and had a look at the code. What do I have to do to fix this error? (exactly) I didn't find out exactly what the OP did to get this error. However you can check that there is a line: #define EXPORT_VAR_AS_FUNCTION in crypto\opensslconf.h If not make sure you are following all the steps in INSTALL.W32 to the letter. STeve. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
