![]() Some more related details are available here: "This is caused by our use of IPC::Cmd::can_run, and somewhere deep down, ends up having Config interacting with ExtUtils::MakeMaker in some off manner, print that string and then just return to whatever level up." Passing on the actual analysis from levitte ( ): Please note that the issue was reported to OpenSSL already on where it was determined to be an issue related to ActivePerl rather than OpenSSL. Note that nmake.exe is very well available from the Visual Studio 2015 command prompt (even though it's not in the system environment's PATH settings - it's being added to PATH by starting the Visual Studio 2015 command prompt though). Install dmake.exe with the Perl Package Manager by running: So you will not be able to execute the commands from a Makefile. It looks like you don't have either nmake.exe or dmake.exe on your PATH, and OpenSSL 1.1.0c run "perl Configure VC-WIN64A" from a Visual Studio 2015 command prompt.
0 Comments
Leave a Reply. |