openssl: Openssl 3.2.1 configuration fails on windows
Hello, I’ve used the same environment I’ve build all my previous Openssl versions, it now fails for version 3.2.1 VS 14.28.29914.0 Nasm 2.16.01 Perl 5.24.3
c:\os\openssl>perl configure
It looks like you don't have either nmake.exe or dmake.exe on your PATH,
so you will not be able to execute the commands from a Makefile. You can
install dmake.exe with the Perl Package Manager by running:
ppm install dmake
Configuring OpenSSL version 3.2.1 for target VC-WIN64A
Using os-specific seed configuration
Failure! makefile wasn't produced.
Please read INSTALL.md and associated NOTES-* files. You may also have to
look over your available compiler tool chain or change your configuration.
C:\os\openssl\crypto\providers: No such file or directory at configure line 3500.
The part about not having nmake is wrong, it always appears. I’ve also double checked version 3.2.0 and its fine. I can provide any other information needed.
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 23 (17 by maintainers)
Commits related to this issue
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to levitte/openssl by levitte 5 months ago
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to openssl/openssl by levitte 5 months ago
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to openssl/openssl by levitte 5 months ago
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to openssl/openssl by levitte 5 months ago
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to sthagen/openssl-openssl by levitte 5 months ago
- Fix a few incorrect paths in some build.info files The following files referred to ../liblegacy.a when they should have referred to ../../liblegacy.a. This cause the creation of a mysterious directo... — committed to Sashan/openssl by levitte 5 months ago
I can confirm from my end that both solutions now work and I am able to successfully compile OpenSSL 3.1.5. Confirmed the following two scenarios worked :
1) Perl 5.26 WITH Pull 23452 2) Perl 5.32.1 WITHOUT Pull 23452
Fix in #23452. @tavrez, would you mind trying it out?
I am getting the exact same error after trying to compile to the latest version of OpenSSL ( both 3.2.1 and 3.1.5 ). Nothing has changed on my machine aside from the OpenSSL source code:
Previous versions of OpenSSL 3.1.4 and 3.2.0 compile without issue