This is a message in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.

--AKMAILBOUNDARY
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Steve,
> Applied.

thanks again!

> There are a couple of new ones which I'd initially omitted from the
> Windows build: -DSHA256_ASM and -DSHA512_ASM.

ok - then I need these also in netware.pl - see patch below and attached:

--- netware.pl.orig=09Fri Jan 04 13:05:02 2008
+++ netware.pl=09Fri Jan 04 20:33:27 2008
@@ -332,7 +332,8 @@
$whirlpool_asm_src=3D"crypto${o}whrlpool${o}asm${o}wp-nw.asm";
$cpuid_asm_obj=3D"\$(OBJ_D)${o}x86cpuid-nw${obj}";
$cpuid_asm_src=3D"crypto${o}x86cpuid-nw.asm";
- $cflags.=3D" -DOPENSSL_CPUID_OBJ -DBN_ASM -DOPENSSL_BN_ASM_PART_WORDS =
-DMD5_ASM -DSHA1_ASM -DWHIRLPOOL_ASM";
+ $cflags.=3D" -DOPENSSL_CPUID_OBJ -DBN_ASM -DOPENSSL_BN_ASM_PART_WORDS =
-DMD5_ASM -DWHIRLPOOL_ASM";
+ $cflags.=3D" -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM";
$cflags.=3D" -DAES_ASM -DRMD160_ASM";
}
else

> Creating the things in the batch file seems a bit of a hack and they cou=

ld
> be handled in the makefile in the same way as the Unix build.


> The Configure script also works out things like CFLAGS for the relevant
> options. The WIN32 build partly duplicates this functionality, it should
> really just pick up whatever options the Configure script has decided.

hmm, since the configure script is written in Perl I was also already thin=
king if we could work with that only....

If I have next some spare time I will give it a try, and try to figure out=
what's adaptable from Unix world....

thanks, Guen.


--AKMAILBOUNDARY
Content-Type: application/octet-stream; name="netware.pl.diff"
Content-Transfer-Encoding: base64

LS0tIG5ldHdhcmUucGwub3JpZwlGcmkgSmFuIDA0IDEzOjA1Oj AyIDIwMDgN
CisrKyBuZXR3YXJlLnBsCUZyaSBKYW4gMDQgMjA6MzM6MjcgMj AwOA0KQEAg
LTMzMiw3ICszMzIsOCBAQA0KICAgICR3aGlybHBvb2xfYXNtX3 NyYz0iY3J5
cHRvJHtvfXdocmxwb29sJHtvfWFzbSR7b313cC1udy5hc20iOw 0KICAgICRj
cHVpZF9hc21fb2JqPSJcJChPQkpfRCkke299eDg2Y3B1aWQtbn cke29ian0i
Ow0KICAgICRjcHVpZF9hc21fc3JjPSJjcnlwdG8ke299eDg2Y3 B1aWQtbncu
YXNtIjsNCi0gICAkY2ZsYWdzLj0iIC1ET1BFTlNTTF9DUFVJRF 9PQkogLURC
Tl9BU00gLURPUEVOU1NMX0JOX0FTTV9QQVJUX1dPUkRTIC1ETU Q1X0FTTSAt
RFNIQTFfQVNNIC1EV0hJUkxQT09MX0FTTSI7DQorICAgJGNmbG Fncy49IiAt
RE9QRU5TU0xfQ1BVSURfT0JKIC1EQk5fQVNNIC1ET1BFTlNTTF 9CTl9BU01f
UEFSVF9XT1JEUyAtRE1ENV9BU00gLURXSElSTFBPT0xfQVNNIj sNCisgICAk
Y2ZsYWdzLj0iIC1EU0hBMV9BU00gLURTSEEyNTZfQVNNIC1EU0 hBNTEyX0FT
TSI7DQogICAgJGNmbGFncy49IiAtREFFU19BU00gLURSTUQxNj BfQVNNIjsN
CiB9DQogZWxzZQ0K
--AKMAILBOUNDARY--
__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org