building with configuration VC-WIN64A fails

[jamuir]

I tried to build master (eaee176) using the configuration VC-WIN64A on two different x86_64 windows machines and both builds failed.

I used a bat file containing the following lines:

REM doit.bat > log.txt 2>&1
perl Configure VC-WIN64A --prefix="C:\Users\tvavra\source\repos\james\tmp\beforespace afterspace"
nmake
nmake test
nmake install

The first nmake step fails with the following error:

	cmd /C ""link" /nologo /debug /dll  /nologo /debug @C:\Users\tvavra\AppData\Local\Temp\2\nmB0A4.tmp /implib:libcrypto.lib || (DEL /Q libcrypto-3-x64.* libcrypto.lib & EXIT 1)"
crypto\aes\libcrypto-shlib-aes_cfb.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
Could Not Find C:\Users\tvavra\source\repos\james\openssl\libcrypto-3-x64.*
NMAKE : fatal error U1077: 'cmd /C ""link" /nologo /debug /dll  /nologo /debug @C:\Users\tvavra\AppData\Local\Temp\2\nmB0A4.tmp /implib:libcrypto.lib || (DEL /Q libcrypto-3-x64.* libcrypto.lib & EXIT 1)"' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\bin\HostX86\x86\nmake.exe" /                   _tests' : return code '0x2'
Stop.

Then both nmake test and nmake install fail with the same error.

[jamuir]

I should note that if I call Configure without VC-WIN64A (so that the script selects its own build-config), then the build completes successfully.

[mattcaswell]

fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'

This normally occurs because of a discrepancy between the toolchain being used and the architecture that you are attempting to build for, i.e. using the x86 VC toolchain but attempting to build for VC-WIN64A (i.e. x86_64).

If you run the compiler (cl.exe) by itself with no arguments it should tell you what architecture it is targeting.

See:

openssl/NOTES-WINDOWS.md

Lines 65 to 73 in eaee176

	4. Use Visual Studio Developer Command Prompt with administrative privileges,
	choosing one of its variants depending on the intended architecture.
	Or run `cmd` and execute `vcvarsall.bat` with one of the options `x86`,
	`x86_amd64`, `x86_arm`, `x86_arm64`, `amd64`, `amd64_x86`, `amd64_arm`,
	or `amd64_arm64`.
	This sets up the environment variables needed for `nmake.exe`, `cl.exe`,
	etc.
	See also
	<https://docs.microsoft.com/cpp/build/building-on-the-command-line>

[jamuir]

thanks for your reply, Matt.

you were right that I did not have the VC toolchain initialized correctly.

I set it correctly now like so:

"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build"\vcvarsall.bat amd64

cl reports it is targeting x64.

Unfortunately, I am still not able to build using VC-WIN64A.

@REM doit.bat > log.txt 2>&1

set path=C:\Program Files\NASM;%path%
nasm -v
perl -v

cl

perl Configure VC-WIN64A --prefix="C:\Users\muirj\source\repos\tmp\beforespace afterspace"
nmake

I hit the following failure in the lib tool:

        "lib" /nologo /out:apps\libapps.lib @C:\Users\muirj\AppData\Local\Temp\nmEFDA.tmp
apps\lib\libapps-lib-fmt.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
NMAKE : fatal error U1077: '"lib" /nologo /out:apps\libapps.lib @C:\Users\muirj\AppData\Local\Temp\nmEFDA.tmp' : return code '0x458'       
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\bin\HostX64\x64\nmake.exe" /
                   _build_sw' : return code '0x2'

it seems like the option /machine is missing from lib.

[mattcaswell]

Did you do a "make clean" between builds? I suspect some leftovers from your previous failed build. Maybe even try a fresh clone.

[jamuir]

thanks again, Matt.

You were right. It seems to have been some artifact from my previous failed build causing the problem. I thought I had done nmake clean after the failure, but it seems likely I did not.

After a nmake clean and a few calls to git clean -x ... I went back to a completely clean tree, and then I was finally able to build successfully using VC-WIN64A.