On Sun, 29 Apr 2001, Jarkko Hietaniemi wrote: > On Sat, Apr 28, 2001 at 09:56:51PM -0700, Prymmer/Kahn wrote: > > > > Enclosed please find a unix-format context diff of the changes > > I found necessary to get the 9885 kit building with MS VC 5 > > and the nmake utility. This patch affects only win32/Makefile > > and does not (unfortunately) take care of win32/makefile.mk. > > Thanks, applied. > > We really do need a Win32 make champion who will unify the Makefile > and makefile.mk by creating a win32/makemake.pl or similar that would > generate both makefiles. Indeed we do. In addition, as Nick points out later, we need for win32/buildext.pl and win32/FindExt.pm to be a little more clever and to remove the hard coded list of extensions. Unfortunately for my testing here is what I see trying to use Sarathy's modified dmake-4.1pl1-win32.zip along with MS VC 5 (which may be an unkosher combination since the dmake recommendations in README.win32 imply that one would opt for dmake if you were using Borland and you would use nmake if you were using MSVC): D:\ttt\perl\win32>dmake del /f config.h del: not found dmake.exe: Error code 127, while making '.\config.h' (Ignored) copy config_H.vc config.h copy: not found dmake.exe: Error code 127, while making '.\config.h' So apparently dmake cannot recognize basic %COMSPEC% builtins like `del` and `copy`. In a built-with-nmake directory tree a similar error message cropse up when dmake tries to run: ..\miniperl.exe $(ARGS) and dmake fails with "don't know much about '..miniperl.exe'" type messages. My dmake installation seems unhealthy. An attempt at running `dmake -v` does yield plenty of verbose messages and most of the startup files seem to be found. I am not sure yet what I've done wrong. Peter PrymmerThread Previous | Thread Next