Error building OpenSSL-1.1.1g

Thu Jun 25 23:47:16 UTC 2020

Thank you.  I suspected as much.

Can someone point me to sources of information about how to resolve this issue?  I simply don't believe I'm the only one who wants to build OpenSSL for use in a Windows 10 environment - someone must have been successful and be able to point me to additional information.

A few points that may be useful and then two specific questions.

1. I program exclusively for a Windows environment.  Most of what I develop should be portable, but it as almost exclusively for my own use, which is presently almost exclusively Windows.  I *may* at some future point go back to Linux, but not yet.

2. I have never used (or seen need to use) Visual Studio.  I downloaded a copy specifically to get this package installed.  I attempted to install for 64-bit use.   But it is not entirely clear to me to know which pars are actually being used.  Usually, I would have just used Mingw-w64 along with Windows ports of the standard complement of UNIX tools.  While I do have access to Cygwin, my preference is to either stick with Windows or make t full change back to UNIX.

3. I have built and installed a significant number of software packages, so am not really a newbie, but there are clear gaps in my knowledge and experience.

4. Before installing Visual Studio, I messed around quite a bit trying to figure out how I might modify the build process to work with my usual set of tools - mostly UNIX-tools ported to Windows environment.  My preference would be to find pointers to information of how to accomplish that.

THE SPECIFIC QUESTIONS:

1. How do I figure out whether OpenSSL is trying to build the 32- or 64-bit version and which options, or environmental variables, or specific PATH elements do I need to pay attention to in order to accomplish that?

2. Has anyone succeeded building OpenSSL for use in a Windows 10 environment *without* need for visual studio?

I'd really appreciate any useful information or pointers to such.

Thanks. 

-----Original Message-----
From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of Matt Caswell
Sent: Thursday, June 25, 2020 2:03 PM
To: openssl-users at openssl.org
Subject: Re: Error building OpenSSL-1.1.1g

On 25/06/2020 20:20, mhkelley2017 at gmail.com wrote:
> Thanks! That helped, but I have two follow-ups.
> 
> 1) To whom would I suggest minor changes to the available installation
> instructions to help avoid future such misunderstandings?

You can raise on issue on Github. Or even better raise a PR with your
suggested changes. However, as it so happens the Windows instructions
have very recently been significantly updated - so some of your
suggestions may already have been included:

https://github.com/openssl/openssl/pull/12098

> crypto\aes\aesni-mb-x86_64.obj : fatal error LNK1112: module machine type
> 'x64' conflicts with target machine type 'x86'

This usually occurs when attempting to build 64-bit OpenSSL using the
32-bit VisualStudio tools.

Matt

> Could Not Find
> c:\Users\Owner\LocalPrograms\OpenSSL\openssl-1.1.1g\libcrypto-1_1-x64.*
> NMAKE : fatal error U1077: 'link' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio\2019\Community\VC\Tools\MSVC\14.26.28801\bin\HostX86\x86\nmake.exe"'
> : return code '0x2'
> Stop.
> 
> -----Original Message-----
> From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of Matt
> Caswell
> Sent: Thursday, June 25, 2020 12:15 PM
> To: openssl-users at openssl.org
> Subject: Re: Error building OpenSSL-1.1.1g
> 
> 
> 
> On 25/06/2020 18:32, Michael Wojcik wrote:
>>> From: openssl-users [mailto:openssl-users-bounces at openssl.org] On Behalf
> Of mhkelley2017 at gmail.com
>>> Sent: Thursday, June 25, 2020 11:54
>>
>>> Error:  'ml64' is not recognized as an internal or external command,
>>> operable program or batch file.
>>
>> It's part of Visual C. The VC-WIN64A-masm configuration
> (Configurations/50-masm.conf) specifies it as the assembler.
> 
> Note that using masm to compile OpenSSL is no longer supported by us
> (although it might still work).
> 
> Preferred is to use the VC-WIN64A target and the nasm compiler.
> 
> If you use the Developer Studio command prompt (64-bit) it should have
> all the environment variables set up already to find the various VS tools.
> 
> Matt
> 
> 
>>
>>> Building with Visual Studio  2019 Community
>>
>> Maybe VS2019 Community doesn't include the assembler? I haven't looked. Or
> maybe it's part of some optional component?
>>
>> In VS2017 Professional, which is what I have configured at the moment on
> this machine, it's in .../VC/Tools/MSVC/14.16.27023/bin/HostX86/x64, thanks
> to VS's gratuitously complicated directory layout.
>>
>> --
>> Michael Wojcik
>> Distinguished Engineer, Micro Focus
>>
>>
>>
> 