- ectest.c
6. Add pragma to disable warnings.
- rc2_skey.c, rsa_pss.c
7. Add pragma to disable optimizations because they cause 'Internal
Compile Error' while compiling for Windows Mobile 2003 (WCE420/ARMV4).
I'll throw in additional defined(_MSC_VER) to those #ifs as the pragmas
in question
Hi,
At 07 Aug 2005 21:39:15 +0200 Andy Polyakov wrote:
- ectest.c
6. Add pragma to disable warnings.
- rc2_skey.c, rsa_pss.c
7. Add pragma to disable optimizations because they cause 'Internal
Compile Error' while compiling for Windows Mobile 2003 (WCE420/ARMV4).
I'll throw in
Hi Steven:
At 04 Aug 2005 11:07:08 +1000 Steven Reddie wrote:
Satoshi, I found my old files. The makefiles I obtained from eVC3 and eVC4
for a little test.exe may have been munged a little as I extracted the
information I needed; it was two years ago so I don't recall.
Thank you for
Hi,
At 04 Aug 2005 01:00:10 +0900 Satoshi Nakamura wrote:
At 02 Aug 2005 17:43:46 +0200 Andy Polyakov wrote:
Is this universal for CE compilers? What's difference between CORELIBC.
LIB and LIBC.LIB? If one refers to DLL, can you post output from
dumpbin /exports for that DLL? Again, for my
Hi,
At 03 Aug 2005 18:26:20 +0200 Andy Polyakov wrote:
Here is a patch to fix these problems except for 8. About 8, you can
supress it using pragma or just add a command line option.
You mean like #pragma warning(disable:4959) or /wd4959? Please verify
either and confirm.
Unfortunatelly,
- des_old.h, ui_locl.h
5. Undef '_' for SH3 and SH4. For SH3 and SH4, '_' is defined as '1' and
it causes a compile error. Although I think it's better to change the
variable name, I add '#undef _' just to compile.
Well, I'd rather go for
#ifdef _
#undef _
#endif
I mean I would not make
+#if defined(OPENSSL_SYS_WINCE) defined(_MIPS_)
+#pragma warning(push)
+#pragma warning(disable:4959)
+#endif
It appears that warning numbers may vary among compiler releases...
Therefore it would be appropriate not only add defined(_MSC_VER), but
even _MSC_VER==:-( To tell _MSC_VER
Hi,
At 03 Aug 2005 00:25:27 +0200 Andy Polyakov wrote:
Test 20050803 snapshot as it becomes available. It addresses this and
the other problems/suggestions discussed so far. A.
I tested it. It's getting better, but still has some problems.
- VC-32.pl
1. It seems semi-colon is required after
Hi,
At 02 Aug 2005 17:43:46 +0200 Andy Polyakov wrote:
Is this universal for CE compilers? What's difference between CORELIBC.
LIB and LIBC.LIB? If one refers to DLL, can you post output from
dumpbin /exports for that DLL? Again, for my reference... To spare the
public some bandwidth, send
Hi,
At 03 Aug 2005 00:15:34 +0900 Satoshi Nakamura wrote:
At 02 Aug 2005 14:23:17 +0200 Andy Polyakov wrote:
In rand_win.c we could read
#if defined(OPENSSL_SYS_WINCE) WCEPLATFORM!=MS_HPC_PRO
Well, WCEPLATFORM!=MS_HPC_PRO condition is *never* met... Meaning that
CryptGenRandom was
I tested it. It's getting better, but still has some problems.
- VC-32.pl
1. It seems semi-colon is required after }.
2. Use /machine:MIPS instead of /machine:R4100 or something for MIPS.
Got it.
- cryptlib.c
3. MB_TASKMODAL is not supported.
I've chosen to skip it unconditionally.
In rand_win.c we could read
#if defined(OPENSSL_SYS_WINCE) WCEPLATFORM!=MS_HPC_PRO
Well, WCEPLATFORM!=MS_HPC_PRO condition is *never* met... Meaning that
CryptGenRandom was never called on *any* WCE platform, instead of all
but MS_HPC_PRO... Fixed by replacing it with _WIN32_WCE=210 condition,
Hi,
At 03 Aug 2005 18:46:53 +0200 Andy Polyakov wrote:
Well, MSDN mentions that 210 is minimum requirement *and* on elder
reference page it mentions that the target application or dll should be
linked with cryptapi.lib. Can this be explanation for link error? A.
cryptapi.lib itself is not
Satoshi Nakamura wrote:
And I'm thinking of creating a list which includes:
1. Environment variables which are set by the batch file.
2. Compiler/Linker options which are set by IDE and how they are
expanded.
for each major platform and cpu.
Hi Satoshi,
I did this a couple of years ago
The vision is to reduce WCE-isms to #if
defined(_WIN32_WCE) _WIN32_WCE=*minimally_required* and eventual
#ifdef PLATFORM [there it's *proven* to be required]. The latter is
currently broken as I now realize, by means of essentially meaningless
-DWCEPLATFORM=$wceplatf
In rand_win.c we could
One change that you may want to make is turning off the optimisations. I
think the flags are /Ox /Ob2 /O2. /Ox and /O2 will cause eVC4 to
break with
internal compiler errors on a number of modules.
Well, let's set them to least common denominator
How does /O1i sound? 1 means optimize for
Hi,
At 01 Aug 2005 11:31:57 +0200 Andy Polyakov wrote:
And therefore I've decided to eliminate dependency on wcedefs.mak [from
wcecompat] and implemented the corresponding logic directly to VC-32.mak.
Grab latest snapshot to test it. For reference. Note that this change
doesn't eliminate
I got openssl-0.9.8-stable-SNAP-20050801.tar.gz and found some problems.
1. Use /MC instead of /MD and /MDd
/MD and /MDd are not supported for Windows CE.
For my reference. What's /MC? I can't find it on MSDN... Can you post
output from 'cl /help'?
2. Define UNDER_CE as well as _WIN32_WCE.
Hi,
At 02 Aug 2005 14:23:17 +0200 Andy Polyakov wrote:
In rand_win.c we could read
#if defined(OPENSSL_SYS_WINCE) WCEPLATFORM!=MS_HPC_PRO
Well, WCEPLATFORM!=MS_HPC_PRO condition is *never* met... Meaning that
CryptGenRandom was never called on *any* WCE platform, instead of all
but
Hi,
At 02 Aug 2005 23:37:43 +0900 Satoshi Nakamura wrote:
Here is a patch.
Sorry, there was a small bug. This is the correct one against
snapshot-20050802.
diff -ur openssl-0.9.8-stable-SNAP-20050802.orig/util/pl/VC-32.pl
openssl-0.9.8-stable-SNAP-20050802/util/pl/VC-32.pl
---
In addition, this patch is required to compile.
diff -ur openssl-0.9.8-stable-SNAP-20050802.orig/crypto/cryptlib.c
openssl-0.9.8-stable-SNAP-20050802/crypto/cryptlib.c
--- openssl-0.9.8-stable-SNAP-20050802.orig/crypto/cryptlib.c 2005-07-05
09:04:43.0 +0900
+++
Hi,
At 02 Aug 2005 17:14:52 +0200 Andy Polyakov wrote:
For my reference. What's /MC? I can't find it on MSDN... Can you post
output from 'cl /help'?
This is cut from output of clarm /?, which is in WCE300 directory.
---
-LINKING-
/MC link with COREDLL.LIB,
Hi,
At 02 Aug 2005 17:26:51 +0200 Andy Polyakov wrote:
What fails more specifically? I'd prefer to keep OPENSSL_showfatal,
which would show dialog box on WCE... A.
Here is an error message I got:
Building OpenSSL
clarm.exe /Fotmp32dll_ARM\cryptlib.obj -Iinc32 -Itmp32dll_ARM /MC /Ox
This is cut from output of clarm /?, which is in WCE300 directory.
---
-LINKING-
/MC link with COREDLL.LIB, CORELIBC.LIB
/ML link with COREDLL.LIB, LIBC.LIB
Is this universal for CE compilers? What's difference between
CORELIBC.LIB and LIBC.LIB? If one refers
.\crypto\cryptlib.c(634) : error C2220: warning treated as error - no object
file generated
.\crypto\cryptlib.c(634) : warning C4013: 'GetProcessWindowStation' undefined;
assuming extern returning int
I see. This should be fixed in another place...
.\crypto\cryptlib.c(746) : warning C4013:
.\crypto\cryptlib.c(634) : error C2220: warning treated as error - no
object file generated
.\crypto\cryptlib.c(634) : warning C4013: 'GetProcessWindowStation'
undefined; assuming extern returning int
I see. This should be fixed in another place...
.\crypto\cryptlib.c(746) : warning C4013:
OK, I can see that WCEVERSION is defined in 3rd party wcecompat.mak,
but I would feel better if we use variable set by VCVARS*.BAR or
whatever it's called in embedded C. Meaning that I'd like to rephrase
the question. Can you figure out variables set by VC, which we can use?
They are
] [mailto:[EMAIL PROTECTED]
On Behalf Of Andy Polyakov
Sent: Monday, 1 August 2005 7:32 PM
To: openssl-dev@openssl.org
Subject: Re: mk1mf.pl doesn't generate makefile for Windows CE
OK, I can see that WCEVERSION is defined in 3rd party wcecompat.mak,
but I would feel better if we use variable set
I haven't been keeping on top of the issues with CE builds (since they
worked for me with a few minor tweaks). What was the problem with
wcedefs.mak?
Lack of support for *arbitrary* CE version, most notably 300, lack of
support for commonly referred _WIN32_WCE and lack of support for
I've chosen to unify VC-32.pl and VC-CE.pl instead. I mean VC-CE.pl is
gone now and VC-32.pl is expected to take care of all Windows flavors,
Win32, Win64 and WinCE. See http://cvs.openssl.org/chngview?cn=14275
for reference.
I see. I downloaded the latest 0.9.8-snapshot, and it generates
Hi,
At 25 Jul 2005 11:27:32 +0200 Andy Polyakov wrote:
I've been browsing through MSDN and didn't quite figured out where
_WIN32_WCE and platform-specific pre-processor macros get
assigned/defined. Most notably I used to believe that they're pre-
defined by compiler driver itself, but [this
I found
reference that at least _WIN32_WCE is defined through project
preferences as -D_WIN32_WCE=$(CEVersion).
I think we need to fix this problem before everything else. The simplest
way to fix this problem is to add -D_WIN32_WCE=$(WCEVERSION) after
$(WCETARGETDEFS) in makefiles.
Can you
I found
reference that at least _WIN32_WCE is defined through project
preferences as -D_WIN32_WCE=$(CEVersion).
I think we need to fix this problem before everything else. The simplest
way to fix this problem is to add -D_WIN32_WCE=$(WCEVERSION) after
$(WCETARGETDEFS) in makefiles.
Can you
Hi,
At 25 Jul 2005 23:36:41 +0200 Andy Polyakov wrote:
Can you double-confirm this? MSDN mentions -D_WIN32_WCE=$(CEVersion)
and you suggest -D_WIN32_WCE=$(WCEVERSION). Is one wrong or are both
right?
OK, I can see that WCEVERSION is defined in 3rd party wcecompat.mak,
but I would feel
Hi,
At 25 Jul 2005 00:19:17 +0200 Andy Polyakov wrote:
I've chosen to unify VC-32.pl and VC-CE.pl instead. I mean VC-CE.pl is
gone now and VC-32.pl is expected to take care of all Windows flavors,
Win32, Win64 and WinCE. See http://cvs.openssl.org/chngview?cn=14275
for reference.
I see. I
35 matches
Mail list logo
