Error building nodeJS + FIPS (static linking) on Windows 10

[RobertMcAuley]

Version

18.12.0

Platform

Microsoft Windows NT 10.0.19044.0 x64

Subsystem

No response

What steps will reproduce the bug?

Install windows prerequisites as defined in BUILDING.md: https://github.com/nodejs/node/blob/v18.x/BUILDING.md#windows

Run:
python configure.py --openssl-is-fips
.\vcbuild.bat

How often does it reproduce? Is there a required condition?

Reproduced every time, no required conditions.

What is the expected behavior?

The build should pass and node should run in FIPS mode

What do you see instead?

The build runs for about 30-40 minutes and fails with the below error trace:

...
...
     Creating library ..\..\out\Release\mksnapshot.lib and object ..\..\out\Release\mksnapshot.exp
  mksnapshot.vcxproj -> ..\..\out\Release\\mksnapshot.exe
  generating: "..\..\out\Release\obj\v8_snapshot\/snapshot.cc" "..\..\out\Release\obj\v8_snapshot\/embedded.S"
  Assembling ..\..\out\Release\obj\v8_snapshot\\embedded.S...
  setup-isolate-deserialize.cc
  snapshot.cc
  v8_snapshot.vcxproj -> ..\..\out\Release\lib\v8_snapshot.lib
  node_pch.cc
  node_snapshot_stub.cc
  node_mksnapshot.cc
     Creating library out\Release\node_mksnapshot.lib and object out\Release\node_mksnapshot.exp
  node_mksnapshot.vcxproj -> out\Release\\node_mksnapshot.exe
  node_mksnapshot
  fipsinstall, and also copy_fips_module
  Can't open "out\Release\obj.target/deps/openssl/libopenssl-fipsmodule.so" for reading, No such file or directory

Additional information

No response

[RobertMcAuley]

I verified that the file out\Release\obj.target/deps/openssl/libopenssl-fipsmodule.so doesn't exist. I assume it should have been created as part of the build process

[david-doran-ibm]

Related: #14115

[huseyinacacak-janea]

Hi @RobertMcAuley, I wanted to look into this issue but wasn't able to reproduce it on main branch. Do you think this can be closed now?

[RobertMcAuley]

Hi @huseyinacacak-janea if it can't be reproduced anymore then sure!

[StefanStojanovic]

Closing this one as it seems resolved now.