Hi,

Are you sure you are using x64 Cross Tools Command Prompt of Visual Studio
2005? You will have this error if you use the regular Command Prompt of
Visual Studio 2005 instead of the cross compiling one. There is no need to
run under Windows 64bit in order to compile WIN64 binaries.

Regards,
-- 
Mounir IDRASSI
IDRIX
http://www.idrix.fr

On Thu, June 5, 2008 11:47 pm, Melnick, Jeff wrote:
> I've been trying to build OpenSSL 0.9.8h for WIN64A.
>
> I have Visual Studio 2005, SP1 and the Server 2008 SDK (6.1) on 32 bit
> Windows XP.
>
>
>
> I run:
>
>             perl Configure VC-WIN64A
>
>             ms\do_win64a
>
>             nmake -f ms\ntdll.mak
>
>
>
> I get a ton of errors from ms\uptable.asm.  For example:
>
>             ms\uptable.asm(45) : error A2024: invalid operand size for
> instruction
>
> ms\uptable.asm(62) : error A2024: invalid operand size for instruction
>
> ms\uptable.asm(32) : error A2006: undefined symbol : r9
>
> ms\uptable.asm(33) : error A2006: undefined symbol : r8
>
> ms\uptable.asm(34) : error A2006: undefined symbol : rdx
>
> ms\uptable.asm(35) : error A2006: undefined symbol : rcx
>
>
>
> I'm beginning to think that this needs to be build on a 64 bit version of
> Windows.
>
>
>
> Has anyone seen this?
>
> What might I need to do differently?
>
> Thank you for the help.
>
>
>
> ________________________________
>
> Jeff Melnick
> Sr Engineer
>
>   <http://www.securecomputing.com/>
>
> Your trusted source for enterprise security(tm)
> www.securecomputing.com <http://www.securecomputing.com/>
> NASDAQ: SCUR
>
> +1 (925) 288-4154 (Direct Phone)
> +1 (651) 307-1471 (Mobile Phone)
> +1 (925) 827-2593 (Fax)
> [EMAIL PROTECTED]
>
> Secure Computing Corporation
> 1855 Gateway Boulevard
> Suite 200
> Concord, CA 94520
> USA>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to