Hi=20

This as been discussed in users mailing list.
subject: 0.9.7f rc4/asm problem=20
OpenSSL 0.9.7f released (you 'll find an answer oon this =
thread)

nasmw -f win32 -o crypto\rc4\asm\r4_win32.obj
..\crypto\rc4\asm\r4_win32.asm
..\crypto\rc4\asm\r4_win32.asm:30: error: operation size not specified
..\crypto\rc4\asm\r4_win32.asm:265: error: operation size not specified
..\crypto\rc4\asm\r4_win32.asm:267: error: operation size not specified
..\crypto\rc4\asm\r4_win32.asm:271: error: operation size not specified
NMAKE : fatal error U1077: 'nasmw' : return code '0x1'
Stop.

When I use the previous version of /crypto/rc4/asm/rc4-586.pl, it =
compiles
fine. This was obviously triggered by the changes seen here:
http://cvs.openssl.org/filediff?f=3D...-586.pl&v1=3D=
1.1.1
..1&v2=3D1.1.1.1.12.1.

I've included excerpts of the diff that show which parts of the script =
are
generating the compile errors

Regards

Fred
-----Original Message-----
From: owner-openssl-dev@openssl.org on behalf of David Reeves via RT
Sent: Fri 4/8/2005 4:51 PM
To:=09
Cc: openssl-dev@openssl.org
Subject: [openssl.org #1041] OpenSSL WIN32 Compiler Bug report for =
openssl 0.9.7f=20

April 8, 2005

OpenSSL WIN32 Compiler Bug report for openssl 0.9.7f
=20

Hi OpenSSL developers,


I just downloaded openssl 9.7f. I am trying to
compile it with MSVC++ 6.0 service pack 6. I cannot
find masm that is available with MSVC sp6, so I
downloaded nasm.

As directed in the WIN32 Installation notes for
OpenSSL, I did the following:
=20

1) perl Configure VC-WIN32

2) ms\do_nasm

3) nmake -f ms\ntdll.mak

=20

The build stops as shown below:

=20

C:\Downloads\OpenSSL\openssl-0.9.7f>nasmw -f win32 -o
crypto\rc4\asm\r4_win32.obj
..\crypto\rc4\asm\r4_win32.asm

..\crypto\rc4\asm\r4_win32.asm:30: error: operation
size not specified

..\crypto\rc4\asm\r4_win32.asm:265: error: operation
size not specified

..\crypto\rc4\asm\r4_win32.asm:267: error: operation
size not specified

..\crypto\rc4\asm\r4_win32.asm:271: error: operation
size not specified

=20

Have you received a confirmation - that this is a bug
in the new code? Is this isolated to nasm or does
this also occur with masm?

=20

Do you have a satisfactory work-around?

=20

Regards,

=20

David Reeves
dnreeves@swbell.net
dreeves@practiceinsight.net

=20

__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org



__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org