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

[Mangino, Nicholas @ CSG - CSE 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

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.

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

Appreciate any help you can give.

______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-***@openssl.org
Automated List Manager ***@openssl.org

[Mangino, Nicholas @ CSG - CSE via RT]

Have attempted another build using Win 32 option
perl Configure VC-WIN32 no-asm no-hw

ms\do_ms completes without error or warnings.

Running nmake -f ms\ntdll.mak compiles all C code but generates the following error on linking
rc /fo"tmp32dll\libeay32.res" /d CRYPTO ms\version32.rc
Microsoft (R) Windows (R) Resource Compiler Version 6.2.9200.16384
Copyright (C) Microsoft Corporation. All rights reserved.

link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def @C:\Users\nmangino\AppData\Local\Temp\nm9D07.tmp
Creating library out32dll\libeay32.lib and object out32dll\libeay32.exp
bss_fd.obj : error LNK2001: unresolved external symbol _OPENSSL_UplinkTable
bss_file.obj : error LNK2019: unresolved external symbol _OPENSSL_UplinkTable referenced in function
_BIO_new_file
b_dump.obj : error LNK2001: unresolved external symbol _OPENSSL_UplinkTable
out32dll\libeay32.dll : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\link.EXE"' :
return code '0x460'
Stop.

Better now but can't get away from this uplink error.
Again, I appreciate any help you can give.


-----Original Message-----
From: The default queue via RT [mailto:***@openssl.org]
Sent: Tuesday, October 14, 2014 1:49 AM
To: Mangino, Nicholas @ CSG - CSE
Subject: [openssl.org #3564] AutoReply: Build error OpenSSL 1.0.1i


Greetings,

This message has been automatically generated in response to the creation of a trouble ticket regarding:
"Build error OpenSSL 1.0.1i",
a summary of which appears below.

There is no need to reply to this message right now. Your ticket has been assigned an ID of [openssl.org #3564].

Please include the string:

[openssl.org #3564]

in the subject line of all future correspondence about this issue. To do so, you may reply to this message.

Thank you,
***@openssl.org

-------------------------------------------------------------------------
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

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.

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

Appreciate any help you can give.


______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-***@openssl.org
Automated List Manager ***@openssl.org

[Andy Polyakov via RT]

Post by Mangino, Nicholas @ CSG - CSE via RT
Have attempted another build using Win 32 option
perl Configure VC-WIN32 no-asm no-hw
ms\do_ms completes without error or warnings.
Running nmake -f ms\ntdll.mak compiles all C code but generates the following error on linking
rc /fo"tmp32dll\libeay32.res" /d CRYPTO ms\version32.rc
Microsoft (R) Windows (R) Resource Compiler Version 6.2.9200.16384
Copyright (C) Microsoft Corporation. All rights reserved.
Creating library out32dll\libeay32.lib and object out32dll\libeay32.exp
bss_fd.obj : error LNK2001: unresolved external symbol _OPENSSL_UplinkTable
bss_file.obj : error LNK2019: unresolved external symbol _OPENSSL_UplinkTable referenced in function
_BIO_new_file
b_dump.obj : error LNK2001: unresolved external symbol _OPENSSL_UplinkTable
out32dll\libeay32.dll : fatal error LNK1120: 1 unresolved externals
return code '0x460'
Stop.

I can't reproduce it. You tried to build for another platform earlier.
If it was in same directory you probably have to delete tmp32dll.


______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-***@openssl.org
Automated List Manager ***@openssl.org

[Andy Polyakov via RT]

Post by Mangino, Nicholas @ CSG - CSE 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.

Post by Mangino, Nicholas @ CSG - CSE via RT
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.

Post by Mangino, Nicholas @ CSG - CSE via RT
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-***@openssl.org
Automated List Manager ***@openssl.org