[openssl] Build error on x64-windows

[smultronbusken]

Package: openssl:x64-windows@3.2.1#2

Host Environment

• Host: x64-windows
• Compiler: MSVC 19.39.33523.0
• vcpkg-tool version: 2024-03-14-7d353e869753e5609a1f1a057df3db8fd356e49d vcpkg-scripts version: 1751f9f8c 2024-04-09 (19 hours ago)

To Reproduce

vcpkg install openssl Failure logs

-- Using cached openssl-openssl-openssl-3.2.1.tar.gz.
-- Cleaning sources at C:/Users/fredh/Documents/SignalRClientCpp/submodules/vcpkg/buildtrees/openssl/src/nssl-3.2.1-385ff0b09c.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/fredh/Documents/SignalRClientCpp/submodules/vcpkg/downloads/openssl-openssl-openssl-3.2.1.tar.gz
-- Applying patch command-line-length.patch
-- Applying patch script-prefix.patch
-- Applying patch windows/install-layout.patch
-- Applying patch windows/install-pdbs.patch
-- Applying patch unix/android-cc.patch
-- Applying patch unix/move-openssldir.patch
-- Applying patch unix/no-empty-dirs.patch
-- Applying patch unix/no-static-libs-for-shared.patch
-- Using source at C:/Users/fredh/Documents/SignalRClientCpp/submodules/vcpkg/buildtrees/openssl/src/nssl-3.2.1-385ff0b09c.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
-- Getting CMake variables for x64-windows
-- Prerunning x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: C:/Users/fredh/Documents/SignalRClientCpp/submodules/vcpkg/downloads/tools/perl/5.38.0.1/perl/bin/perl.exe Configure enable-static-engine enable-capieng no-tests no-docs shared no-apps no-makedepend VC-WIN64A --debug --prefix=C:\\Users\\fredh\\Documents\\SignalRClientCpp\\submodules\\vcpkg\\packages\\openssl_x64-windows\\debug --openssldir=C:\\Users\\fredh\\Documents\\SignalRClientCpp\\submodules\\vcpkg\\packages\\openssl_x64-windows\\debug AS=C:\\Users\\fredh\\Documents\\SignalRClientCpp\\submodules\\vcpkg\\downloads\\tools\\nasm\\nasm-2.16.01\\nasm.exe "CC=C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.39.33519\\bin\\Hostx64\\x64\\cl.exe" "CFLAGS=  -nologo -DWIN32 -D_WINDOWS -W3 -utf-8 -MP  -D_DEBUG -MDd -Z7 -Ob0 -Od -RTC1  " "AR=C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.39.33519\\bin\\Hostx64\\x64\\lib.exe" "ARFLAGS=-machine:x64 -nologo" "LD=C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.39.33519\\bin\\Hostx64\\x64\\link.exe" "LDFLAGS= -machine:x64 -nologo    -debug -INCREMENTAL "
    Working Directory: C:/Users/fredh/Documents/SignalRClientCpp/submodules/vcpkg/buildtrees/openssl/x64-windows-dbg
    Error code: 255
    See logs for more information:
      C:\Users\fredh\Documents\SignalRClientCpp\submodules\vcpkg\buildtrees\openssl\prerun-specific-x64-windows-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_nmake.cmake:125 (vcpkg_execute_required_process)
  ports/openssl/windows/portfile.cmake:74 (vcpkg_build_nmake)
  ports/openssl/portfile.cmake:75 (include)
  scripts/ports.cmake:175 (include)

C:\Users\fredh\Documents\SignalRClientCpp\submodules\vcpkg\buildtrees\openssl\prerun-specific-x64-windows-dbg-err.log

``` strict.pm did not return a true value at Configure line 13. BEGIN failed--compilation aborted at Configure line 13. ```

[LilyWangLL]

Maybe you can try to clone vcpkg to a short path, then rebuild openssl.

[smultronbusken]

Does not work, not even in C:\vcpkg

[github-actions[bot]]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[smultronbusken]

still not working sadly

[github-actions[bot]]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

[smultronbusken]

For future people: This error is impossible to fix due to an issue with Windows itself...