Cannot compile on windows

[Shawn Hoffman]

I seem to have problems which others have posted about before, however I've either seen no solutions in response, or the solutions which worked for them don't work for me.

Anyways, the environment I've tried to compile in has consisted of all combinations of the following:
windows 7 x64
VS2008/VS2010 x86/x64
Latest ActiveState Perl/Latest Strawberry Perl

I've tried to compile within the VS command prompts (which are supposed to setup the environment for you), as well as from a normal cmd prompt (setting up the environment with vsvars32.bat).
I've tried with and without NASM.

So, the first error I get is that running one of the do_* scripts in ms results in blank nt.mak and ntdll.mak files. This is because of line 907 in mk1mf.pl being hit, for example:

C:\openssl-1.0.0d>ms\do_nasm.bat

C:\openssl-1.0.0d>perl util\mkfiles.pl 1>MINFO

C:\openssl-1.0.0d>perl util\mk1mf.pl nasm VC-WIN32 1>ms\nt.mak
no rule for crypto\md4 at util\mk1mf.pl line 907.

C:\openssl-1.0.0d>perl util\mk1mf.pl dll nasm VC-WIN32 1>ms\ntdll.mak
no rule for crypto\md4 at util\mk1mf.pl line 907.

C:\openssl-1.0.0d>perl util\mk1mf.pl nasm BC-NT 1>ms\bcb.mak
no rule for crypto\md4 at util\mk1mf.pl line 907.

C:\openssl-1.0.0d>perl util\mkdef.pl 32 libeay 1>ms\libeay32.def

C:\openssl-1.0.0d>perl util\mkdef.pl 32 ssleay 1>ms\ssleay32.def

This caused me to try configuring with no-md4 and etcetera, however the mk1mf script is never happy...it will die based on other subdirs no matter what I've disabled via Configure.

There seem to be other problems after this (i.e. if i edit line 907, .mak files are created...but they fail), however I'd like to try to fix this first problem...maybe it will fix the following ones.

-Shawn

[kal...@gmail.com]

I came across this same problem today, and found out the issue involved carriage returns on winblows (surprise...). I added a line to mk1mf.pl to filter out any CRs left after the chop at line 319.

[line 319]: chop;
[line 320]: s/\r$//; #remove carriage return too!

-Johnny

[ying...@gmail.com]

Thanks. works for me. Only wonder, why this bug still exists in openssl now, almost a year.

[Jarmo Pertman]

Works for me too. Maybe there's no official bug report and that's why the bug still exists?

Jarmo Pertman
-----
IT does really matter - http://itreallymatters.net

[fanc...@gmail.com]

This bug is still not fixed at the latest version