On Wed, 2004-03-03 at 16:47, Nick Ing-Simmons wrote:
> Scott T. Hildreth <[EMAIL PROTECTED]> writes:
> >As posted earlier, the Active State Perl runs under the Windows
> >environment and the cygwin Perl is compiled under the cygwin "unix" type
> >environment.  So if you are compiling modules under cygwin, you need to
> >use the cygwin compiled perl.   
> 
> Or to put it another way, when building modules to run with ActivePerl
> you must use nmake and not cygwin make (nor MSYS make).
> 
> ActivePerl's MakeMaker writes Makefiles for nmake. So 
> pathnames have \ not / and drive letters and possibly leading 
> spaces instead of tabs, and special nmake macros to work round 
> command line length issues etc. etc.
> 
> I believe you can download nmake.exe from somewhere.
> 
> A relatively minor tweak to Config.pm will cause ActivePerl 
> to write Makefiles for 'dmake', but we don't yet have MakeMaker 
> support for either GNU make on Win32 (either cygwin's or MinGW one),
> nor the "make" that comes with Borland.
> 

  ..or in more detail, all that stuff Nick wrote above.  :-)

> >
> >
> >On Wed, 2004-03-03 at 09:18, Doug Brann wrote:
> >> Dear newsgroup,
> >> 
> >> I am running perl Active State 5.8.3 and cygwin. I can't seem to build any perl 
> >> modules (even the ones off CPAN)
> >> 
> >> I type:
> >> perl Makefile.PL
> >> and all is ok,
> >> 
> >> then I type:
> >> make test
> >> 
> >> and I get the error:
> >> Makefile:332: *** multiple target patterns. Stop.
> >> 
> >> What's going on?
> 

Reply via email to