Nobu:

Wow. Well it was definitely an NMAKE version issue. Another program have
installed apparently gave the 1.20 version of nmake that came (unannounced)
with it precedence in my path over the latest 6.0 version. All I changed was
putting my various MS Visual C++ 6.0 folders ahead in my system PATH (they
were in my user path prior to that), and it worked fine.

Thanks!

-Bob.



% -----Original Message-----
% From: nobu.nokada / softhome.net [mailto:nobu.nokada / softhome.net]
% Sent: Thursday, February 07, 2002 8:14 PM
% To: ruby-talk ML
% Subject: Re: Latest CVS/Win32 build error
%
%
% Hi,
%
% At Fri, 8 Feb 2002 10:19:08 +0900,
% Bob Calco <robert.calco / verizon.net> wrote:
% > I created a mswin32-build directory in my build root, and when
% I issue the
% > following:
% >
% > C:\projects\ruby\mwin32-build\> ..\win32\configure.bat
% >
% > I get the following:
% >
% > Loading NMAKE
% > NMAKE: Fatal error U1073: don't know how to make 'nul'
% > Stop.
% >
% > I hadn't had this experience with 1.6.5, anybody else run into
% this with the
% > stable snapshot/current CVS? If so, any idea what the cause is?
% I believe I
% > have all the right stuff in my PATH -- nmake, cl, dumpbin, lib, rm.
%
% Nothing changed since one and a half years ago.  Which version
% of Windows and nmake.exe do you use?  `nul' should be a special
% device name.
%
% BTW, try this patch.
%
% Index: configure.bat
% ===================================================================
% RCS file: /cvs/ruby/src/ruby/win32/configure.bat,v
% retrieving revision 1.1
% diff -u -2 -p -r1.1 configure.bat
% --- configure.bat	2000/08/03 09:55:54	1.1
% +++ configure.bat	2002/02/08 04:03:04
% @@ -11,3 +11,4 @@ echo>> ~tmp~.mak 	@-$(MAKE) -l$(MAKEFLAG
%  if not "%1" == "" echo>> ~tmp~.mak 	srcdir="%1" \
%  echo>> ~tmp~.mak 	WIN32DIR=$(@D)
% +echo>> ~tmp~.mak nul:
%  nmake -alf ~tmp~.mak
%
% --
% Nobu Nakada
%