RE: [openssl.org #3564] Build error OpenSSL 1.0.1i

2014-10-30 Thread Mangino, Nicholas @ CSG - CSE via RT
Finally got it to build. Many thanks for all your help.

-Original Message-
From: Andy Polyakov via RT [mailto:r...@openssl.org] 
Sent: Monday, October 27, 2014 4:51 PM
To: Mangino, Nicholas @ CSG - CSE
Cc: openssl-dev@openssl.org
Subject: Re: [openssl.org #3564] Build error OpenSSL 1.0.1i

 Followed your instructions regarding changing the target.
 But received different problems with the assembler.
 See below
 
 Y:\OpenSSL\openssl-1.0.1icmd /c nasm -f win64 -v  1NUL 21
 
 Y:\OpenSSL\openssl-1.0.1iif 1 NEQ 0 goto ml64
 
 Y:\OpenSSL\openssl-1.0.1iperl ms\uplink-x86_64.pl masm  
 1ms\uptable.asm
 
 Y:\OpenSSL\openssl-1.0.1iml64 -c -Foms\uptable.obj ms\uptable.asm 
 'ml64' is not recognized as an internal or external command, operable 
 program or batch file.

You do need assembler. If you don't have ml64 (no, ml won't do), then just 
download nasm and drop it anywhere on %PATH%. Actually nasm is preferred. If in 
doubt, always use nasm.



__
OpenSSL Project http://www.openssl.org
Development Mailing List   openssl-dev@openssl.org
Automated List Manager   majord...@openssl.org


RE: [openssl.org #3564] Build error OpenSSL 1.0.1i

2014-10-27 Thread Mangino, Nicholas @ CSG - CSE via RT
\uptable.asm(157) : error A2006:undefined symbol : rdx
ms\uptable.asm(158) : error A2006:undefined symbol : r8
ms\uptable.asm(159) : fatal error A1012:error count exceeds 100; stopping 
assembly
NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 
11.0\VC\BIN\ml.EXE' : r
eturn code '0x1'
Stop.

Y:\OpenSSL\openssl-1.0.1i

Any suggestions?


-Original Message-
From: Andy Polyakov via RT [mailto:r...@openssl.org] 
Sent: Thursday, October 23, 2014 8:44 AM
To: Mangino, Nicholas @ CSG - CSE
Cc: openssl-dev@openssl.org
Subject: Re: [openssl.org #3564] Build error OpenSSL 1.0.1i

 I am attempting to build Open SSL 1.0.1.i on  Intel 64,  Windows 7,  using 
 Visual Studio Professional 2012.
 I configured the build with
 perl  Configure  debug-VC-WIN64I  no-asm  no-hw

WIN64I denotes Itanium, while what you need on Windows 7 is WIN64A.

 ms\do_win64i complains about not finding ias but continues.
 
 Running   nmake -f ms\ntdll.mak  generates the following errors
 ml  /c ms\uptable.asm
 Microsoft (R) Macro Assembler Version 11.00.50727.1 Copyright (C) 
 Microsoft Corporation.  All rights reserved.
 
 Assembling: ms\uptable.asm
 ms\uptable.asm(1) : error A2008:syntax error : .
 ms\uptable.asm(2) : error A2044:invalid character in file
 ms\uptable.asm(3) : error A2044:invalid character in file
 ms\uptable.asm(5) : error A2044:invalid character in file
 ms\uptable.asm(6) : error A2034:must be in segment block
 ms\uptable.asm(7) : error A2008:syntax error : .
 ms\uptable.asm(8) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(9) : error A2008:syntax error : loc0
 ms\uptable.asm(10) : error A2008:syntax error : .
 ms\uptable.asm(11) : error A2008:syntax error
 ms\uptable.asm(12) : error A2044:invalid character in file
 ms\uptable.asm(13) : error A2008:syntax error : .
 ms\uptable.asm(14) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(15) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(16) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(17) : error A2044:invalid character in file
 ms\uptable.asm(18) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(19) : error A2045:missing angle bracket or brace in 
 literal ...
 ms\uptable.asm(104) : error A2045:missing angle bracket or brace in 
 literal
 ms\uptable.asm(105) : error A2044:invalid character in file
 ms\uptable.asm(106) : fatal error A1012:error count exceeds 100; 
 stopping assembly NMAKE : fatal error U1077: 'C:\Program Files 
 (x86)\Microsoft Visual Studio 11.0\VC\BIN\ml.EXE' : r eturn code '0x1'
 Stop.
 
 I configured for no assembler code but nmake is attempting to assemble this 
 code.

Yes, even with no-asm you need assembler to compile one little assembly module.

 How can I gert around this error and complete the build?

You correct target. Confusion likely arouse from the fact that Intel started to 
use Intel 64 to denote x86_64 processors. I mean it's easy to mix IA64 and 
Intel 64...




__
OpenSSL Project http://www.openssl.org
Development Mailing List   openssl-dev@openssl.org
Automated List Manager   majord...@openssl.org


Re: [openssl.org #3564] Build error OpenSSL 1.0.1i

2014-10-27 Thread Andy Polyakov via RT
 Followed your instructions regarding changing the target.
 But received different problems with the assembler.
 See below
 
 Y:\OpenSSL\openssl-1.0.1icmd /c nasm -f win64 -v  1NUL 21
 
 Y:\OpenSSL\openssl-1.0.1iif 1 NEQ 0 goto ml64
 
 Y:\OpenSSL\openssl-1.0.1iperl ms\uplink-x86_64.pl masm  1ms\uptable.asm
 
 Y:\OpenSSL\openssl-1.0.1iml64 -c -Foms\uptable.obj ms\uptable.asm
 'ml64' is not recognized as an internal or external command,
 operable program or batch file.

You do need assembler. If you don't have ml64 (no, ml won't do), then
just download nasm and drop it anywhere on %PATH%. Actually nasm is
preferred. If in doubt, always use nasm.


__
OpenSSL Project http://www.openssl.org
Development Mailing List   openssl-dev@openssl.org
Automated List Manager   majord...@openssl.org


Re: [openssl.org #3564] Build error OpenSSL 1.0.1i

2014-10-23 Thread Andy Polyakov via RT
 I am attempting to build Open SSL 1.0.1.i on  Intel 64,  Windows 7,  using 
 Visual Studio Professional 2012.
 I configured the build with
 perl  Configure  debug-VC-WIN64I  no-asm  no-hw

WIN64I denotes Itanium, while what you need on Windows 7 is WIN64A.

 ms\do_win64i complains about not finding ias but continues.
 
 Running   nmake -f ms\ntdll.mak  generates the following errors
 ml  /c ms\uptable.asm
 Microsoft (R) Macro Assembler Version 11.00.50727.1
 Copyright (C) Microsoft Corporation.  All rights reserved.
 
 Assembling: ms\uptable.asm
 ms\uptable.asm(1) : error A2008:syntax error : .
 ms\uptable.asm(2) : error A2044:invalid character in file
 ms\uptable.asm(3) : error A2044:invalid character in file
 ms\uptable.asm(5) : error A2044:invalid character in file
 ms\uptable.asm(6) : error A2034:must be in segment block
 ms\uptable.asm(7) : error A2008:syntax error : .
 ms\uptable.asm(8) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(9) : error A2008:syntax error : loc0
 ms\uptable.asm(10) : error A2008:syntax error : .
 ms\uptable.asm(11) : error A2008:syntax error
 ms\uptable.asm(12) : error A2044:invalid character in file
 ms\uptable.asm(13) : error A2008:syntax error : .
 ms\uptable.asm(14) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(15) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(16) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(17) : error A2044:invalid character in file
 ms\uptable.asm(18) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(19) : error A2045:missing angle bracket or brace in literal
 ...
 ms\uptable.asm(104) : error A2045:missing angle bracket or brace in literal
 ms\uptable.asm(105) : error A2044:invalid character in file
 ms\uptable.asm(106) : fatal error A1012:error count exceeds 100; stopping 
 assembly
 NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 
 11.0\VC\BIN\ml.EXE' : r
 eturn code '0x1'
 Stop.
 
 I configured for no assembler code but nmake is attempting to assemble this 
 code.

Yes, even with no-asm you need assembler to compile one little assembly
module.

 How can I gert around this error and complete the build?

You correct target. Confusion likely arouse from the fact that Intel
started to use Intel 64 to denote x86_64 processors. I mean it's easy
to mix IA64 and Intel 64...



__
OpenSSL Project http://www.openssl.org
Development Mailing List   openssl-dev@openssl.org
Automated List Manager   majord...@openssl.org